Re: [openstack-dev] [nova] Question about force_host skip filters

2015-02-14 1:41 GMT+08:00 Nikola Đipanov : > On 02/12/2015 04:10 PM, Chris Friesen wrote: > > On 02/12/2015 03:44 AM, Sylvain Bauza wrote: > > > >> Any action done by the operator is always more important than what the > >> Scheduler > >> could decide. So, in an emergency situation, the operator w

Re: [openstack-dev] [nova] Shared storage support

Actually I have similar idea, an plan to work on it at L by a nova-spec (is it worth a spec?). But this idea not come from this bug, it's come from other cases: 1. Currently we need specified 'on_shared_storage' and 'block_migration' when evacuate and live_migration. After we tracking the shared

Re: [openstack-dev] [nova] blueprint about multiple workers supported in nova-scheduler

Rui, you still can run multiple nova-scheduler process now. 2015-03-05 10:55 GMT+08:00 Rui Chen : > Looks like it's a complicated problem, and nova-scheduler can't scale-out > horizontally in active/active mode. > > Maybe we should illustrate the problem in the HA docs. > > http://docs.openstack.

Re: [openstack-dev] [nova] Question about boot-from-volume instance and flavor

2015-03-04 4:45 GMT+08:00 Jay Pipes : > On 03/03/2015 01:10 AM, Rui Chen wrote: > >> Hi all, >> >> When we boot instance from volume, we find some ambiguous description >> about flavor root_gb in operations guide, >> http://docs.openstack.org/openstack-ops/content/flavors.html >> >> /Virtual root

Re: [openstack-dev] removal of v3 in tree testing

2015-03-06 13:49 GMT+08:00 GHANSHYAM MANN : > Hi Sean, > > That is very nice idea to keep only 1 set of tests and run those twice via > tox. > > Actually my main goal was- > - 1. Create clean sample file structure for V2. V2.1 and micro-versions >Something like below- > api_samples/ >

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

Thanks for Jay point this out! If we have agreement on this and document it, that will be great for guiding developer how to add new API. I know we didn't want extension for API. But I think we still need modularity. I don't think we should put everything in a single file, that file will become hu

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

ok, no problem, will take a look it tomorrow. 2015-03-09 20:18 GMT+08:00 Christopher Yeoh : > > > On Mon, Mar 9, 2015 at 10:08 PM, John Garbutt > wrote: > >> +1 >> >> Please could you submit a dev ref for this? >> >> We can argue on the review, a bit like this one: >> >> https://github.com/opens

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

confidence for my English and view. So please feel free to comment and update the doc to add your thought and your view, and add yourself as co-author.(If you feel hopeless, you also can start new one) Thanks Alex 2015-03-09 23:37 GMT+08:00 Alex Xu : > ok, no problem, will take a look it tomor

Re: [openstack-dev] [nova][api] Microversions. And why do we need API extensions for new API functionality?

2015-03-10 3:37 GMT+08:00 Jay Pipes : > On 03/08/2015 08:10 AM, Alex Xu wrote: > >> Thanks for Jay point this out! If we have agreement on this and document >> it, that will be great for guiding developer how to add new API. >> >> I know we didn't want exte

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

2015-03-13 2:13 GMT+08:00 Sean Dague : > On 03/12/2015 02:03 PM, Chris Friesen wrote: > > Hi, > > > > I'm having an issue with microversions. > > > > The api_version() code has a comment saying "This decorator MUST appear > > first (the outermost decorator) on an API method for it to work > correc

[openstack-dev] [Nova] The expected behavior of os-tenant-network API

Hi, All, When review the policy patches. I found there is a little strange behavior in os-tenant-network API. And just file a bug for them: 1. non-admin can't create network by os-tenant-network API https://bugs.launchpad.net/nova/+bug/1432101 2. non-admin can delete a network without any associ

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

2015-03-13 19:10 GMT+08:00 Sean Dague : > On 03/13/2015 02:55 AM, Chris Friesen wrote: > > On 03/12/2015 12:13 PM, Sean Dague wrote: > >> On 03/12/2015 02:03 PM, Chris Friesen wrote: > >>> Hi, > >>> > >>> I'm having an issue with microversions. > >>> > >>> The api_version() code has a comment sayi

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

2015-03-16 9:48 GMT+08:00 Alex Xu : > > > 2015-03-13 19:10 GMT+08:00 Sean Dague : > >> On 03/13/2015 02:55 AM, Chris Friesen wrote: >> > On 03/12/2015 12:13 PM, Sean Dague wrote: >> >> On 03/12/2015 02:03 PM, Chris Friesen wrote: >> >>> Hi

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

st Regards! > > Kevin (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 > > [ima

Re: [openstack-dev] [nova] is it possible to microversion a static class method?

declaration into the code. > > > > On Mon, Mar 16, 2015 at 12:21 PM, Alex Xu wrote: > >> >> >> 2015-03-16 9:48 GMT+08:00 Alex Xu : >> >>> >>> >>> 2015-03-13 19:10 GMT+08:00 Sean Dague : >>> >>>> On 03/13/2015 02:5

Re: [openstack-dev] [nova] what is our shipped paste.ini going to be for Kilo

2015-03-17 13:25 GMT+08:00 Christopher Yeoh : > On Mon, 16 Mar 2015 11:22:12 -0400 > Russell Bryant wrote: > > > On 03/16/2015 11:08 AM, John Garbutt wrote: > > > While its not under Nova's control, I think we need to consider the > > > keystone catalog here. > > > > > > It feels nice to have an

Re: [openstack-dev] In loving memory of Chris Yeoh

Feel very sad. Just few weeks ago, I still saw him active on the community. Really hard believe this happen such suddenly. He was my leader in IBM and mentored me on the openstack community also, offered lots of help without reservation, really learn a lot from him. We have phone call meeting eve

Re: [openstack-dev] [nova] Policy rules are killed by the context admin check

2015-04-23 6:55 GMT+08:00 Matt Riedemann : > > > On 4/22/2015 8:32 AM, Sylvain Bauza wrote: > >> Hi, >> >> By discussing on a specific bug [1], I just discovered that the admin >> context check which was done at the DB level has been moved to the API >> level thanks to the api-policy-v3 blueprint

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

Thanks Andrey for hard work on the microverison client support. Wrote down some my thought: I also agreed we will have only one endpoint 'compute'. Hope we can switch v2.1 export as '/v2' in the api-paste.conf as default very soon~ let's say what expected after we only have v2.1 in the world fir

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

2015-04-24 17:24 GMT+08:00 Andrey Kurilin : > Thank you for suggestions! I'll try modify patches as soon as possible. > np, it's better waiting for more comment before you begin to update the code first. avoid you need rework again I think :) > > On Fri, Apr 24, 2015 at 6

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

/v2/' already can be used to discover microversion support or not. Sounds like add another way to support discover? And v2 api didn't return fault with some extra header, that sounds like behavior and back-incompatible change. > > On Fri, Apr 24, 2015 at 12:42 PM, Alex Xu wrote: &g

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

2015-04-27 17:49 GMT+08:00 John Garbutt : > I see these changes as really important. > > We need to establish good patterns other SDKs can copy. > > On 24 April 2015 at 12:05, Alex Xu wrote: > > 2015-04-24 18:15 GMT+08:00 Andrey Kurilin : > >> >When user execute

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

2015-04-28 15:22 GMT+08:00 Alex Xu : > > > 2015-04-27 17:49 GMT+08:00 John Garbutt : > >> I see these changes as really important. >> >> We need to establish good patterns other SDKs can copy. >> >> On 24 April 2015 at 12:05, Alex Xu wrote: >

[openstack-dev] [nova] Nova API meeting

Hi, Sorry for sending this reminder late. We have weekly Nova API meeting this week. But the meeting time was adjust. The meeting is being held today Friday UTC1200. We encourage cloud operators and those who use the REST API such as SDK developers and others who and are interested in the future

Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core

I'm not core, but I want to +1 :) 2015-04-30 19:30 GMT+08:00 John Garbutt : > Hi, > > I propose we add Melanie to nova-core. > > She has been consistently doing great quality code reviews[1], > alongside a wide array of other really valuable contributions to the > Nova project. > > Please respond

Re: [openstack-dev] [nova][api] API working group liaisons and responsibilities

2015-05-02 5:12 GMT+08:00 Everett Toews : > On Apr 30, 2015, at 9:54 AM, Jay Pipes wrote: > > > Hi Stackers, > > > > OK, so Matthew Gilliard and Alex Xu have volunteered to be the Nova > team's liaisons to the API working group. Big thank you to Matthew and

Re: [openstack-dev] [nova] Which error code should we return when OverQuota

>From API-WG guideline, exceed quota should be 403 https://github.com/openstack/api-wg/blob/master/guidelines/http.rst 2015-05-06 3:30 GMT+08:00 Chen CH Ji : > In doing patch [1], A suggestion is submitted that we should return 400 > (bad Request) instead of 403 (Forbidden) > I take a look at [2

Re: [openstack-dev] [nova][python-novaclient] microversion implementation on client side

ack.org/cgit/openstack/python-ironicclient/tree/ironicclient/common/http.py#n72 > > -Deva > > On Mon, Apr 27, 2015 at 2:49 AM, John Garbutt > wrote: > > I see these changes as really important. > > > > We need to establish good patterns other SDKs can copy. > > &

[openstack-dev] [nova] Nova API meeting

Hi, We have weekly Nova API meeting this week. But the meeting time was adjust. The meeting is being held tomorrow Friday UTC1200. 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 othe

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

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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

[openstack-dev] [nova] Removes the extra URL routes in Nova API

Currently I'm working on removing the stevedore [0], and move the URL routes mapping into a plain list [1]. But actually, the original URL mappings which Nova created [2] are more than that list. Due to the interface 'routes.Mapper.resources' create a set routes conforming to the Atom publish prot

Re: [openstack-dev] [nova] [neutron] What the behavior of AddFixedIp API should be?

eply something, thank you. >>> >>> >> If the functionality is available via Neutron APIs, we should just >> deprecate the multinic API like we did for the other network API proxies in >> microv

Re: [openstack-dev] [nova] [neutron] What the behavior of AddFixedIp API should be?

oops, sorry, the correct link is https://review.openstack.org/#/c/384261/, I must remove last number accidently 2017-03-30 14:34 GMT+08:00 Kevin Benton : > Not sure what you meant to link to, but that's not a spec. :) > > On Wed, Mar 29, 2017 at 11:21 PM, Alex Xu wrote: > &

Re: [openstack-dev] [nova][api] quota-class-show not sync to quota-show

We talked about remove the quota-class API for multiple times ( http://lists.openstack.org/pipermail/openstack-dev/2016-July/099218.html) I guess we can deprecate the entire quota-class API directly. 2017-04-07 18:19 GMT+08:00 Chen CH Ji : > Version 2.35 removed most deprecated output like float

Re: [openstack-dev] [nova][deployment] FYI: changes to cells v2 setup guide (pike only)

Is it strange that the 'nova service-list' and 'nova host-list' return the hosts which didn't have host mapping yet? How the user to know whether a host was added to a cell or not? 2017-04-14 23:45 GMT+08:00 Matt Riedemann : > Nova is working on adding multi-cell aware support to the compute API

Re: [openstack-dev] [nova] Usability question for the server migrations API

2017-04-15 4:38 GMT+08:00 Chet Burgess : > On Fri, Apr 14, 2017 at 1:27 PM, Matt Riedemann > wrote: > >> The GET /servers/{server_id}/migrations API only lists in-progress live >> migrations. This is an artifact of when it was originally introduced as the >> os-migrations API which was tightly co

Re: [openstack-dev] [libvirt] Whether kvm supports NVIDIA VGPU

2017-04-15 3:03 GMT+08:00 Jay Pipes : > On 04/12/2017 10:53 PM, 文峰sx-9149 wrote: > >> Will the openstack or libvirt (kvm) support NVIDIA VGPU? >> I am here >> >> to see a mail introduction libvirt kvm support VGPU. >> But I

[openstack-dev] [nova][api] Strict validation in query parameters

We added new decorator 'query_schema' to support validate the query parameters by JSON-Schema. It provides more strict valiadation as below: * set the 'additionalProperties=False' in the schema, it means that reject any invalid query parameters and return HTTPBadRequest 400 to the user. * use the

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

2017-06-19 22:17 GMT+08:00 Jay Pipes : > On 06/19/2017 09:04 AM, Edward Leafe wrote: > >> Current flow: >> * Scheduler gets a req spec from conductor, containing resource >> requirements >> * Scheduler sends those requirements to placement >> * Placement runs a query to determine the root RPs that

Re: [openstack-dev] [nova] The definition of 'Optional' parameter in API reference

2017-07-04 15:40 GMT+08:00 Ghanshyam Mann : > On Mon, Jul 3, 2017 at 1:38 PM, Takashi Natsume > wrote: > > Hi, all. > > > > In Nova API reference, there is inconsistency in > > whether to define parameters added in new microversion as 'optional' or > not. > > Those should be defined based on how

Re: [openstack-dev] [nova] placement/resource providers update 27

2017-07-07 19:44 GMT+08:00 Chris Dent : > > After 40 days in the desert I've returned with placement update 27. > > Unfortunately, as far as I can tell, no one did any updates while I > was gone so I don't have anything to crib from to have the full > story on what's going on. I suspect I will mis

Re: [openstack-dev] [nova] Should PUT /os-services be idempotent?

2017-07-12 9:18 GMT+08:00 Matt Riedemann : > I'm looking for some broader input on something being discussed in this > change: > > https://review.openstack.org/#/c/464280/21/nova/api/openstac > k/compute/services.py > > This is collapsing the following APIs into a single API: > > Old: > > * PUT /o

Re: [openstack-dev] [nova] Proposing Balazs Gibizer for nova-core

Yay! 2017-08-23 9:18 GMT+08:00 Matt Riedemann : > I'm proposing that we add gibi to the nova core team. He's been around for > awhile now and has shown persistence and leadership in the multi-release > versioned notifications effort, which also included helping new > contributors to Nova get invo

Re: [openstack-dev] [nova] Less than 24 hours to Pike RC2

2017-08-24 11:34 GMT+08:00 Matt Riedemann : > This is just a reminder that we're in the final stretch for Pike RC2 which > happens tomorrow. > > There are a couple of fixes in flight yet for RC2 at the top of the > etherpad: > > https://etherpad.openstack.org/p/nova-pike-release-candidate-todo > >

Re: [openstack-dev] [nova][api] why need PUT /servers/{server_id}/metadata/{key} ?

2017-09-20 21:14 GMT+08:00 Matt Riedemann : > On 9/20/2017 12:48 AM, Chen CH Ji wrote: > >> in analyzing other code, found seems we don't need PUT >> /servers/{server_id}/metadata/{key} ? >> >> as the id is only used for check whether it's in the body and we will >> honor the whole body (body['met

Re: [openstack-dev] [ironic] ironic and traits

It sounds like Ironic use the Trait to configure the instance https://review.openstack.org/#/c/504952/5/specs/approved/config-template-traits.rst@95 The downside I can see is that the extra burden added to the placement. As the example, used in the spec: * CUSTOM_BM_CONFIG_BIOS_VMX_ON * CUSTOM_BM_

[openstack-dev] [api][nova] Why we return a redirect (302) when request to 'GET /v2.1'?

There is bug complain about the redirect which returned by the 'GET /v2.1' https://launchpad.net/bugs/1728732 'GET /v2.1' will return a redirect to the 'GET /v2.1/'. The response of 'GET /v2.1/' is the API version info. This seems nova API behaviour for a long time. In the keystone catalog, the e

Re: [openstack-dev] [nova][neutron] How do you use the instance IP filter?

FYI, Nova did use regex https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L2408 2017-10-27 11:35 GMT+08:00 Matt Riedemann : > On 10/26/2017 9:54 PM, Tony Breeds wrote: > >> Can you use RLIKE/REGEX? or is that too MySQL specific ? >> > > I thought about that, and my gut respo

Re: [openstack-dev] [api][nova] Why we return a redirect (302) when request to 'GET /v2.1'?

2017-11-02 20:42 GMT+08:00 Sean Dague : > On 11/01/2017 11:04 PM, Alex X wrote: > >> There is bug complain about the redirect which returned by the 'GET >> /v2.1' https://launchpad.net/bugs/1728732 >> >> 'GET /v2.1' will return a redirect to the 'GET /v2.1/'. The response of >> 'GET /v2.1/' is the

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

++, I also want to join this party :) 2018-01-09 8:40 GMT+08:00 Zhipeng Huang : > Agree 100% to avoid regular meeting and it is better to have bi-weekly > email report. Meeting should be arranged event based, and I think given the > status of OpenStack community's work on resource provider, mostl

Re: [openstack-dev] [nova] PTL Election Season

Matt, thanks for your leading and help over the past years! Your obsessive paperwork is really helpful and I appreciate for that. 2018-01-23 7:09 GMT+08:00 Matt Riedemann : > On 1/15/2018 11:04 AM, Kendall Nelson wrote: > >> Election details: https://governance.openstack.org/election/ >> >> Pleas

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-14 10:38 GMT+08:00 Cheng, Yingxin : > > On 7/14/16, 05:42, "Ed Leafe" wrote: > On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin > wrote: > > 4. Capabilities are managed/grouped/abstracted by namespaces, and > scheduler can make decisions based on either cap_names or cap_namespaces >

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-18 13:45 GMT-07:00 Matt Riedemann : > On 7/15/2016 8:06 PM, Alex Xu wrote: > >> >> Actually I still think aggregates isn't good for Manage Caps, just as I >> said in previous reply about Aggregates. One of reason is just same with >> #2 you said :) And

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-20 11:08 GMT-07:00 Jay Pipes : > On 07/18/2016 01:45 PM, Matt Riedemann wrote: > >> On 7/15/2016 8:06 PM, Alex Xu wrote: >> >>> >>> Actually I still think aggregates isn't good for Manage Caps, just as I >>> said in previous reply about

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

[RFC] ResourceProviderTags - Manage > > Capabilities with ResourceProvider > > > > On 07/13/2016 01:37 PM, Ed Leafe wrote: > > > On Jul 11, 2016, at 6:08 AM, Alex Xu wrote: > > > > > >> For example, the capabilities can be de

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-28 22:31 GMT+08:00 Jay Pipes : > On 07/20/2016 11:25 PM, Alex Xu wrote: > >> One more for end users: Capabilities Discovery API, it should be 'GET >> /resource_providers/tags'. Or a proxy API from nova to the placement >> API? >> >

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

Nova-spec is submitted: https://review.openstack.org/345138, welcome review and comments! 2016-07-11 19:08 GMT+08:00 Alex Xu : > This propose is about using ResourceProviderTags as a solution to manage > Capabilities (Qualitative) in ResourceProvider. > The ResourceProviderTags is to

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

2016-08-02 4:13 GMT+08:00 Matt Riedemann : > On 8/1/2016 1:39 PM, Ken'ichi Ohmichi wrote: > >> 2016-07-29 10:32 GMT-07:00 Sean Dague : >> >>> On 07/28/2016 05:38 PM, Matt Riedemann wrote: >>> On 7/28/2016 3:55 PM, Matt Riedemann wrote: > For os-attach-interfaces, we need that to atta

[openstack-dev] [nova] [scheduler] Use ResourceProviderTags instead of ResourceClass?

Chris have a thought about using ResourceClass to describe Capabilities with an infinite inventory. In the beginning we brain storming the idea of Tags, Tan Lin have same thought, but we say no very quickly, due to the ResourceClass is really about Quantitative stuff. But Chris give very good point

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

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] os-virtual-interfaces isn't deprecated in 2.36

2016-08-02 22:09 GMT+08:00 Matt Riedemann : > On 8/2/2016 2:41 AM, Alex Xu wrote: > >> A little strange we have two API endpoints, one is >> '/servers/{uuid}/os-interfaces', another one is >> '/servers/{uuid}/os-virtual-interfaces'. >> >>

Re: [openstack-dev] [nova] os-virtual-interfaces isn't deprecated in 2.36

2016-08-03 14:40 GMT+08:00 Alex Xu : > > > 2016-08-02 22:09 GMT+08:00 Matt Riedemann : > >> On 8/2/2016 2:41 AM, Alex Xu wrote: >> >>> A little strange we have two API endpoints, one is >>> '/servers/{uuid}/os-interfaces', another one is &g

Re: [openstack-dev] [nova] [scheduler] Use ResourceProviderTags instead of ResourceClass?

2016-08-03 2:12 GMT+08:00 Jay Pipes : > On 08/02/2016 08:19 AM, Alex Xu wrote: > >> Chris have a thought about using ResourceClass to describe Capabilities >> with an infinite inventory. In the beginning we brain storming the idea >> of Tags, Tan Lin have same thought, bu

Re: [openstack-dev] [Nova] Does this api modification need Microversion?

2016-08-03 22:03 GMT+08:00 Matt Riedemann : > On 8/2/2016 1:11 AM, han.ro...@zte.com.cn wrote: > >> patchset url: https://review.openstack.org/#/c/334747/ >> >> >> >> Allow "revert_resize" to recover error instance after resize/migrate. >> >> When resize/migrate instance, if error occurs on source

Re: [openstack-dev] [Nova] Some thoughts on API microversions

Agree with Andrew about Microversions may overused. I thought similar thing before. The Microversions should be the version control of API 'core' protocol. So I can say the protocol of send an action to server is: 'POST /servers/{uuid}/action'. We won't bump microversion for any new action or acti

Re: [openstack-dev] [Nova] Some thoughts on API microversions

2016-08-05 0:43 GMT+08:00 Andrew Laski : > > > On Thu, Aug 4, 2016, at 11:40 AM, John Garbutt wrote: > > On 4 August 2016 at 16:28, Edward Leafe wrote: > > > On Aug 4, 2016, at 8:18 AM, Andrew Laski wrote: > > > > > >> This gets to the point I'm trying to make. We don't guarantee old > > >> beha

Re: [openstack-dev] [nova] [scheduler] Use ResourceProviderTags instead of ResourceClass?

I think the way is "Use ResourceProviderTags instead of ResourceClass", not "Use ResourceClass instead of ResourceClass" 2016-08-05 21:16 GMT+08:00 Chris Dent : > On Tue, 2 Aug 2016, Alex Xu wrote: > > Chris have a thought about using ResourceClass to describe Capabili

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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 ___

[openstack-dev] [nova] The deprecation of proxy API related CLI

Hi, guys, We have agreement on how to deprecate the CLI for the proxy APIs which were deprecated in 2.36 when mid-cycle. But I still feels that we have something isn't very clear. So I just want to summary the situation at here, and to be clear the final goal. Here are the patches https://review.

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-15 12:56 GMT+08:00 Yingxin Cheng : > Hi, > > I'm concerned with the dependencies between "os-capabilities" library and > all the other OpenStack services such as Nova, Placement, Ironic, etc. > > Rather than embedding the universal "os-capabilities" in Nova, Cinder, > Glance, Ironic servic

Re: [openstack-dev] [nova] os-capabilities library created

2016-08-16 7:31 GMT+08:00 Jay Pipes : > On 08/15/2016 03:57 AM, Alex Xu wrote: > >> 2016-08-15 12:56 GMT+08:00 Yingxin Cheng > <mailto:yingxinch...@gmail.com>>: >> >> >> Hi, >> >> I'm concerned with the dependencies between &

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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 ___

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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 ___

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] resignation from bug czar role

Markus, thank you for all your help! 2016-09-05 19:19 GMT+08:00 Markus Zoeller : > TL;DR: bug czar role for Nova is vacant from now on > > > After doing bug triage for ~1 year, which was quiet interesting, it's > time for me to move to different topics. My tasks within the company > internal team

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

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] Adding Takashi Natsume to python-novaclient core

+1 2018-02-09 23:01 GMT+08:00 Matt Riedemann : > I'd like to add Takashi to the python-novaclient core team. > > python-novaclient doesn't get a ton of activity or review, but Takashi has > been a solid reviewer and contributor to that project for quite awhile now: > > http://stackalytics.com/rep

Re: [openstack-dev] [nova][cyborg]Dublin PTG Cyborg Nova Interaction Discussion

+1, I'm interested also. 2018-02-12 23:27 GMT+08:00 Eric Fried : > I'm interested. No date/time preference so far as long as it sticks to > Monday/Tuesday. > > efried > > On 02/12/2018 09:13 AM, Zhipeng Huang wrote: > > Hi Nova team, > > > > Cyborg will have ptg sessions on Mon and Tue from 2:00

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

2018-03-06 22:45 GMT+08:00 Mooney, Sean K : > > > > > *From:* Matthew Booth [mailto:mbo...@redhat.com] > *Sent:* Saturday, March 3, 2018 4:15 PM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* Re: [openstack-dev] [Nova] [Cybo

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

2018-03-07 10:21 GMT+08:00 Alex Xu : > > > 2018-03-06 22:45 GMT+08:00 Mooney, Sean K : > >> >> >> >> >> *From:* Matthew Booth [mailto:mbo...@redhat.com] >> *Sent:* Saturday, March 3, 2018 4:15 PM >> *To:* OpenStack Development Mai

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

t; and pre-programed ones. > Therefore it is correct that in your description, the programming > operation should be a call from Nova to Cyborg, and cyborg will complete > the operation while nova waits. The only problem is that the weigher step > should be an optional one. > >

Re: [openstack-dev] [nova] Proposing Eric Fried for nova-core

+1 2018-03-27 10:00 GMT+08:00 melanie witt : > Howdy everyone, > > I'd like to propose that we add Eric Fried to the nova-core team. > > Eric has been instrumental to the placement effort with his work on nested > resource providers and has been actively contributing to many other areas > of open

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

s a prior thread > > <http://lists.openstack.org/pipermail/openstack-dev/2018- > March/127882.html> > > about it. I was trying to get a solution within Cyborg, but that faces > > this race condition as well. > > > > IIUC, this situation is somewhat s

[openstack-dev] [nova] The createBackup API

There is spec proposal to fix a bug of createBackup API with microversion. ( https://review.openstack.org/#/c/511825/) When rotation parameter is '0', the createBackup API just do a snapshot, and then delete all the snapshots. That is meaningless behavier. But there is thing hope to get wider sug

Re: [openstack-dev] [placement][nova] Decision time on granular request groups for like resources

I'm trying so hard to catch up the discussion since I lost few.., it is really hard... In my mind , I'm always thinking the request group is only about binding the trait and the resource class together. Also thinking about whether we need a explicit tree structure to describe the request. So sound

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

2018-04-24 5:51 GMT+08:00 Arvind N : > Thanks for the detailed options Matt/eric/jay. > > Just few of my thoughts, > > For #1, we can make the explanation very clear that we rejected the > request because the original traits specified in the original image and the > new traits specified in the new

Re: [openstack-dev] [nova][placement] Trying to summarize bp/glance-image-traits scheduling alternatives for rebuild

2018-04-24 20:53 GMT+08:00 Eric Fried : > > The problem isn't just checking the traits in the nested resource > > provider. We also need to ensure the trait in the exactly same child > > resource provider. > > No, we can't get "granular" with image traits. We accepted this as a > limitation for t

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

2018-05-17 1:24 GMT+08:00 Jay Pipes : > On 05/16/2018 01:01 PM, Nadathur, Sundar wrote: > >> Hi, >> The Cyborg quota spec [1] proposes to implement a quota (maximum >> usage) for accelerators on a per-project basis, to prevent one project >> (tenant) from over-using some resources and starving

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

2018-05-17 9:38 GMT+08:00 Alex Xu : > > > 2018-05-17 1:24 GMT+08:00 Jay Pipes : > >> On 05/16/2018 01:01 PM, Nadathur, Sundar wrote: >> >>> Hi, >>> The Cyborg quota spec [1] proposes to implement a quota (maximum >>> usage) for accelera

Re: [openstack-dev] [Cyborg] [Nova] Cyborg traits

I can help on it. 2018-05-31 21:49 GMT+08:00 Eric Fried : > Yup. I'm sure reviewers will bikeshed the names, but the review is the > appropriate place for that to happen. > > A couple of test changes will also be required. You can have a look at > [1] as an example to follow. > > -efried > > [1

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

Maybe I missed something. Is there anyway the nova-compute can know the resources are allocated from which child resource provider? For example, the host has two PFs. The request is asking one VF, then the nova-compute needs to know the VF is allocated from which PF (resource provider). As my under

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

ell the difference at that point, then it actually > doesn't matter.) > > [1] https://review.openstack.org/#/c/511879/ > > On 06/05/2018 09:05 AM, Alex Xu wrote: > > Maybe I missed something. Is there anyway the nova-compute can know the > > resources are allocated from which child reso

Re: [openstack-dev] [Cyborg] [Nova] Cyborg traits

After reading the spec https://review.openstack.org/#/c/554717/14/doc/specs/rocky/cyborg-nova-sched.rst , I confuse on the CUSTOM_ACCELERATOR_FPGA meaning. Initially, I thought it means a region. But after reading the spec, it can be a device, a region or a function. Is it on purpose design? Sound

Re: [openstack-dev] [nova] Nominating Stephen Finucane for nova-core

+1 2016-12-02 23:22 GMT+08:00 Matt Riedemann : > I'm proposing that we add Stephen Finucane to the nova-core team. Stephen > has been involved with nova for at least around a year now, maybe longer, > my ability to tell time in nova has gotten fuzzy over the years. > Regardless, he's always been

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

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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

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

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] [api][zun] Effective URL for resource actions

Yea, looks like no consensus at here. Look at the discussion Chris pointed to, the "/containers//action" sounds a good API for tasks. But we also see the disadvantage for it. When we want to use URL to identifying an action, we found all the actions into a single API. We faced this problem multipl

Re: [openstack-dev] [api][zun] Effective URL for resource actions

2016-12-20 11:34 GMT+08:00 Qiming Teng : > On Tue, Dec 20, 2016 at 10:14:49AM +0800, Alex Xu wrote: > > Yea, looks like no consensus at here. Look at the discussion Chris > pointed > > to, the "/containers//action" sounds a good API for tasks. > > Did you mean &q

<    1   2   3   4   >