2014-09-04 22:36 GMT+09:00 Sean Dague s...@dague.net:
On 09/04/2014 09:30 AM, Ken'ichi Ohmichi wrote:
Hi
I'd like to request FFE for patches of v3-api-schema.
The list is the following:
https://review.openstack.org/#/c/67428/
https://review.openstack.org/#/c/103437/
https
repository, into their own repo called
openstack-integration-tests or os-integration-tests“.
why not keeping it simple:
tempest: importable test library
tempest-tests: all the test cases
Simple, obvious and clear ;)
+1 :-)
Thanks
Ken'ichi Ohmichi
big +1 :-)
2014-07-30 14:56 GMT-07:00 Sean Dague s...@dague.net:
+1
On 07/30/2014 02:19 PM, Chris Behrens wrote:
+1
On Jul 30, 2014, at 2:02 PM, Michael Still mi...@stillhq.com wrote:
Greetings,
I would like to nominate Jay Pipes for the nova-core team.
Jay has been involved with nova
Hi Jay,
I faced the same problem and can pass it with adding the following line
into localrc:
LOGFILE=/opt/stack/logs/stack.sh.log
Thanks
Ken'ichi Ohmichi
---
2014-07-02 14:58 GMT+09:00 Jay Lau jay.lau@gmail.com:
Hi,
Does any one encounter this error when install devstack? How did you
out the backlog.
I'll send out another reminder the day before the review day.
+1 for qa-spec review day.
I've written it on my schedule.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
/
Thanks
Ken'ichi Ohmichi
--
For the future micro versions, we still have those v3 test to be inspired by.
Chris, does that seem workable?
John
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
/servers.py#L82
Thanks
Ken'ichi Ohmichi
---
[1] https://review.openstack.org/#/c/98525/
[2] https://review.openstack.org/#/c/84695/
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
and the request SHOULD NOT be repeated.
would fit to out of quota.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
failed because of not
backporting the Nova patch into Icehouse branch yet.
I'm not sure we can backport this kind of patches into Icehouse
because Nova v3 API of Icehouse must be experimental in future.
So how about disabling v3 API tests in check-tempest-dsvm-full-icehouse?
Thanks
Ken'ichi Ohmichi
2014-05-10 0:29 GMT+09:00 Matthew Treinish mtrein...@kortar.org:
On Thu, May 08, 2014 at 09:50:03AM -0400, David Kranz wrote:
On 05/07/2014 10:48 AM, Ken'ichi Ohmichi wrote:
Hi Sean,
2014-05-07 23:28 GMT+09:00 Sean Dague s...@dague.net:
On 05/07/2014 10:23 AM, Ken'ichi Ohmichi wrote:
Hi
2014-05-09 22:57 GMT+09:00 Matthew Treinish mtrein...@kortar.org:
On Fri, May 09, 2014 at 10:31:00PM +0900, Ken'ichi Ohmichi wrote:
2014-05-09 15:00 GMT+09:00 Ghanshyam Mann
ghanshyam.m...@nectechnologies.in:
Hi Sean,
-Original Message-
From: Sean Dague [mailto:s...@dague.net
Hi David,
2014-05-07 22:53 GMT+09:00 David Kranz dkr...@redhat.com:
I just looked at a patch https://review.openstack.org/#/c/90310/3 which was
given a -1 due to not checking that every call to list_hosts returns 200. I
realized that we don't have a shared understanding or policy about this.
Hi Sean,
2014-05-07 23:28 GMT+09:00 Sean Dague s...@dague.net:
On 05/07/2014 10:23 AM, Ken'ichi Ohmichi wrote:
Hi David,
2014-05-07 22:53 GMT+09:00 David Kranz dkr...@redhat.com:
I just looked at a patch https://review.openstack.org/#/c/90310/3 which was
given a -1 due to not checking
expected.
Any thoughts?
Thanks
Ken'ichi Ohmichi
---
[1]: http://lists.openstack.org/pipermail/openstack-dev/2014-March/028724.html
http://lists.openstack.org/pipermail/openstack-dev/2014-February/027896.html
[2]:
https://review.openstack.org/#/q/status:open+project:openstack/tempest
Hi Matthew,
2014-04-28 11:54 GMT+09:00 Ken'ichi Ohmichi ken1ohmi...@gmail.com:
2014-04-28 11:02 GMT+09:00 Matthew Treinish mtrein...@kortar.org:
On Mon, Apr 28, 2014 at 01:01:00AM +, Kenichi Oomichi wrote:
Now we are working for adding Nova API responses checks to Tempest[1] to
block
# Sorry for sending this again, previous mail was unreadable.
2014-04-28 11:54 GMT+09:00 Ken'ichi Ohmichi ken1ohmi...@gmail.com:
This is also why there are a bunch of nova v2 extensions that just add
properties to an existing API. I think in v3 the proposal was to do this with
microversioning
lag Sunday, but the meet-up would be nice for me;-)
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
Since this is the scheduled off week, I'm going to cancel this week's
Nova API meeting.
The next meeting will be on May 8th and will be at 00:00 UTC.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
, I don't
have strong opinion for including the validation also. These schemas will be
large sometimes and the combination in the same patch would make reviews
difficult. In current Nova API test implementations, we are separating them
into different patches.
Thanks
Ken'ichi Ohmichi
/nova/tree/master/nova/api/openstack/compute/schemas/v3
These schemas are used only for Nova v3 API, there is nothing for v2
API(current) because
v2 API does not use jsonschema.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev
the issue?
Yes, that would fix the issue.
Thanks for considering.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
will
be caught which is the desired behavior from tempest here.
Yes, right. Thanks for clarify it.
I have not found enough idea for this yet.
Thanks Matt,
I have gotten one idea for it!
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
the interoperability should depend on v2
API, that seems
sandbox.. (I know that it is a little overstatement, but we have found
a lot of this kind
of problem already..)
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev
Hi Chris,
Thanks for your info, I got it.
That is a quick response and enough for me:-)
Thanks
Ken'ichi Ohmichi
---
2014-02-13 Christopher Yeoh cbky...@gmail.com:
Hi Kenichi,
Ah yes, it was decided at the mid cycle meetup to delay the nova network
changes
until Juno. Sorry I should have
the deserializing rule.
Thanks
Ken'ichi Ohmichi
---
On 2014年01月13日 22:38, Sean Dague wrote:
I know we've been here before, but I want to raise this again while there
is still time left in icehouse.
I would like to propose that the Nova v3 API removes the XML payload
entirely. It adds complexity
for the negative test generator. It would be necessary to hard-code
API schemas in Tempest.
Thanks
Ken'ichi Ohmichi
---
The negative test patch in the shared fork
https://github.com/mkoderer/tempest/tree/feature/negative_tests defines such
a schema. The tempest patch will be updated from
to release new WSME which includes new type classes?
I'd like to try applying these classes to Ceilometer after the release because
Ceilometer is the best for showing these classes' usage.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev
provide API definitions through API with jsonschema format, but
Nova does not have such feature.
We need to port these API schema from Nova to Tempest, I guess. right?
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev
Hi Sean,
That is good idea, I also am in.
BTW, what time will this work start?
I tried to join this kind of work, but I could not find anyone on IRC
in my timezone.
Thanks
Ken'ichi Ohmichi
2014/1/9 Sean Dague s...@dague.net:
On 01/09/2014 08:01 AM, Thierry Carrez wrote:
Sean Dague wrote
://review.openstack.org/#/c/59616/1/nova/api/openstack/compute/schemas/v3/agents_schema.py
Thanks
Ken'ichi Ohmichi
---
2013/12/7 David Kranz dkr...@redhat.com:
On 11/13/2013 06:09 PM, Christopher Yeoh wrote:
On Thu, Nov 14, 2013 at 7:52 AM, David Kranz dkr...@redhat.com wrote:
On 11/13/2013 08:30 AM
.
Thank you for pointing this bp out.
I added the etherpad link Ken'ichi pointed to this bp. Ken'ichi, should you
be the owner of this bp?
Unfortunately, I could not change the items of this bp from my
launchpad account.
Could you be the owner?
Thanks
Ken'ichi Ohmichi
---
On Tue, Dec 3, 2013
://status.openstack.org/elastic-recheck/
Thank you for the info, that is interesting.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
this problem 4 times, but I am not sure this is
worth or not.
Thanks
Ken'ichi Ohmichi
---
2) https://bugs.launchpad.net/bugs/1251784
neutron, Nova
328 Hits
3) https://bugs.launchpad.net/bugs/1249065
neutron
122 hits
4) https://bugs.launchpad.net/bugs/1251448
neutron
65 Hits
Raw Data
check this contents before starting this work.
Thanks
Ken'ichi Ohmichi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
] Review request: Blurprint of API
validation
On Fri, Aug 2, 2013 at 4:35 PM, Russell Bryant rbry...@redhat.com wrote:
On 07/09/2013 07:45 AM, Ken'ichi Ohmichi wrote:
Hi,
The blueprint nova-api-validation-fw has not been approved yet.
I hope
://review.openstack.org/#/c/25358/
Thanks,
Ken'ichi Ohmichi
---
On Tue, 16 Jul 2013 13:37:15 +0900
Ken'ichi Ohmichi oomi...@mxs.nes.nec.co.jp wrote:
Hi Russell,
I assigned you as the approver of bp nova-api-validation-fw,
so could you take a look at this bp?
You have changed the priority from
Hi Russell,
I assigned you as the approver of bp nova-api-validation-fw,
so could you take a look at this bp?
You have changed the priority from Medium to Low these days.
Could you show your concerns about this bp if you have.
Thanks
Ken'ichi Ohmichi
---
On Tue, 9 Jul 2013 20:45:57 +0900
web framework(e.g. Pecan/WSME) in the future, we
will be able to use this framework.
Thanks
Ken'ichi Ohmichi
---
On Fri, 5 Jul 2013 16:27:39 +0900
Ken'ichi Ohmichi oomi...@mxs.nes.nec.co.jp wrote:
Hi,
I have submitted a blueprint[1] and a patch[2] for Nova API validation.
I request
://lists.openstack.org/pipermail/openstack-dev/2013-June/009970.html
- http://lists.openstack.org/pipermail/openstack-dev/2013-June/010057.html
[4]: http://lists.openstack.org/pipermail/openstack-dev/2013-June/010814.html
Thanks
Ken'ichi Ohmichi
working fine.
I have written it on https://etherpad.openstack.org/NovaApiValidationFramework
I think each project can select original WSME validation or jsonschema by its
necessity, when each project moves to Pecan/WSME in the future.
Thanks
Ken'ichi Ohmichi
201 - 240 of 240 matches
Mail list logo