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

On 2014年08月23日 18:29, Christopher Yeoh wrote: On Sat, 23 Aug 2014 03:56:27 -0500 Joe Cropper 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/delet

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

On 2014年09月18日 18:14, Day, Phil wrote: -Original Message- From: Kenichi Oomichi [mailto:oomi...@mxs.nes.nec.co.jp] Sent: 18 September 2014 02:44 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] are we going to remove the novaclient v3 sh

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

On 2014年09月18日 18:57, Sean Dague wrote: On 09/18/2014 06:38 AM, Christopher Yeoh wrote: On Sat, 13 Sep 2014 06:48:19 -0400 Sean Dague 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:stpi

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

Close to Kilo, it is time to think about what's next for nova API. In Kilo, we will continue develop the important feature micro-version. In previous v2 on v3 propose, it's include some implementations can be used for micro-version. (https://review.openstack.org/#/c/84695/19/specs/juno/v2-on-v3-

Re: [openstack-dev] [nova] Can we deprecate the server backup API please?

Sounds make sense to me, and then we needn't fix this strange behaviour also https://review.openstack.org/#/c/409644/ Jay Pipes 于2018年11月17日周六 上午3:56写道： > The server backup API was added 8 years ago. It has Nova basically > implementing a poor-man's cron for some unknown reason (probably because

[openstack-dev] [Nova] Remove ratelimits from nova v3 api

Hi, guys, Looks like ratelimits is not really useful. The reason already pointed out by this patch: https://review.openstack.org/#/c/34821/ , Thanks Joe for point it out. So v3 API is a chance to cleanup those stuff. If there isn't anyone object it. I will send patch to get ride of ratelimit

Re: [openstack-dev] [Nova] Splitting up V3 API admin-actions plugin

On 2013?12?01? 21:39, Christopher Yeoh wrote: Hi, At the summit we agreed to split out lock/unlock, pause/unpause, suspend/unsuspend functionality out of the V3 version of admin actions into separate extensions to make it easier for deployers to only have loaded the functionality that they wa

Re: [openstack-dev] [openstack-qa] [qa][nova] The document for the changes from Nova v2 api to v3

repository? Seems better than keeping it in the wiki so that you can update with code changes. Anne On Wed, Nov 13, 2013 at 11:11 PM, Alex Xu <mailto:x...@linux.vnet.ibm.com>> wrote: On 2013?11?14? 07:09, Christopher Yeoh wrote: On Thu, Nov 14, 2013 at 7:52 AM, Dav

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

On 2013年12月12日 04:41, Ryan Petrello wrote: 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 using pecan (and paves the way for other ext

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

I replied some comments on the gerrit also. If we have patch for demonstrate pecan style extension, that will be great. Thanks Alex On 2013年12月18日 05:08, Ryan Petrello wrote: So any additional feedback on this patch? I’d love to start working on porting some of the other extensions to pecan,

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

On 2014?01?06? 16:47, Yaguang Tang wrote: 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 related quota items are stored in two diffe

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

+1 for drop xml. But if we can't drop it, can we think about use XMLDictSerializer instead of XmlTemplate? We spend a lot of time to maintain XmlTemplate, and it make xml format inconsistent(some of resouce's attribute is output as xml sub-element, some of them is output as xml element's attribu

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

On 2014年01月14日 20:04, Ken'ichi Ohmichi wrote: > Hi, > > 2014/1/14 Alex Xu : >> +1 for drop xml. But if we can't drop it, can we think about use >> XMLDictSerializer instead of XmlTemplate? We spend a lot of time to maintain >> XmlTemplate, and it make xml >

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

On 2014?01?08? 23:12, Jay Lau wrote: Thanks Russell, OK, will file a bug for first issue. For second question, I want to show some of my comments here. I think that we should disable cold migration for an ACTIVE VM as cold migrating will first destroy the VM then re-create the VM when using K

Re: [openstack-dev] [nova] Checking before delete flavor?

On 2014?01?26? 20:05, Rui Chen wrote: Hi Stackers: Some instance operations and flavor are closely connected, for example, resize. If I delete the flavor when resize instance, instance will be error. Like this: 1. run instance with flavor A 2. resize instance from flavor A to flavor B 3. del

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

On 2014年02月04日 19:36, Christopher Yeoh wrote: On Tue, 04 Feb 2014 11:37:29 +0100 Thierry Carrez wrote: Christopher Yeoh wrote: On Tue, Feb 4, 2014 at 12:03 PM, Joe Gordon mailto:joe.gord...@gmail.com>> wrote: John and I discussed a third possibility: nova-network v3 should be an extension,

[openstack-dev] [Nova][Neutron] Neutron network in Nova V3 API

Hi, guys, I'm working neutron network stuff in nova V3 API. We will only pass port ids when create server, and Nova won't proxy any neutron call in the future. I plan to add new v3 network extension, that only accept port ids as parameters. And it will pass those port ids in the old request_ne

Re: [openstack-dev] [Nova][Neutron] Neutron network in Nova V3 API

On 2014?02?12? 17:15, Alex Xu wrote: Hi, guys, I'm working neutron network stuff in nova V3 API. We will only pass port ids when create server, and Nova won't proxy any neutron call in the future. I plan to add new v3 network extension, that only accept port ids as parameters. A

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

nticipated. Thanks, Chris! Thanks Russell, that's much appreciated. I'm also very thankful to everyone who has worked on the V3 API either through patches and/or reviews, especially Alex Xu and Ivan Zhu who have done a lot of work on it in Havana and Icehou

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

On 2014年02月25日 21:17, Ken'ichi Ohmichi wrote: 2014-02-25 19:48 GMT+09:00 Thierry Carrez : 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, too big, and doesn't fit in the incremental nature of t

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

On 2014年02月26日 18:40, Thierry Carrez wrote: Kenichi Oomichi wrote: From: Christopher Yeoh [mailto:cbky...@gmail.com] So the problem here is what we consider a "bug" becomes a feature from a user of the API point of view. Eg they really shouldn't be passing some data in a request, but its ignored

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

On 2014?02?28? 00:05, Dan Smith wrote: Sure, but that's still functionally equivalent to using the /v2 prefix. So we could chuck the current /v3 code and do: /v2: Current thing /v3: invalid, not supported /v4: added simple task return for server create /v5: added the event extension /v6: added

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

On 2014?02?28? 13:40, Chris Friesen wrote: On 02/27/2014 06:00 PM, Alex Xu wrote: Does mean our code looks like as below? if client_version > 2: elif client_version > 3 ... elif client_version > 4: ... elif client_version > 5: ... elif client_version > 6:

Re: [openstack-dev] [nova] V3 API support

I think Chris is on vacation. We move V3 API to V2.1. V2.1 have some improvement compare to V2. You can find more detail at http://specs.openstack.org/openstack/nova-specs/specs/juno/implemented/v2-on-v3-api.html We need support instance tag for V2.1. And in your patch, we needn't json-schema for

[openstack-dev] [api] Using query string or request body to pass parameter

Hi, I have question about using query string or request body for REST API. This question found when I review this spec: https://review.openstack.org/#/c/131633/6..7/specs/kilo/approved/judge-service-state-when-deleting.rst Think about use request body will have more benefit: 1. Request body can

Re: [openstack-dev] [api] Using query string or request body to pass parameter

Not sure all, nova is limited at https://github.com/openstack/nova/blob/master/nova/api/openstack/wsgi.py#L79 That under our control. Maybe not just ask question for delete, also for other method. 2014-12-09 1:11 GMT+08:00 Kevin L. Mitchell : > On Mon, 2014-12-08 at 14:07 +0800, Eli Qiao wrote:

Re: [openstack-dev] [api] Using query string or request body to pass parameter

Kevin, thanks for the info! I agree with you. RFC is the authority. use payload in the DELETE isn't good way. 2014-12-09 7:58 GMT+08:00 Kevin L. Mitchell : > On Tue, 2014-12-09 at 07:38 +0800, Alex Xu wrote: > > Not sure all, nova is limited > > at > https://github.com/ope

[openstack-dev] [nova] Evacuate instance which in server group with affinity policy

Hi, There is problem when evacuate instance. If the instance is in the server group with affinity policy, the instance can't evacuate out the failed compute node. I know there is soft affinity policy under development, but think of if the instance in server group with hard affinity means no way t

Re: [openstack-dev] [nova] Evacuate instance which in server group with affinity policy

2014-12-22 9:01 GMT+08:00 Lingxian Kong : > 2014-12-19 17:44 GMT+08:00 Alex Xu : > > Hi, > > > > There is problem when evacuate instance. If the instance is in the server > > group with affinity policy, the instance can't evacuate out the failed > > comp

Re: [openstack-dev] [nova] Evacuate instance which in server group with affinity policy

e-add the VM to the group once the environment is > operational once again. > > [1] https://review.openstack.org/#/c/136487/ > [2] https://review.openstack.org/#/c/139272/ > > - Joe > > On Dec 21, 2014, at 8:36 PM, Lingxian Kong wrote: > > > 2014-12-22

Re: [openstack-dev] [nova] Evacuate instance which in server group with affinity policy

2014-12-22 10:36 GMT+08:00 Lingxian Kong : > 2014-12-22 9:21 GMT+08:00 Alex Xu : > > > > > > 2014-12-22 9:01 GMT+08:00 Lingxian Kong : > >> > > >> > >> but what if the compute node is back to normal? There will be > >> instances in the

Re: [openstack-dev] [nova] Evacuate instance which in server group with affinity policy

2014-12-22 21:50 GMT+08:00 Sylvain Bauza : > > Le 22/12/2014 13:37, Alex Xu a écrit : > > > > 2014-12-22 10:36 GMT+08:00 Lingxian Kong : > >> 2014-12-22 9:21 GMT+08:00 Alex Xu : >> > >> > >> > 2014-12-22 9:01 GMT+08:00 Lingxian Kong : >&g

Re: [openstack-dev] [nova] Questions on pep8 F811 hacking check for microversion

2015-01-06 20:31 GMT+08:00 Jay Pipes : > On 01/06/2015 06:25 AM, Chen CH Ji wrote: > >> Based on nova-specs api-microversions.rst >> we support following function definition format, but it violate the >> hacking rule pep8 F811 because duplicate function definition >> we should use #noqa for them ,

Re: [openstack-dev] [nova][api]do we need to have a spec for all api related changes?

2015-01-07 11:43 GMT+08:00 Eli Qiao : > hi all: > I have a patch [1], just did slight changes on api, do I need to write a > spec(kinds of wasting time to get approved)? > since api-microversion[2] is almost done, can we just feel free to add > changes as micro-version api? > We definitely can't

[openstack-dev] [Nova][Ironic] Question about scheduling two instances to same baremetal node

Hi, All There is bug when running nova with ironic https://bugs.launchpad.net/nova/+bug/1402658 The case is simple: one baremetal node with 1024MB ram, then boot two instances with 512MB ram flavor. Those two instances will be scheduling to same baremetal node. The problem is at scheduler side t

Re: [openstack-dev] [Nova][Ironic] Question about scheduling two instances to same baremetal node

2015-01-09 17:17 GMT+08:00 Sylvain Bauza : > > Le 09/01/2015 09:01, Alex Xu a écrit : > > Hi, All > > There is bug when running nova with ironic > https://bugs.launchpad.net/nova/+bug/1402658 > > The case is simple: one baremetal node with 1024MB ram, then boot two

Re: [openstack-dev] [Nova][Ironic] Question about scheduling two instances to same baremetal node

e upstream > because it’s a bit hacky and will hopefully be obsolete soon. I could share > it if you like. > > Paul > > [2] https://review.openstack.org/#/c/127609/ > > > > > > From: *Sylvain Bauza* > Date: 9 January 2015 at 09:17 > Subject: Re: [openstack

Re: [openstack-dev] [Nova][Ironic] Question about scheduling two instances to same baremetal node

2015-01-09 22:22 GMT+08:00 Sylvain Bauza : > > Le 09/01/2015 14:58, Alex Xu a écrit : > > > > 2015-01-09 17:17 GMT+08:00 Sylvain Bauza : > >> >> Le 09/01/2015 09:01, Alex Xu a écrit : >> >> Hi, All >> >> There is bug when running nova wi

Re: [openstack-dev] [nova] request spec freeze exception for Attach/Detach SR-IOV interface

2015-01-13 13:57 GMT+08:00 少合冯 : > Hello, > > I'd like to request an exception for Attach/Detach SR-IOV interface > feature. [1] > This is an important feature that aims to improve better performance than > normal > network interface in guests and not too hard to implement. > > Thanks, > Shao He,

[openstack-dev] [Nova] Requesting exception for add separated policy rule for each v2.1 api

https://review.openstack.org/#/c/127863/ This spec is part of Nova REST API policy improvement. And those improvement already got generic agreement as in this full view devref https://review.openstack.org/#/c/138270/ This spec is just for Nova REST API v2.1. So really hope it can be done before v

[openstack-dev] [Nova] Enable policy improvment both v2/v3 API or not

Hi, guys There are some BPs working on improve the usability of API policy. Initially those BP just for v2.1/v3 API. For v2 API, we just want to it keep the same as before. But in Juno design summit, we get some complain about policy is hard to use. (https://etherpad.openstack.org/p/juno-nova-de

Re: [openstack-dev] [Nova] Nominating Ken'ichi Ohmichi for nova-core

+1 On 2014年06月14日 06:40, Michael Still wrote: Greetings, I would like to nominate Ken'ichi Ohmichi for the nova-core team. Ken'ichi has been involved with nova for a long time now. His reviews on API changes are excellent, and he's been part of the team that has driven the new API work we've

Re: [openstack-dev] [Nova] API weekly meeting

Any time except 15-22 UTC On 2014年03月07日 08:45, Christopher Yeoh wrote: Hi, I'd like to start a weekly IRC meeting for those interested in discussing Nova API issues. I think it would be a useful forum for: - People to keep up with what work is going on the API and where its headed. - Cloud

Re: [openstack-dev] [nova] a question about instance snapshot

Hi, Jeremy, the discussion at here http://lists.openstack.org/pipermail/openstack-dev/2013-August/013688.html Thanks Alex On 2014年03月07日 10:29, Liuji (Jeremy) wrote: Hi, all Current openstack seems not support to snapshot instance with memory and dev states. I searched the blueprint and found

Re: [openstack-dev] [nova] Backwards incompatible API changes

On 2014年03月21日 17:04, Christopher Yeoh wrote: On Thu, 20 Mar 2014 15:45:11 -0700 Dan Smith wrote: I know that our primary delivery mechanism is releases right now, and so if we decide to revert before this gets into a release, that's cool. However, I think we need to be looking at CD as a very

Re: [openstack-dev] How to add a property to the API extension?

On 2014年04月17日 05:25, Jiang, Yunhong wrote: Hi, Christopher, I have some question to the API changes related to https://review.openstack.org/#/c/80707/4/nova/api/openstack/compute/plugins/v3/hypervisors.py , which adds a property to the hypervisor information. Hi, Yunhong, Chris may b

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

On 2014年09月23日 04:27, Brant Knudson wrote: On Fri, Sep 19, 2014 at 1:39 AM, Alex Xu <mailto:x...@linux.vnet.ibm.com>> wrote: Close to Kilo, it is time to think about what's next for nova API. In Kilo, we will continue develop the important feature micro-version.

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

On 2014年09月23日 08:00, Ken'ichi Ohmichi wrote: # I changed the title for getting opinions from many projects. 2014-09-22 23:47 GMT+09:00 Anne Gentle : -Original Message- From: Alex Xu [mailto:x...@linux.vnet.ibm.com] Sent: Friday, September 19, 2014 3:40 PM To: OpenStack Develo

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

On 2014年09月23日 17:12, Christopher Yeoh wrote: On Mon, 22 Sep 2014 09:29:26 + Kenichi Oomichi 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

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

I'm interesting in the group too! On 2014年09月24日 18:01, Salvatore Orlando wrote: Please keep me in the loop. The importance of ensuring consistent style across Openstack APIs increases as the number of "integrated" project increases. Unless we decide to merge all API endpoints as proposed in a

Re: [openstack-dev] [api] Forming the API Working Group

On 2014年10月14日 12:52, Christopher Yeoh wrote: On Mon, 13 Oct 2014 22:20:32 -0400 Jay Pipes wrote: On 10/13/2014 07:11 PM, Christopher Yeoh wrote: On Mon, 13 Oct 2014 10:52:26 -0400 Jay Pipes wrote: On 10/10/2014 02:05 AM, Christopher Yeoh wrote: I agree with what you've written on the wik

Re: [openstack-dev] [api] Forming the API Working Group

On 2014年10月14日 21:57, Jay Pipes wrote: On 10/14/2014 05:04 AM, Alex Xu wrote: There is one reason to think about what projects *currently* do. When we choice which convention we want. For example, the CamelCase and snake_case, if the most project use snake_case, then choice snake_case style

Re: [openstack-dev] [nova] APIImpact flag for nova specs

On 2014年10月15日 14:20, Christopher Yeoh wrote: Hi, I was wondering what people thought of having a convention of adding an APIImpact flag to proposed nova specs commit messages where the Nova API will change? It would make it much easier to find proposed specs which affect the API as its not alwa

Re: [openstack-dev] [api] API recommendation

2014-10-16 17:57 GMT+08:00 Salvatore Orlando : > In an analysis we recently did for managing lifecycle of neutron > resources, it also emerged that task (or operation) API are a very useful > resource. > Indeed several neutron resources introduced the (in)famous PENDING_XXX > operational statuses

[openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

Hi, Currently migration/rebuild/evacuate didn't support pass scheduler-hints, that means any migration can't use schedule-hints that passed when creating instance. Can we add scheduler-hints support when migration/rebuild/evacuate? That also can enable user move in/out instance to/from an se

Re: [openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

ing 100193, PRC Inactive hide details for Alex Xu ---10/29/2014 12:19:35 PM---Hi, Currently migration/rebuild/evacuate didn't support passAlex Xu ---10/29/2014 12:19:35 PM---Hi, Currently migration/rebuild/evacuate didn't support pass From: Alex Xu To: openstack-dev@lists.openstack.org

Re: [openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

n (Chen) Ji 纪 晨 >> >> Engineer, zVM Development, CSTL >> Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com >> Phone: +86-10-82454158 >> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, >> Beijing 100193, PRC >> >>

Re: [openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

.com > Phone: +86-10-82454158 > Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, > Beijing 100193, PRC > > [image: Inactive hide details for Alex Xu ---10/29/2014 01:34:13 PM---On > 2014年10月29日 12:37, Chen CH Ji wrote: >]Alex Xu ---10/29/2014 01:34:13 &g

Re: [openstack-dev] [Nova] Add scheduler-hints when migration/rebuild/evacuate

#/c/88983/17/specs/juno/persist-scheduler-hints.rst Yea, thanks! will check that. > > > > > > From: Alex Xu [sou...@gmail.com] > > Sent: Wednesday, October 29, 2014 9:11 PM > > To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [nova][compute] propose to use a table to deal with the vm_state when _init_instance in compute

+1, good idea! 2014-11-04 15:15 GMT+08:00 Eli Qiao : > hello all: > in current _init_instance function in compute manager, > there's flood 'and' 'or' logic, to check the vm_state and task_state when > initialize a instance during service list, > this lead hard to read and hard to maintain, so I

Re: [openstack-dev] [nova] top gate bug is libvirt snapshot

Question about swap volume, swap volume's implementation is very similar with live snapshot. Both implemented by blockRebase. But swap volume didn't check any libvirt and qemu version. Should we add version check for swap_volume now? That means swap_volume will be disable also. On 2014?06?26?

Re: [openstack-dev] [OpenStack][Nova][Scheduler] Promote select_destination as a REST API

Maybe we can implement this goal by another way, adding new API 'confirm_before_migration' that's similar with 'confirm_resize'. This also can resolve Chris Friesen's concern. On 2014年07月23日 00:13, Jay Pipes wrote: On 07/21/2014 11:16 PM, Jay Lau wrote: Hi Jay, There are indeed some China cu

Re: [openstack-dev] [nova] libvirtError: XML error: Missing CPU model name on 2nd level vm

You can search nested kvm on the web to get more info, or you can try just use qemu not kvm on 2nd level. On 2014?08?06? 11:32, Chen CH Ji wrote: Thanks a lot for your suggestions , I guess it might be 2nd level configuration issue ... will take more time on it , thanks my 1st level host h

[openstack-dev] [nova] nova-network stuck at get semaphores lock when startup

When I startup nova-network, it stuck at trying get lock for ebtables. @utils.synchronized('ebtables', external=True) def ensure_ebtables_rules(rules, table='filter'): . Checking the code found that invoke utils.synchronized without parameter lock_path, the code will try to use posix s

Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup

Software Park, Haidian District, Beijing 100193, PRC Inactive hide details for Alex Xu ---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at trying get lock for ebtaAlex Xu ---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at trying get lock for ebtables

[openstack-dev] nova-network stuck at get semaphores lock when startup

Software Park, Haidian District, Beijing 100193, PRC Inactive hide details for Alex Xu ---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at trying get lock for ebtaAlex Xu ---08/07/2014 04:54:09 PM---When I startup nova-network, it stuck at trying get lock for ebtables

Re: [openstack-dev] [nova] nova-network stuck at get semaphores lock when startup

Oops, thanks On 2014年08月07日 22:08, Ben Nemec wrote: Unfortunately this is a known issue. We're working on a fix: https://bugs.launchpad.net/oslo/+bug/1327946 On 08/07/2014 03:57 AM, Alex Xu wrote: When I startup nova-network, it stuck at trying get lock for ebtables. @utils.synchro

[openstack-dev] [qa][nova] The document for the changes from Nova v2 api to v3

Hi, guys This is the document for the changes from Nova v2 api to v3: https://wiki.openstack.org/wiki/NovaAPIv2tov3 I will appreciate if anyone can help for review it. Another problem comes up - how to keep the doc updated. So can we ask people, who change something of api v3, update the doc ac

Re: [openstack-dev] [openstack-qa] [qa][nova] The document for the changes from Nova v2 api to v3

On 2013?11?14? 05:22, David Kranz wrote: On 11/13/2013 08:30 AM, Alex Xu wrote: Hi, guys This is the document for the changes from Nova v2 api to v3: https://wiki.openstack.org/wiki/NovaAPIv2tov3 I will appreciate if anyone can help for review it. Another problem comes up - how to keep the

Re: [openstack-dev] [openstack-qa] [qa][nova] The document for the changes from Nova v2 api to v3

On 2013?11?14? 07:09, Christopher Yeoh wrote: On Thu, Nov 14, 2013 at 7:52 AM, David Kranz <mailto:dkr...@redhat.com>> wrote: On 11/13/2013 08:30 AM, Alex Xu wrote: Hi, guys This is the document for the changes from Nova v2 api to v3: https://wiki.openstack

[openstack-dev] [Nova] Network stuff in Nova API v3

Hi, guys, Currently we have one core and two extensions that related network in Nova API v3. They are ips, attach_interface and multinic. I have two questions for them. The first question is about ips and attach_interface. The below was the index's response of ips and attach_interface: ips:

Re: [openstack-dev] [Nova] Network stuff in Nova API v3

nova-api that has to proxy info from neutron, but I agree we should reduce where we can. John On 7 August 2013 10:08, Alex Xu wrote: Hi, guys, Currently we have one core and two extensions that related network in Nova API v3. They are ips, attach_interface and multinic. I have two questions for

Re: [openstack-dev] [Nova] Network stuff in Nova API v3

On 2013年08月07日 22:24, John Garbutt wrote: Hey, On 7 August 2013 14:42, Alex Xu wrote: On 2013年08月07日 17:38, John Garbutt wrote: multi-nic added an extra virtual interface on a seprate network, like adding a port: http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi

Re: [openstack-dev] [Nova] Network stuff in Nova API v3

On 2013年08月08日 13:49, Zhu Bo wrote: On 2013年08月07日 21:42, Alex Xu wrote: On 2013年08月07日 17:38, John Garbutt wrote: multi-nic added an extra virtual interface on a seprate network, like adding a port: http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi-nics.html That

[openstack-dev] Remove 'absolute_limit' from limits's response for v3

Hi, guys, When I'm cleaning up v3 api. I found limits extension will return absolute_limit. I think that already done by extension quota_sets. And I can't guess the reason why we keep that in limits. For ensure, I didn't missing something, I bring it to here. If we haven't any reason for

Re: [openstack-dev] [nova] v3 api remove security_groups extension (was Re: security_groups extension in nova api v3)

On 2013年08月16日 03:16, Melanie Witt wrote: On Aug 13, 2013, at 3:35 PM, Melanie Witt wrote: On Aug 13, 2013, at 2:11 AM, Day, Phil wrote: If we really want to get clean separation between Nova and Neutron in the V3 API should we consider making the Nov aV3 API only accept lists o port ids in

Re: [openstack-dev] [nova] v3 api remove security_groups extension (was Re: security_groups extension in nova api v3)

On 2013?08?16? 14:34, Christopher Yeoh wrote: On Fri, Aug 16, 2013 at 10:28 AM, Melanie Witt > wrote: On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote: > +1 from me as long as this wouldn't change anything for the EC2 API's security groups support, which

Re: [openstack-dev] [nova] v3 api remove security_groups extension (was Re: security_groups extension in nova api v3)

On 2013年08月17日 00:14, Vishvananda Ishaya wrote: On Aug 15, 2013, at 5:58 PM, Melanie Witt wrote: On Aug 15, 2013, at 1:13 PM, Joe Gordon wrote: +1 from me as long as this wouldn't change anything for the EC2 API's security groups support, which I assume it won't. Correct, it's unrelated to

Re: [openstack-dev] [nova] Revert Baremetal v3 API extension?

+1 On 2013年09月05日 17:51, John Garbutt wrote: +1 I meant to raise that myself when I saw some changes there the other day. On 4 September 2013 15:52, Thierry Carrez wrote: Russell Bryant wrote: On 09/04/2013 10:26 AM, Dan Smith wrote: Hi all, As someone who has felt about as much pain as pos

Re: [openstack-dev] [nova] FFE Request: v3 setting v3 API core

On 2013?09?08? 21:34, Christopher Yeoh wrote: Hi, The following 3 changesets in the queue: https://review.openstack.org/#/c/43274/ https://review.openstack.org/#/c/43278/ https://review.openstack.org/#/c/43280/ make keypairs, scheduler hints and console output part of the V3 core api. This ess

Re: [openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

Looks like we use API_MAX_VERSION and DEFAULT_OS_COMPUTE_API_VERSION with wrong way. This isn't broken with rackspace only, this broken novaclient runing with nova legacy v2 api(legacy v2 api's behavior is no version exposed). API_MAX_VERSION is the max version of client supported, currently it sh

Re: [openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

I just work out a patch quickly for fixing this, https://review.openstack.org/237850 2015-10-21 10:08 GMT+08:00 Alex Xu : > Looks like we use API_MAX_VERSION and DEFAULT_OS_COMPUTE_API_VERSION with > wrong way. This isn't broken with rackspace only, this broken novaclient > ru

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. In other timezones the meeting is at: EST 08:00 (Tue) Japan 21:00 (Tue) China 20:00 (Tue) United Kingdom 13:00 (Tue) The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meeti

[openstack-dev] [nova] [doc] How to support Microversions and Actions in Swagger Spec

Hi, folks Nova API sub-team is working on the swagger generation. And there is PoC https://review.openstack.org/233446 But before we are going to next step, I really hope we can get agreement with how to support Microversions and Actions. The PoC have demo about Microversions. It generates min ve

Re: [openstack-dev] [nova][policy] Exposing hypervisor details to users

2015-11-06 20:59 GMT+08:00 Sean Dague : > On 11/06/2015 07:28 AM, John Garbutt wrote: > > On 6 November 2015 at 12:09, Sean Dague wrote: > >> On 11/06/2015 04:49 AM, Daniel P. Berrange wrote: > >>> On Fri, Nov 06, 2015 at 05:08:59PM +1100, Tony Breeds wrote: > Hello all, > I came ac

Re: [openstack-dev] [nova] [doc] How to support Microversions and Actions in Swagger Spec

2015-11-06 22:22 GMT+08:00 Anne Gentle : > > > On Thu, Nov 5, 2015 at 9:31 PM, Alex Xu wrote: > >> Hi, folks >> >> Nova API sub-team is working on the swagger generation. And there is PoC >> https://review.openstack.org/233446 >> >> But before we

Re: [openstack-dev] [nova] [doc] How to support Microversions and Actions in Swagger Spec

2015-11-06 20:46 GMT+08:00 John Garbutt : > On 6 November 2015 at 03:31, Alex Xu wrote: > > Hi, folks > > > > Nova API sub-team is working on the swagger generation. And there is PoC > > https://review.openstack.org/233446 > > > > But before we are going

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. In other timezones the meeting is at: EST 08:00 (Tue) Japan 21:00 (Tue) China 20:00 (Tue) United Kingdom 13:00 (Tue) The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meeti

Re: [openstack-dev] [nova] Nova API sub-team meeting

2015-11-09 21:49 GMT+08:00 Ed Leafe : > On Nov 9, 2015, at 7:11 AM, Alex Xu wrote: > > > > We have weekly Nova API meeting this week. The meeting is being held > Tuesday UTC1200. > > > > In other timezones the meeting is at: > > > > EST 08:00 (Tue) &g

[openstack-dev] [nova] Welcome to contribute on improvement the nova API documentation

Hi, At Tokyo summit, we decided the API documentation is hight priority and focus on Mitaka release. We really need better API documentation to help user to use our API easily. Those API doc works are also good for new contributors, it is good chance to get familiar with nova. So if you are inter

[openstack-dev] [nova] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Hi, At nova api subteam weekly meeting, we decided hold 2 days virtual doc sprint to help the Nova API document. The initial proposed date is Dec 8 and 9(Let me know if the date is conflict with other thing). The sprint is running on local time for folks. Peoples can work on the patch and also can

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Sorry, add [docs] and [api] tags to the title! 2015-11-11 20:51 GMT+08:00 Alex Xu : > Hi, > > At nova api subteam weekly meeting, we decided hold 2 days virtual doc > sprint to help the Nova API document. The initial proposed date is Dec 8 > and 9(Let me know if the date is conf

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

2015-11-13 17:36 GMT+08:00 John Garbutt : > On 6 November 2015 at 15:32, John Garbutt wrote: > > Hi, > > > > I propose we add Alex Xu[1] to nova-core. > > > > Over the last few cycles he has consistently been doing great work, > > including some quali

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks Alex

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks _

Re: [openstack-dev] [nova] How were we going to remove soft delete again?

2015-11-30 19:42 GMT+08:00 Sean Dague : > On 11/24/2015 11:36 AM, Matt Riedemann wrote: > > I know in Vancouver we talked about no more soft delete and in Mitaka > > lxsli decoupled the nova models from the SoftDeleteMixin [1]. > > > > From what I remember, the idea is to not add the deleted colum

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks _

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-02 23:12 GMT+08:00 Sylvain Bauza : > > > Le 02/12/2015 15:23, Sean Dague a écrit : > >> We have previously agreed that scheduler hints in Nova are an open ended >> thing. It's expected for sites to have additional scheduler filters >> which expose new hints. The way we handle that with our

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Just reminder the event which close the time, the virtual doc sprint is right next week. Welcome to join us! 2015-11-11 20:51 GMT+08:00 Alex Xu : > Hi, > > At nova api subteam weekly meeting, we decided hold 2 days virtual doc > sprint to help the Nova API document. The initial prop

Re: [openstack-dev] [nova] jsonschema for scheduler hints

2015-12-04 16:48 GMT+08:00 Sylvain Bauza : > > > Le 04/12/2015 04:21, Alex Xu a écrit : > > > > 2015-12-02 23:12 GMT+08:00 Sylvain Bauza : > >> >> >> Le 02/12/2015 15:23, Sean Dague a écrit : >> >>> We have previously agreed that scheduler

  1   2   3   4   >