[openstack-dev] [nova] Nova API meeting

2014-08-14 Thread Christopher Yeoh
Hi, 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 of the API to participate. In other timezones the meeting is at: EST

Re: [openstack-dev] [all] 3rd Party CI vs. Gerrit

2014-08-14 Thread Christopher Yeoh
On Wed, 13 Aug 2014 18:52:05 -0400 Jay Pipes jaypi...@gmail.com wrote: On 08/13/2014 06:35 PM, Russell Bryant wrote: On 08/13/2014 06:23 PM, Mark McLoughlin wrote: On Wed, 2014-08-13 at 12:05 -0700, James E. Blair wrote: cor...@inaugust.com (James E. Blair) writes: Sean Dague

Re: [openstack-dev] [QA] Picking a Name for the Tempest Library

2014-08-18 Thread Christopher Yeoh
On Sat, 16 Aug 2014 18:27:19 +0200 Marc Koderer m...@koderer.com wrote: Hi all, Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com: I suggest that tempest should be the name of the import'able library, and that the integration tests themselves should be what is pulled out of

Re: [openstack-dev] [nova] Server Group API: add 'action' to authorizer?

2014-08-23 Thread Christopher Yeoh
On Sat, 23 Aug 2014 03:56:27 -0500 Joe Cropper cropper@gmail.com wrote: Hi Folks, Would anyone be opposed to adding the 'action' checking to the v2/v3 authorizers? This would allow administrators more fine-grained control over who can read vs. create/update/delete server groups.

[openstack-dev] [nova] Nova API meeting

2014-08-28 Thread Christopher Yeoh
Hi, 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 of the API to participate. In other timezones the meeting is at: EST

Re: [openstack-dev] [qa] Lack of consistency in returning response from tempest clients

2014-08-29 Thread Christopher Yeoh
On Fri, 29 Aug 2014 11:13:39 -0400 David Kranz dkr...@redhat.com wrote: On 08/29/2014 10:56 AM, Sean Dague wrote: On 08/29/2014 10:19 AM, David Kranz wrote: While reviewing patches for moving response checking to the clients, I noticed that there are places where client methods do not

[openstack-dev] [nova] FFE request v2-on-v3-api

2014-09-04 Thread Christopher Yeoh
Hi, I'd like to request a FFE for 4 changesets from the v2-on-v3-api blueprint: https://review.openstack.org/#/c/113814/ https://review.openstack.org/#/c/115515/ https://review.openstack.org/#/c/115576/ https://review.openstack.org/#/c/11/ They have all already been approved and were in the

Re: [openstack-dev] [Nova] [FFE] alternative request for v2-on-v3-api

2014-09-04 Thread Christopher Yeoh
On Thu, 4 Sep 2014 23:08:09 +0900 Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: Hi I'd like to request FFE for v2.1 API patches. This request is different from Christopher's one. His request is for the approved patches, but this is for some patches which are not approved yet.

Re: [openstack-dev] [Nova][FFE] v3-api-schema

2014-09-04 Thread Christopher Yeoh
On Thu, 4 Sep 2014 22:30:51 +0900 Ken'ichi Ohmichi ken1ohmi...@gmail.com 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://review.openstack.org/#/c/103436/

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Christopher Yeoh
On Thu, 4 Sep 2014 11:24:29 +0100 Daniel P. Berrange berra...@redhat.com wrote: - A fairly significant amount of nova code would need to be considered semi-stable API. Certainly everything under nova/virt and any object which is passed in/out of the virt driver API. Changes to such

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

2014-09-05 Thread Christopher Yeoh
On Thu, 4 Sep 2014 12:57:57 -0700 Joe Gordon joe.gord...@gmail.com wrote: Overall I do think we need to re-think how the review burden is distributed. That being said, this is a nice proposal but I am not sure if it moves the review burden around enough or is the right approach. Do you have

Re: [openstack-dev] [nova] FFE server-group-quotas

2014-09-05 Thread Christopher Yeoh
I'm willing to sponsor this Chris — Sent from Mailbox On Fri, Sep 5, 2014 at 10:29 PM, Day, Phil philip@hp.com wrote: Hi, I'd like to ask for a FFE for the 3 patchsets that implement quotas for server groups. Server groups (which landed in Icehouse) provides a really useful

[openstack-dev] [nova] Nova API meeting

2014-09-11 Thread Christopher Yeoh
Hi, 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 of the API to participate. In other timezones the meeting is at: EST

Re: [openstack-dev] [nova] are we going to remove the novaclient v3 shell or what?

2014-09-17 Thread Christopher Yeoh
On Wed, 17 Sep 2014 17:42:30 + Day, Phil philip@hp.com wrote: I think in the hopefully not too distant future we'll be able to make the v1_1 client handle both V2 and V2.1 (who knows. Maybe we can even rename it v2) - and that's what we should do because it will prove if we have full

[openstack-dev] [nova] Nova API meeting

2014-09-18 Thread Christopher Yeoh
Hi, 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 of the API to participate. In other timezones the meeting is at: EST

Re: [openstack-dev] [nova] Expand resource name allowed characters

2014-09-18 Thread Christopher Yeoh
On Sat, 13 Sep 2014 06:48:19 -0400 Sean Dague s...@dague.net wrote: On 09/13/2014 02:28 AM, Kenichi Oomichi wrote: 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

Re: [openstack-dev] [nova] Expand resource name allowed characters

2014-09-18 Thread Christopher Yeoh
On Thu, 18 Sep 2014 13:45:42 +0200 Flavio Percoco fla...@redhat.com wrote: On 09/18/2014 01:28 PM, Sean Dague wrote: On 09/18/2014 07:19 AM, Ken'ichi Ohmichi wrote: 2014-09-18 19:57 GMT+09:00 Sean Dague s...@dague.net: On 09/18/2014 06:38 AM, Christopher Yeoh wrote: On Sat, 13 Sep 2014

Re: [openstack-dev] [Nova] Some ideas for micro-version implementation

2014-09-23 Thread Christopher Yeoh
On Mon, 22 Sep 2014 09:29:26 + Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote: Before discussing how to implement, I'd like to consider what we should implement. IIUC, the purpose of v3 API is to make consistent API with the backwards incompatible changes. Through huge discussion in

Re: [openstack-dev] [Nova] Some ideas for micro-version implementation

2014-09-23 Thread Christopher Yeoh
On Mon, 22 Sep 2014 09:47:50 -0500 Anne Gentle a...@openstack.org wrote: (1) Input/Output attribute names (1.1) These names should be snake_case. eg: imageRef - image_ref, flavorRef - flavor_ref, hostId - host_id (1.2) These names should contain extension names if they are provided

Re: [openstack-dev] [Nova] Some ideas for micro-version implementation

2014-09-23 Thread Christopher Yeoh
On Mon, 22 Sep 2014 15:27:47 -0500 Brant Knudson b...@acm.org wrote: Did you consider JSON Home[1] for this? For Juno we've got JSON Home support in Keystone for Identity v3 (Zaqar was using it already). We weren't planning to use it for microversioning since we weren't planning on doing

Re: [openstack-dev] [all] REST API style guide (Re: [Nova] Some ideas for micro-version implementation)

2014-09-23 Thread Christopher Yeoh
On Tue, 23 Sep 2014 09:00:26 +0900 Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote: \ So how about just using HTTP 200(OK) only for status codes? That would give up providing accurate internal status to clients but backwards backwards incompatibilities never happen. No I think that we should

Re: [openstack-dev] [Nova] [All] API standards working group

2014-09-23 Thread Christopher Yeoh
On Tue, 23 Sep 2014 18:18:56 -0400 Jay Pipes jaypi...@gmail.com wrote: On 09/23/2014 05:03 PM, Rochelle.RochelleGrober wrote: jaypi...@gmail.com mailto:jaypi...@gmail.com on Tuesday, September 23, 2014 9:09 AM wrote: _Snip I'd like to say

Re: [openstack-dev] [Nova] New API requirements, review of GCE

2013-12-10 Thread Christopher Yeoh
On Tue, Dec 10, 2013 at 11:36 PM, Alexandre Levine alev...@cloudscaling.com wrote: Russell, I'm a little confused about importing it into stackforge repository. Please clarify it for me. Right now our code is a part of nova itself, adding lots of files and changing several of existing,

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-11 Thread Christopher Yeoh
On Thu, Dec 12, 2013 at 7:11 AM, Ryan Petrello ryan.petre...@dreamhost.comwrote: Hello, I’ve spent the past week experimenting with using Pecan for Nova’s API, and have opened an experimental review: https://review.openstack.org/#/c/61303/6 …which implements the `versions` v3 endpoint

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-11 Thread Christopher Yeoh
On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann doug.hellm...@dreamhost.comwrote: On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello ryan.petre...@dreamhost.com wrote: Hello, I’ve spent the past week experimenting with using Pecan for Nova’s API, and have opened an experimental review:

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-12 Thread Christopher Yeoh
On Thu, Dec 12, 2013 at 3:17 PM, Mike Perez thin...@gmail.com wrote: On 10:06 Thu 12 Dec , Christopher Yeoh wrote: On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann doug.hellm...@dreamhost.comwrote: So for compatibility testing I think what will probably happen is that we'll

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-12 Thread Christopher Yeoh
On Fri, Dec 13, 2013 at 8:12 AM, Jonathan LaCour jonathan-li...@cleverdevil.org wrote: On December 11, 2013 at 2:34:07 PM, Doug Hellmann ( doug.hellm...@dreamhost.com) wrote: On Wed, Dec 11, 2013 at 3:41 PM, Ryan Petrello wrote: 1. It looks like the Nova v3 API is composed *entirely*

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-12 Thread Christopher Yeoh
On Fri, Dec 13, 2013 at 4:12 AM, Jay Pipes jaypi...@gmail.com wrote: On 12/11/2013 11:47 PM, Mike Perez wrote: On 10:06 Thu 12 Dec , Christopher Yeoh wrote: On Thu, Dec 12, 2013 at 8:59 AM, Doug Hellmann doug.hellm...@dreamhost.com mailto:doug.hellm...@dreamhost.comwrote: On Wed

Re: [openstack-dev] [OpenStack-dev] How to modify a bug across multiple repo?

2013-12-13 Thread Christopher Yeoh
Hi wu jiang, On Wed, Dec 11, 2013 at 12:26 PM, wu jiang win...@gmail.com wrote: Hi Chris Rob, Thanks for your reply ,and sorry for my late response.. - I tested again. The modification won't effect tempest test because it's an optional argument, so I can commit it later in tempest.

Re: [openstack-dev] [qa][ceilometer] Who can be a asked to help review tempest tests?

2013-12-17 Thread Christopher Yeoh
On Tue, Dec 17, 2013 at 8:33 PM, Nadya Privalova nprival...@mirantis.comwrote: Hi David, I'm working on tempest tests for Ceilometer too. I think this thread is a good place to make a reminder about our strategy how to avoid duplications in change requests. 1. We have something like a test

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-18 Thread Christopher Yeoh
:55 AM, Christopher Yeoh cbky...@gmail.com wrote: On Sat, Dec 14, 2013 at 8:48 AM, Doug Hellmann doug.hellm...@dreamhost.com wrote: That covers routes. What about the properties of the inputs and outputs? I think the best way for me to describe it is that as the V3 API core and all

Re: [openstack-dev] [Nova] Support for Pecan in Nova

2013-12-18 Thread Christopher Yeoh
ryan.petre...@dreamhost.com On Dec 14, 2013, at 10:45 AM, Doug Hellmann doug.hellm...@dreamhost.com wrote: On Sat, Dec 14, 2013 at 7:55 AM, Christopher Yeoh cbky...@gmail.com wrote: On Sat, Dec 14, 2013 at 8:48 AM, Doug Hellmann doug.hellm...@dreamhost.com wrote

Re: [openstack-dev] [Nova] Future meeting times

2013-12-22 Thread Christopher Yeoh
On Thu, Dec 19, 2013 at 12:59 AM, Russell Bryant rbry...@redhat.com wrote: Greetings, The weekly Nova meeting [1] has been held on Thursdays at 2100 UTC. I've been getting some requests to offer an alternative meeting time. I'd like to try out alternating the meeting time between two

Re: [openstack-dev] [Ceilometer][Tempest]Tracking of blueprints and changes

2013-12-27 Thread Christopher Yeoh
On Fri, Dec 27, 2013 at 8:57 PM, Nadya Privalova nprival...@mirantis.comwrote: Hello guys! I hope all of you are enjoying the holidays! But I'd like to raise a Tempest question. Again. I hope this email will not be lost after vacations :) After the summit we decided to track all tests that

Re: [openstack-dev] [nova] minimum review period for functional changes that break backwards compatibility

2014-01-02 Thread Christopher Yeoh
On Thu, Jan 2, 2014 at 8:23 PM, Thierry Carrez thie...@openstack.orgwrote: Tim Bell wrote: - Changes in default behaviour: Always likely to affect existing systems in some way. Maybe we should have an additional type of review vote that comes from people who are recognised as

Re: [openstack-dev] [nova] minimum review period for functional changes that break backwards compatibility

2014-01-02 Thread Christopher Yeoh
On Fri, Jan 3, 2014 at 7:30 AM, Tim Bell tim.b...@cern.ch wrote: Is there a mechanism to tag changes as being potentially more appropriate for the more ops related profiles ? I'm thinking more when someone proposes a change they suspect could have an operations impact, they could highlight

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

2014-01-06 Thread Christopher Yeoh
On Tue, Jan 7, 2014 at 7:50 AM, Jon Bernard jbern...@tuxion.com wrote: Hello all, I would like to propose instance-level snapshots as a feature for inclusion in Nova. An initial draft of the more official proposal is here [1], blueprint is here [2]. In a nutshell, this feature will take

Re: [openstack-dev] [nova] where to expose network quota

2014-01-07 Thread Christopher Yeoh
On Mon, Jan 6, 2014 at 4:47 PM, Yaguang Tang yaguang.t...@canonical.comwrote: Hi all, Now Neutron has its own quota management API for network related items(floating ips, security groups .etc) which are also manged by Nova. when using nova with neutron as network service, the network

Re: [openstack-dev] Discuss the option delete_on_termination

2014-01-08 Thread Christopher Yeoh
On Thu, Jan 9, 2014 at 9:25 AM, 黎林果 lilinguo8...@gmail.com wrote: Hi All, Attach a volume when creating a server, the API contains 'block_device_mapping', such as: block_device_mapping: [ { volume_id: VOLUME_ID, device_name: /dev/vdc,

Re: [openstack-dev] Discuss the option delete_on_termination

2014-01-08 Thread Christopher Yeoh
On Thu, Jan 9, 2014 at 2:35 PM, 黎林果 lilinguo8...@gmail.com wrote: Hi Chris, Thanks for you reply. It's not only hard coded for swap volumes. In function '_create_instance' which for creating instance of nova/compute/api.py, the '_prepare_image_mapping' function will be called. And it hard

Re: [openstack-dev] [nova] Discuss the option delete_on_termination

2014-01-09 Thread Christopher Yeoh
apply this to the V3 API rather than doing an enhancement for both the V2 and V3 API. Regards, Chris 2014/1/9 Christopher Yeoh cbky...@gmail.com: On Thu, Jan 9, 2014 at 2:35 PM, 黎林果 lilinguo8...@gmail.com wrote: Hi Chris, Thanks for you reply. It's not only hard coded for swap

Re: [openstack-dev] [all] Organizing a Gate Blocking Bug Fix Day - Mon Jan 27th

2014-01-09 Thread Christopher Yeoh
On Thu, Jan 9, 2014 at 11:30 PM, Sean Dague s...@dague.net wrote: Minor correction, we're going to do this on Jan 27th, to be after the i2 push, as I don't think there is time organize this prior. So FYI Jan 27th is a public holiday in Australia (Australia Day!), but given the timezone

Re: [openstack-dev] [nova] api schema validation pattern changes

2014-01-12 Thread Christopher Yeoh
On my phone so will be very brief but perhaps the extensions extension could publish the jsonschema(s) for the extension. I think the only complicating   factor would be where extensions extend extensions but I think it's all doable. Chris — Sent from Mailbox for iPhone On Mon, Jan 13, 2014

Re: [openstack-dev] [nova] api schema validation pattern changes

2014-01-13 Thread Christopher Yeoh
, DreamHost ryan.petre...@dreamhost.com On Jan 13, 2014, at 9:23 AM, Jay Pipes jaypi...@gmail.com wrote: On Sun, 2014-01-12 at 19:52 -0800, Christopher Yeoh wrote: On my phone so will be very brief but perhaps the extensions extension could publish the jsonschema(s) for the extension. I

Re: [openstack-dev] [nova] api schema validation pattern changes

2014-01-13 Thread Christopher Yeoh
On Tue, Jan 14, 2014 at 10:59 AM, Jay Pipes jaypi...@gmail.com wrote: We don't need API extensions and they make our Compute API laughably complex and cumbersome. We should ditch entirely the concept of API extensions in our next Compute API major release. I think it way too late in the

Re: [openstack-dev] [nova] api schema validation pattern changes

2014-01-14 Thread Christopher Yeoh
On Tue, Jan 14, 2014 at 1:12 PM, Jay Pipes jaypi...@gmail.com wrote: On Tue, 2014-01-14 at 11:45 +0800, Christopher Yeoh wrote: On Tue, Jan 14, 2014 at 10:59 AM, Jay Pipes jaypi...@gmail.com wrote: We don't need API extensions and they make our Compute API laughably

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

2014-01-14 Thread Christopher Yeoh
On Mon, Jan 13, 2014 at 10:38 PM, Sean Dague s...@dague.net 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 to the Nova code, and

Re: [openstack-dev] [nova] [rfc] drop XML from v3 API entirely

2014-01-15 Thread Christopher Yeoh
On Tue, Jan 14, 2014 at 8:06 PM, Sean Dague s...@dague.net wrote: On 01/14/2014 05:17 AM, Christopher Yeoh wrote: On Mon, Jan 13, 2014 at 10:38 PM, Sean Dague s...@dague.net This skirts the run time issue, but using twice as many resources. It doesn't however address the fact that real

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

2014-01-19 Thread Christopher Yeoh
On Wed, Jan 15, 2014 at 4:56 PM, Vishvananda Ishaya vishvana...@gmail.comwrote: On Jan 14, 2014, at 2:10 PM, Jon Bernard jbern...@tuxion.com wrote: snip As you’ve defined the feature so far, it seems like most of it could be implemented client side: * pause the instance *

Re: [openstack-dev] [Ironic] Third-party drivers and testing

2014-01-19 Thread Christopher Yeoh
On Mon, Jan 20, 2014 at 6:17 AM, Devananda van der Veen devananda@gmail.com wrote: 1. each driver must adhere to the existing driver interfaces. 2. each driver must have comprehensive unit test coverage and sufficient inline documentation. 3. vendors are responsible for fixing bugs in

Re: [openstack-dev] Havana Release V3 Extensions and new features to quota

2014-01-21 Thread Christopher Yeoh
Hi Vinod, On Mon, Jan 20, 2014 at 9:47 PM, Vinod Kumar Boppanna vinod.kumar.boppa...@cern.ch wrote: Hi, My name is Vinod Kumar Boppanna and I was testing the quota part in the OpenStack Havana Release. I had installed the Havana Release in a single VM through RDO process. During testing,

Re: [openstack-dev] [OpenStack][Nova][cold migration] Why we need confirm resize after cold migration

2014-01-21 Thread Christopher Yeoh
On Mon, Jan 20, 2014 at 6:10 PM, Jay Lau jay.lau@gmail.com wrote: Hey, I have to bring up this topic again. A patch https://review.openstack.org/#/c/66101/ has been uploaded for review to resolve the cold migration auto confirm issue. One question want to get some input from you guys:

Re: [openstack-dev] [OpenStack][Nova][cold migration] Why we need confirm resize after cold migration

2014-01-21 Thread Christopher Yeoh
On Wed, Jan 22, 2014 at 1:05 PM, Jay Lau jay.lau@gmail.com wrote: 2014/1/22 Christopher Yeoh cbky...@gmail.com On Mon, Jan 20, 2014 at 6:10 PM, Jay Lau jay.lau@gmail.com wrote: Hey, I have to bring up this topic again. A patch https://review.openstack.org/#/c/66101/ has been

Re: [openstack-dev] writing comments as complete sentences

2014-01-21 Thread Christopher Yeoh
On Thu, Jan 16, 2014 at 5:35 AM, Renat Akhmerov rakhme...@mirantis.comwrote: I absolutely agree with that. Honestly, I don’t even understand why it can be different (not compliant with regular grammar rules). Comments are supposed to clarify things so they should be worded very clearly and

Re: [openstack-dev] [qa] Tempest test validation

2014-01-27 Thread Christopher Yeoh
On Fri, 24 Jan 2014 11:58:42 -0800 Franck Yelles franck...@gmail.com wrote: Hi everyone, Hi - note that the openstack-qa mailing list is no longer being used (we should really remove it!). I've CC'd your email along to openstack-dev with the [qa] tag in the subject line. I would need some

Re: [openstack-dev] Proposed Logging Standards

2014-01-27 Thread Christopher Yeoh
On Tue, Jan 28, 2014 at 12:55 AM, Sean Dague s...@dague.net wrote: On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote: Hi Sean, I'm currently working on moving away from the built-in logging to use log_config=filename and the python logging framework so that we can start shipping

Re: [openstack-dev] [Nova] Dropping XML support in the v3 compute API

2014-01-28 Thread Christopher Yeoh
On Fri, Jan 24, 2014 at 8:28 AM, Russell Bryant rbry...@redhat.com wrote: Greetings, Recently Sean Dague started some threads [1][2] about the future of XML support in Nova's compute API. Specifically, he proposed [3] that we drop XML support in the next major version of the API (v3). I

Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and beyond

2014-01-29 Thread Christopher Yeoh
On Thu, Jan 30, 2014 at 4:34 AM, Russell Bryant rbry...@redhat.com wrote: On 01/29/2014 12:45 PM, Daniel P. Berrange wrote: I was thinking of an upgrade path more akin to what users got when we removed the nova volume driver, in favour of cinder.

Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and beyond

2014-01-30 Thread Christopher Yeoh
On Thu, Jan 30, 2014 at 2:08 PM, Michael Still mi...@stillhq.com wrote: On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh cbky...@gmail.com wrote: So if nova-network doesn't go away this has implications for the V3 API as it currently doesn't support nova-network. I'm not sure that we

Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and beyond

2014-01-30 Thread Christopher Yeoh
On Fri, Jan 31, 2014 at 12:27 AM, Russell Bryant rbry...@redhat.com wrote: On 01/30/2014 08:10 AM, Christopher Yeoh wrote: On Thu, Jan 30, 2014 at 2:08 PM, Michael Still mi...@stillhq.com mailto:mi...@stillhq.com wrote: On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh cbky

Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and beyond

2014-01-30 Thread Christopher Yeoh
On Fri, Jan 31, 2014 at 3:21 AM, Dan Smith d...@danplanet.com wrote: If necessary the tasks work could be done solely as an extension, but I would really prefer to avoid that so I'll get this ball rolling quickly. I agree that doing it as a bolt-on to v3 would be significantly less

[openstack-dev] [Nova] Putting nova-network support into the V3 API

2014-01-30 Thread Christopher Yeoh
So with it now looking like nova-network won't go away for the forseable future, it looks like we'll want nova-network support in the Nova V3 API after all. I've created a blueprint for this work here: https://blueprints.launchpad.net/nova/+spec/v3-api-restore-nova-network And there is a first

Re: [openstack-dev] Ugly Hack to deal with multiple versions

2014-02-03 Thread Christopher Yeoh
On Tue, Feb 4, 2014 at 6:20 AM, Adam Young ayo...@redhat.com wrote: We have to support old clients. Old clients expect that the URL that comes back for the service catalog has the version in it. Old clients don't do version negotiation. Thus, we need an approach to not-break old clients

Re: [openstack-dev] [Nova] Putting nova-network support into the V3 API

2014-02-03 Thread Christopher Yeoh
On Tue, Feb 4, 2014 at 4:32 AM, Joe Gordon joe.gord...@gmail.com wrote: On Thu, Jan 30, 2014 at 10:45 PM, Christopher Yeoh cbky...@gmail.com wrote: So with it now looking like nova-network won't go away for the forseable future, it looks like we'll want nova-network support in the Nova V3

Re: [openstack-dev] [Nova] Putting nova-network support into the V3 API

2014-02-04 Thread Christopher Yeoh
On Tue, 04 Feb 2014 11:37:29 +0100 Thierry Carrez thie...@openstack.org wrote: Christopher Yeoh wrote: On Tue, Feb 4, 2014 at 12:03 PM, Joe Gordon joe.gord...@gmail.com mailto:joe.gord...@gmail.com wrote: John and I discussed a third possibility: nova-network v3 should

Re: [openstack-dev] [Nova] RFC: Generate API sample files from API schemas

2014-02-06 Thread Christopher Yeoh
On Thu, 6 Feb 2014 13:38:22 + Kenichi Oomichi oomi...@mxs.nes.nec.co.jp 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 require API schema which is defined with

Re: [openstack-dev] [nova][ceilometer] Removing simple_tenant_usage and os-instance_usage_audit_log from V3 API

2014-02-09 Thread Christopher Yeoh
On Fri, Feb 7, 2014 at 3:10 PM, Joe Gordon joe.gord...@gmail.com wrote: Hi All, I would like to propose removing the simple_tenant_usage and os-instance_usage_audit_log extensions from the nova V3 API (while keeping them in V2). Both of these are pre ceilometer extensions to generate

[openstack-dev] [nova] Possible Hyper-V false CI failures

2014-02-09 Thread Christopher Yeoh
Hi, I think the hyper-v CI system is sometimes failing with this message incorrectly: This change was unable to be automatically merged with the current state of the repository. Please rebase your change and upload a new patchset. I only mention it because its the second time I've seen it.

Re: [openstack-dev] [nova] logging wsgi requests exactly once ... issues with request usefulness

2014-02-10 Thread Christopher Yeoh
On Mon, Feb 10, 2014 at 2:56 PM, Sean Dague s...@dague.net wrote: In upstream Nova master we're currently logging ec2 wsgi requests twice, once in the paste pipeline, and once in eventlet. The following patch removes the paste pipeline portion - https://review.openstack.org/#/c/67736/

Re: [openstack-dev] [nova] logging wsgi requests exactly once ... issues with request usefulness

2014-02-10 Thread Christopher Yeoh
On Mon, Feb 10, 2014 at 3:11 PM, Sean Dague s...@dague.net wrote: On 02/10/2014 05:05 PM, Christopher Yeoh wrote: On Mon, Feb 10, 2014 at 2:56 PM, Sean Dague s...@dague.net mailto:s...@dague.net wrote: In upstream Nova master we're currently logging ec2 wsgi requests twice

Re: [openstack-dev] [Nova] Putting nova-network support into the V3 API

2014-02-12 Thread Christopher Yeoh
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] Sent: Tuesday, February 04, 2014 8:37 PM

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Christopher Yeoh
On Thu, 13 Feb 2014 15:54:23 -0500 Sean Dague s...@dague.net wrote: On 02/13/2014 09:45 AM, Dean Troyer wrote: FWIW, an early proposal to address this, as well as capability discovery, still lives at https://etherpad.openstack.org/p/api-version-discovery-proposal. I've lost track of

Re: [openstack-dev] Version Discovery Standardization

2014-02-13 Thread Christopher Yeoh
On Thu, 13 Feb 2014 21:10:01 -0500 Sean Dague s...@dague.net wrote: On 02/13/2014 08:28 PM, Christopher Yeoh wrote: On Thu, 13 Feb 2014 15:54:23 -0500 Sean Dague s...@dague.net wrote: So one question I have around a global version is what happens when we have the following situation

Re: [openstack-dev] [infra] reverify/recheck

2014-02-18 Thread Christopher Yeoh
On Tue, Feb 18, 2014 at 12:27 AM, Gary Kotton gkot...@vmware.com wrote: Thanks! That makes sense. Just odd how a -1 was received. So I think that now a check run is automatically done if the latest Jenkins run is too old (7 days?) This is done because gate failures are so costly. The check

Re: [openstack-dev] [infra] reverify/recheck

2014-02-18 Thread Christopher Yeoh
. Jenkins automatically runs check pipeline jobs after 3 days. On Tue, Feb 18, 2014 at 4:29 PM, Christopher Yeoh cbky...@gmail.com mailto:cbky...@gmail.com wrote: On Tue, Feb 18, 2014 at 12:27 AM, Gary Kotton gkot...@vmware.com mailto:gkot...@vmware.com wrote: Thanks

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-19 Thread Christopher Yeoh
and reviews for this. I would like to specifically thank Christopher Yeoh for his work here. Chris has done an *enormous* amount of work on this and deserves credit for it. He has taken on a task much bigger than anyone anticipated. Thanks, Chris! Thanks Russell, that's much appreciated. I'm

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Christopher Yeoh
. Finally, I would like to thank everyone who has helped with the effort so far. Many hours have been put in to code and reviews for this. I would like to specifically thank Christopher Yeoh for his work here. Chris has done an *enormous* amount of work on this and deserves credit

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-20 Thread Christopher Yeoh
On Thu, 20 Feb 2014 15:24:22 + John Garbutt j...@johngarbutt.com wrote: Also micro and extension versioning is not the magic bullet which will get us out of trouble in the future. Especially with the core changes. Because even though versioning allows us to make changes, for similar

Re: [openstack-dev] supported dependency versioning and testing

2014-02-20 Thread Christopher Yeoh
On Thu, 20 Feb 2014 14:45:03 -0500 Sean Dague s...@dague.net wrote: So I'm one of the first people to utter if it isn't tested, it's probably broken, however I also think we need to be realistic about the fact that if you did out the permutations of dependencies and config options, we'd have

Re: [openstack-dev] supported dependency versioning and testing

2014-02-20 Thread Christopher Yeoh
On Thu, 20 Feb 2014 18:06:25 -0500 Sean Dague s...@dague.net wrote: Honestly, I think our experience in even doing a homogenous gate means I think we should let the distros come in with 3rd party testing on those results. Because we don't really have the bw, in either people or machines, to

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Christopher Yeoh
On Fri, 21 Feb 2014 06:53:11 + Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote: -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

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Christopher Yeoh
On Fri, 21 Feb 2014 13:03:31 -0800 Joe Gordon joe.gord...@gmail.com wrote: 1) Discussions about the v2 and v3 APIs at the in-person Nova meetup last week made me come to the realization that v2 won't be going away *any* time soon. In some cases, users have long term API support

Re: [openstack-dev] [Nova] v3 API in Icehouse

2014-02-21 Thread Christopher Yeoh
On Sat, Feb 22, 2014 at 9:04 AM, Matt Riedemann mrie...@linux.vnet.ibm.comwrote: On 2/21/2014 1:53 AM, Christopher Yeoh wrote: On Fri, 21 Feb 2014 06:53:11 + Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote: -Original Message- From: Christopher Yeoh [mailto:cbky...@gmail.com

[openstack-dev] [nova] Future of the Nova API

2014-02-23 Thread Christopher Yeoh
Hi, There has recently been some speculation around the V3 API and whether we should go forward with it or instead backport many of the changes to the V2 API. I believe that the core of the concern is the extra maintenance and test burden that supporting two APIs means and the length of time

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 02:06:50 -0500 Jay Pipes jaypi...@gmail.com wrote: On Mon, 2014-02-24 at 17:20 +1030, Christopher Yeoh wrote: - Proposed way forward: - Release the V3 API in Juno with nova-network and tasks support - Feature freeze the V2 API when the V3 API is released - Set

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 07:56:19 -0800 Dan Smith d...@danplanet.com wrote: - We want to make backwards incompatible changes to the API and whether we do it in-place with V2 or by releasing V3 we'll have some form of dual API support burden. IMHO, the cost of maintaining both APIs (which

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 11:13:11 -0500 Russell Bryant rbry...@redhat.com wrote: Yes, this is a major concern. It has taken an enormous amount of work to get to where we are, and v3 isn't done. It's a good time to re-evaluate whether we are on the right path. So I think its important to point

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 11:48:41 -0500 Jay Pipes jaypi...@gmail.com wrote: It's not about forcing providers to support all of the public API. It's about providing a single, well-documented, consistent HTTP REST API for *consumers* of that API. Whether a provider chooses to, for example, deploy

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 17:47:51 -0500 Russell Bryant rbry...@redhat.com wrote: On 02/24/2014 05:26 PM, Christopher Yeoh wrote: - Whilst we have existing users of the API we also have a lot more users in the future. It would be much better to allow them to use the API we want to get

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 15:54:42 -0800 Morgan Fainberg m...@metacloud.com wrote: Yes, micro-versioning is most likely a better approach, and I’m a fan of using that to gain the benefits of V3 without changing for the sake of change. Ideally in a versioned API we should be versioning a smaller

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 16:20:12 -0800 Dan Smith d...@danplanet.com wrote: So the deprecation message in the patch says: LOG.warning(_('XML support has been deprecated and will be removed in the Juno release.')) perhaps that should be changed :-) Maybe, but I think we

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 18:17:34 -0500 Sean Dague s...@dague.net wrote: On 02/24/2014 06:13 PM, Chris Friesen wrote: On 02/24/2014 04:59 PM, Sean Dague wrote: So, that begs a new approach. Because I think at this point even if we did put out Nova v3, there can never be a v4. It's too much,

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-24 Thread Christopher Yeoh
On Mon, 24 Feb 2014 17:37:04 -0800 Dan Smith d...@danplanet.com wrote: onSharedStorage = True on_shared_storage = False This is a good example. I'm not sure it's worth breaking users _or_ introducing a new microversion for something like this. This is definitely what I would call a

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-25 Thread Christopher Yeoh
On Mon, 24 Feb 2014 21:15:30 -0500 Russell Bryant rbry...@redhat.com wrote: CC'ing the openstack-operators mailing list to get a wider set of feedback on this question. On 02/24/2014 05:26 PM, Christopher Yeoh wrote: 1) Continue as we have been, and plan to release v3 once we have

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-25 Thread Christopher Yeoh
On Tue, 25 Feb 2014 10:31:42 + John Garbutt j...@johngarbutt.com wrote: On 25 February 2014 06:11, Christopher Yeoh cbky...@gmail.com wrote: On Mon, 24 Feb 2014 17:37:04 -0800 Dan Smith d...@danplanet.com wrote: onSharedStorage = True on_shared_storage = False This is a good

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-25 Thread Christopher Yeoh
On Tue, 25 Feb 2014 09:26:09 -0500 Sean Dague s...@dague.net wrote: On 02/25/2014 08:17 AM, Ken'ichi Ohmichi wrote: 2014-02-25 19:48 GMT+09:00 Thierry Carrez thie...@openstack.org: Sean Dague wrote: So, that begs a new approach. Because I think at this point even if we did put out Nova

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-25 Thread Christopher Yeoh
On Tue, 25 Feb 2014 14:47:16 -0800 Dan Smith d...@danplanet.com wrote: Yeah, so objects is the big one here. Objects, and everything else. With no-db-compute we did it for a couple cycles, then objects, next it will be retooling flows to conductor, then dealing with tasks, talking to gantt,

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-25 Thread Christopher Yeoh
On Tue, 25 Feb 2014 10:37:14 + John Garbutt j...@johngarbutt.com wrote: Now I am tempted to say we morph the V3 code to also produce the V2 responses. And change the v3 API, so thats easier to do, and easier for clients to move (like don't change URLs unless we really have to). I know

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-25 Thread Christopher Yeoh
On Tue, 25 Feb 2014 20:52:14 -0800 Dan Smith d...@danplanet.com wrote: This would reduce the amount of duplication which is required (I doubt we could remove all duplication though) and whether its worth it for say the rescue example is debatable. But for those cases you'd only need to

Re: [openstack-dev] [nova] Future of the Nova API

2014-02-26 Thread Christopher Yeoh
On Wed, 26 Feb 2014 09:28:20 -0800 Dan Smith d...@danplanet.com wrote: If we do go down this route of changing the v2 API like this, it would be nice to bump the minor version as well, so when a user has to distinguish between the two versions they don't have to say Havana V2 vs Icehouse

  1   2   3   4   >