Hi everyone,
I'd like to announce my candidacy for PTL of the Quality Assurance
team for the Newton release cycle. I have joined into the OpenStack
community since 2012 as a developer, and you can see my activities on
the following metric:
* Review: http://stackalytics.com/?release=all&user_id=
Hi David,
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Wednesday, February 25, 2015 4:19 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova][Tempest] Tempest will deny extra
> properties on Nova v2/v2.1
> -Original Message-
> From: Roman Podoliaka [mailto:rpodoly...@mirantis.com]
> Sent: Friday, January 30, 2015 2:12 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [api][nova] Openstack HTTP error codes
>
> Hi Anne,
>
> I think Eugeniya
> -Original Message-
> From: Michael Still [mailto:mi...@stillhq.com]
> Sent: Wednesday, January 28, 2015 7:41 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [nova] Nominating Melanie Witt for
> python-novaclient-core
>
> Greetings,
>
> I would like to nominate Me
Hi David,
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Wednesday, January 14, 2015 4:25 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [QA] Moving tempest clients to tempest-lib (was
> Meeting Thursday January 8th at 22:00 UTC)
>
On 2014/12/11 6:41, Michael Still wrote:
> Hi,
>
> at the design summit we said that we would not approve specifications
> after the kilo-1 deadline, which is 18 December. Unfortunately, we’ve
> had a lot of specifications proposed this cycle (166 to my count), and
> haven’t kept up with the revi
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: Monday, November 24, 2014 10:57 PM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [all] removing XML testing completely from Tempest
>
> Having XML payloads was never a universal part of OpenStack
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Wednesday, November 19, 2014 7:52 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Do we need to add xml support for new API
> extensions on v2 API ?
>
> On Wed, 19 Nov 2014 13
> -Original Message-
> From: Carl Baldwin [mailto:c...@ecbaldwin.net]
> Sent: Tuesday, November 18, 2014 9:35 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] Stale patches
>
> +1. I always hesitate to abandon someone's patch b
Hi Amit,
Thanks for picking this topic up,
Honestly I don't have a strong opinion about validation libraries.
Each project implements based on different web frameworks and
the options of validation libraries would be limited from its web
framework. For example, Nova implements its own wsgi framew
> -Original Message-
> From: Chris Friesen [mailto:chris.frie...@windriver.com]
> Sent: Saturday, October 04, 2014 1:27 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [all][docs][tc] How to scale Documentation
>
> On 10/03/2014 07:50 PM, Anne Gentle wrote:
>
>
> -Original Message-
> From: Brant Knudson [mailto:b...@acm.org]
> Sent: Thursday, October 02, 2014 10:55 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
> implementation
>
>> Thanks for your advice,
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Thursday, September 25, 2014 12:32 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] [All] API standards working group
>
> On Wed, 24 Sep 2014 16:48:43
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Wednesday, September 24, 2014 1:09 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
> implementation
>
> > (1) Input/Output attribute names
> > (1.1) The
> -Original Message-
> From: Brant Knudson [mailto:b...@acm.org]
> Sent: Thursday, September 25, 2014 12:04 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
> implementation
>
>
> vNext
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Wednesday, September 24, 2014 7:19 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] [All] API standards working group
>
> On 09/23/2014 05:03 PM, Rochelle.RochelleGrober wrote:
> > ja
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Wednesday, September 24, 2014 12:47 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
> implementation
>
> On 09/22/2014 04:27 PM, Brant Knudson wrote:
>
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Tuesday, September 23, 2014 7:39 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] Some ideas for micro-version
> implementation
>
> On Mon, 22 Sep 20
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Tuesday, September 23, 2014 7:50 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all] REST API style guide (Re: [Nova] Some
> ideas for micro-version imple
> -Original Message-
> From: Alex Xu [mailto:x...@linux.vnet.ibm.com]
> Sent: Tuesday, September 23, 2014 12:20 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all] REST API style guide (Re: [Nova] Some
> ideas for micro-version implem
> -Original Message-
> From: Day, Phil [mailto:philip@hp.com]
> Sent: Friday, September 19, 2014 7:08 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] are we going to remove the novaclient v3
> shell or what?
>
>
> > >
> > >
Hi Alex,
Thank you for doing this.
> -Original Message-
> From: Alex Xu [mailto:x...@linux.vnet.ibm.com]
> Sent: Friday, September 19, 2014 3:40 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [Nova] Some ideas for micro-version implementation
>
> Close to Kilo, it
> -Original Message-
> From: Ken'ichi Ohmichi [mailto:ken1ohmi...@gmail.com]
> Sent: Thursday, September 18, 2014 10:16 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] are we going to remove the novaclient v3
> shell or what?
> >>
> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Wednesday, September 17, 2014 11:59 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [nova] are we going to remove the novaclient v3
> shell or what?
>
Hi Chris,
Thanks for bring it up here,
> -Original Message-
> From: Chris St. Pierre [mailto:stpie...@metacloud.com]
> Sent: Saturday, September 13, 2014 2:53 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [nova] Expand resource name allowed characters
>
> We have
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Tuesday, September 09, 2014 4:29 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] Kilo Cycle Goals Exercise
>
> > 3. Another long-term topic is standardizing our APIs so that we use
> > con
> -Original Message-
> From: John Garbutt [mailto:j...@johngarbutt.com]
> Sent: Monday, July 21, 2014 6:54 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] [Spec freeze exception] Instance tasks
>
> On 18 July 2014 14:28, Andrew L
+1
Andrea has already worked well for Tempest.
Thanks
Ken'ichi Ohmichi
---
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Tuesday, July 22, 2014 7:34 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [QA] Proposed Changes to Tempe
; adding new tests
>
> On Tue, Jun 17, 2014 at 01:45:55AM +, Kenichi Oomichi wrote:
> >
> > > -Original Message-
> > > From: Matthew Treinish [mailto:mtrein...@kortar.org]
> > > Sent: Monday, June 16, 2014 11:58 PM
> > > To: OpenStack De
Hi,
Chris will have day off tomorrow.
I'd like to run the next meeting instead.
Just a reminder that the weekly Nova API meeting is being held tomorrow
Friday UTC .
We encourage cloud operators and those who use the REST API such as
SDK developers and others who and are interested in the fu
> -Original Message-
> From: Michael Still [mailto:mi...@stillhq.com]
> Sent: Wednesday, June 18, 2014 7:54 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core
>
> Kenichi has now been added
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Monday, June 16, 2014 11:58 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [qa] Clarification of policy for qa-specs around
> adding new tests
>
> On
Hi David,
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Monday, May 19, 2014 6:49 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [qa][nova] Status of v3 tests in tempest
>
> It seems the nova team decided in Atlanta that "v3" as curren
Hi,
In Tempest, there is a lot of copy&paste test code for Nova v2/v3 API tests.
In addition, we need to add many checks for API test coverage.
As the result, now we should apply the same changes to v2 and v3 tests.
To avoid these redundant changes, we started bp/nova-api-test-inheritance[1]
tas
Hi Matthew,
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Friday, May 02, 2014 12:36 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all] Branchless Tempest QA Spec - final draft
>
> > > When addi
Hi David,
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Friday, May 02, 2014 2:30 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [all] Branchless Tempest QA Spec - final draft
>
> > The verify_tempest_conf
Hi Michael,
Thanks for the schedule draft.
I'd like to pick one comment about it.
Now sessions related to Nova v3 API are scheduled like:
- 5:20pm May 14: "Nova V3 API"
- 5:00pm May 15: "Nova V2 on V3 API implementation POC"
but "Nova V3 API" session needs some inputs from "Nova V2 on V3 API
Hi,
Sorry for my late response, but I'd like to discuss this again.
Now we are working for adding Nova API responses checks to Tempest[1] to
block backward incompatible changes.
With this work, Tempest checks each response(status code, response body)
and raises a test failure exception if detect
Hi,
Chris has these days off now.
I'd like to run the next meeting instead.
Just a reminder that the weekly Nova API meeting is being held tomorrow
Friday UTC .
We encourage cloud operators and those who use the REST API such as
SDK developers and others who and are interested in the future
> -Original Message-
> From: Michael Still [mailto:mi...@stillhq.com]
> Sent: Thursday, April 24, 2014 8:10 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] [qa] EC2 status and call for assistance
>
> On Thu, Apr 24, 2014 at 7:39
Hi Matthew,
Thanks for doing this,
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Saturday, April 19, 2014 11:59 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [QA] qa-specs Repo and QA Program Juno Blueprint
> Review Process
>
Hi David,
Thanks for pointing it up.
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Saturday, April 19, 2014 4:16 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [nova][qa] Compatibility of extra values returned in
> json dicts and head
Hi,
We are using a google spreadsheet for managing new Nova API tests of Tempest.
https://docs.google.com/spreadsheet/ccc?key=0AmYuZ6T4IJETdEVNTWlYVUVOWURmOERSZ0VGc1BBQWc#gid=2
When creating a new Nova API test, please see the spreadsheet to avoid the
conflicted work. We can create a test which "a
Hi,
Chris has some days off now.
I'd like to run the next meeting instead.
Just a reminder that the weekly Nova API meeting is being held tomorrow
Friday UTC .
We encourage cloud operators and those who use the REST API such as
SDK developers and others who and are interested in the future
2 API from Tempest?
>
> On Thu, Apr 3, 2014 at 8:16 PM, Sean Dague wrote:
>
>
> On 04/02/2014 10:55 PM, Kenichi Oomichi wrote:
> > Hi,
> >
> > The XML support of Nova v2 API is marked as deprecated, and the
> message is
> >
Hi,
The XML support of Nova v2 API is marked as deprecated, and the message is
'XML support has been deprecated and will be removed in the Juno release.'
with https://review.openstack.org/#/c/75439
Now we are in Juno cycle, so can we remove these tests from Tempest?
If doing it, the gate testing
Hi,
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Thursday, March 27, 2014 9:16 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] Nova API meeting
>
> Hi,
>
> Just a reminder that the weekly Nova API meeting is being held tomorrow
>
Hi,
We need to know what Nova APIs are used by each SDK.
Could SDK developers/users/someone write them on the below spreadsheet?
https://docs.google.com/spreadsheet/ccc?key=0AvimqlvxcSGGdGxYSVJQb2tic25wUmFkcDJFV25OSUE#gid=2
I have written SDK names on the spreadsheet from
https://wiki.open
Hi Chris,
Thank you for picking it up,
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Thursday, March 13, 2014 1:56 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [qa][tempest] Where to do response body validation
>
> The new tem
;
> On 03/11/2014 09:48 AM, Kenichi Oomichi wrote:
> >
> >> -Original Message-
> >> From: Sean Dague [mailto:s...@dague.net]
> >> Sent: Tuesday, March 11, 2014 10:06 PM
> >> To: OpenStack Development Mailing List
> >> Subject: [openst
Hi Sean,
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: Tuesday, March 11, 2014 10:06 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [qa] Tempest review and development priorities until
> release
>
> Tempest has no feature freeze in the s
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Friday, March 07, 2014 9:46 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [Nova] API weekly meeting
>
> Hi,
>
> I'd like to start a weekly IRC meeting for those interested in
> discus
Hi David,
That is an interesting idea, I'd like to join in :-)
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Wednesday, March 05, 2014 3:31 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [qa][nova] Ownership and path to schema definit
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Wednesday, March 05, 2014 10:52 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API
>
> On Wed, 2014-03-05 at 05:43 +,
Hi,
I am working for Nova API tests in Tempest, and I'd like to ask
opinions about the ways.
Tempest generates a request and sends it to each RESTful API.
Then Tempest receives a response from the API and verifies the
response.
>From the viewpoint of the backward compatibility, it is important
t
> -Original Message-
> From: Dan Smith [mailto:d...@danplanet.com]
> Sent: Wednesday, March 05, 2014 9:09 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API
>
> > What I'd like to do next is work
> -Original Message-
> From: Russell Bryant [mailto:rbry...@redhat.com]
> Sent: Tuesday, March 04, 2014 7:31 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API
>
> On 03/03/2014 04:25 PM, Vishvananda Ishaya wrote:
> > This
> -Original Message-
> From: Alex Xu [mailto:x...@linux.vnet.ibm.com]
> Sent: Thursday, February 27, 2014 11:44 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Future of the Nova API
>
> On 2014年02月26日 18:40, Thierry Carrez wrote
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Wednesday, February 26, 2014 11:33 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Future of the Nova API
>
> On Tue, 25 Feb 2014 09:26:09 -0500
> Sean Dague wrote:
> >
> > W
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Tuesday, February 25, 2014 6:35 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] Future of the Nova API
>
> > - twice the code
> > - different enough
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sent: Thursday, February 20, 2014 11:44 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Nova] v3 API in Icehouse
>
> On Wed, 19 Feb 2014 12:36:46 -0500
> Russell Bryant wrote:
>
> > Gree
Hi Chris,
Is it OK to postpone nova-network v3 APIs until Juno release?
I guess that because some nova-network v3 API patches are abandoned today.
I'd just like to make it clear.
Thanks
Ken'ichi Ohmichi
---
> -Original Message-
> From: Christopher Yeoh [mailto:cbky...@gmail.com]
> Sen
pport
>
> Similar capabilities are being introduced here:
> https://review.openstack.org/#/c/61839/
> <https://review.openstack.org/#/c/61839/>
Thank you for the info.
That is very interesting patch and bp.
I will see it more deeply.
Thanks
Ken'ichi Ohmichi
---
> From:
Hi Doug,
> -Original Message-
> From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
> Sent: Thursday, February 06, 2014 11:55 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] WSME 0.6 released
>
> I have just tagged WSME 0.6. It is now on PyPI, and should be pi
Thu, 6 Feb 2014 13:38:22 +
> Kenichi Oomichi wrote:
>
> >
> > Hi,
> >
> > I'd like to propose one idea that autogenerates API sample files from
> > API schema for Nova v3 API.
> >
> > We are working on API validation for v3 API, the works
Hi,
I'd like to propose one idea that autogenerates API sample files from API
schema for Nova v3 API.
We are working on API validation for v3 API, the works require API schema
which is defined with JSONSchema for each API. On the other hand, API sample
files of v3 API are autogenerated from the
Hi,
There is a blueprint ECU[1], and that is an interesting idea for me.
so I'd like to know the comments about ECU idea.
After production environments start, the operators will need to add
compute nodes before exhausting the capacity.
On the scenario, they'd like to add cost-efficient machines a
Hi Jeremy,
> -Original Message-
> From: Jeremy Stanley [mailto:fu...@yuggoth.org]
> Sent: Saturday, January 25, 2014 7:52 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Infra] Question about disk partition
>
> On 2014-01-23 13:55:21 -0800 (-0800), Andrew Woodw
Hi,
I am investigating a gate failure(#1).
On some sample(#2), "create server" continued to fail due to "No space left on
device".
Is it possible to extend the root partition?
On the above sample, the fisrt IOError happened when writing a tempfile under
/var/cache/nova directory:
File
"/opt/
> -Original Message-
> From: Kurt Griffiths [mailto:kurt.griffi...@rackspace.com]
> Sent: Saturday, January 18, 2014 4:47 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [wsme] Undefined attributes in WSME
>
> FWIW, I believe Nova is loo
Hi,
> -Original Message-
> From: Sean Dague [mailto:s...@dague.net]
> Sent: Thursday, January 16, 2014 4:54 AM
> To: Daniel P. Berrange; OpenStack Development Mailing List (not for usage
> questions)
> Subject: Re: [openstack-dev] [devstack] libvirt default log level
>
> On 01/15/2014 0
> On Mon, Jan 13, 2014 at 9:52 PM, Kenichi Oomichi
> wrote:
>
>
>
> Hi Doug,
>
>
> > -Original Message-
> > From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
> > Sent: Tuesday, January 14, 2014 12:07 AM
>
Hi Doug,
> -Original Message-
> From: Doug Hellmann [mailto:doug.hellm...@dreamhost.com]
> Sent: Tuesday, January 14, 2014 12:07 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [wsme] Undefined attributes in WSME
>
>
>
>
> On Mon, J
Hi Gray,
This problem is https://bugs.launchpad.net/nova/+bug/1266711 .
The thread is
http://lists.openstack.org/pipermail/openstack-dev/2014-January/023575.html .
Thanks
Ken'ichi Ohmichi
---
> -Original Message-
> From: Gary Kotton [mailto:gkot...@vmware.com]
> Sent: Tuesday, Januar
Hi,
> -Original Message-
> From: Adalberto Medeiros [mailto:adal...@linux.vnet.ibm.com]
> Sent: Friday, December 06, 2013 11:18 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [qa][tempest] Bug triage and monitoring process
>
> Hello all!
>
> Yesterday, during the
Hi Matthew,
Thank you for picking this up.
> -Original Message-
> From: Matthew Treinish [mailto:mtrein...@kortar.org]
> Sent: Thursday, December 05, 2013 6:04 AM
> To: openstack-dev@lists.openstack.org
> Subject: [openstack-dev] [qa] Moving the QA meeting time
>
> Hi everyone,
>
> I'm
t; IBM Brazil
> Email: adal...@linux.vnet.ibm.com
>
> On Mon 02 Dec 2013 07:36:38 AM BRST, Kenichi Oomichi wrote:
> >
> > Hi Adalberto,
> >
> >> -Original Message-
> >> From: Adalberto Medeiros [mailto:adal...@linux.vnet.ibm.com]
> >&
Hi Adalberto,
> -Original Message-
> From: Adalberto Medeiros [mailto:adal...@linux.vnet.ibm.com]
> Sent: Saturday, November 30, 2013 11:29 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [tempest] list of negative tests that need to be
> separated from other tests
Hi,
I was glad to meet OpenStack developers in the summit,
and I am interested in this topic.
> -Original Message-
> From: David Kranz [mailto:dkr...@redhat.com]
> Sent: Wednesday, November 13, 2013 4:33 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [qa] morato
API
>
> On Mon, Oct 21, 2013 at 7:14 AM, Kenichi Oomichi
> wrote:
>>
>> Some validation features seem necessary as basic features for Nova APIs.
>> so I am trying to pick necessary features for WSME on the following
>> inline messages.
>>
>> Could
Hi Doug,
Thank you for your advice.
Some validation features seem necessary as basic features for Nova APIs.
so I am trying to pick necessary features for WSME on the following
inline messages.
Could you check them?
> -Original Message-
> From: Doug Hellmann [mailto:doug.hellm...@dream
Hi,
# I resend this because gmail distinguished my previous mail as spam one..
I'd like to know what validation feature is really needed for Nova v3 API,
and I hope this mail will be a kick-off of brain-storming for it.
<< Introduction >>
I have submitted a blueprint "nova-api-validation-fw".
T
Hi,
I'd like to know what validation feature is really needed for Nova v3 API,
and I hope this mail will be a kick-off of brain-storming for it.
<< Introduction >>
I have submitted a blueprint "nova-api-validation-fw"[1].
The purpose is comprehensive validation of API input parameters.
32% of No
83 matches
Mail list logo
