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

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

so FYI, in case people missing this spec, there is spec from John https://review.openstack.org/#/c/602201/3/specs/stein/approved/unified-limits-stein.rst@170 the roadmap of this spec is also saying deprecate the quota-class API. melanie witt 于2018年10月25日周四 上午3:54写道： > On Wed, 24 Oct 2018

Re: [openstack-dev] [nova] [ironic] agreement on how to specify options that impact scheduling and configuration

Jay Pipes 于2018年10月5日周五 下午9:25写道： > Added [ironic] topic. > > On 10/04/2018 06:06 PM, Chris Friesen wrote: > > While discussing the "Add HPET timer support for x86 guests" > > blueprint[1] one of the items that came up was how to represent what are > > essentially flags that impact both

Re: [openstack-dev] [placement] The "intended purpose" of traits

Sorry for append another email for something I missed to say. Alex Xu 于2018年9月29日周六 上午10:01写道： > > > Jay Pipes 于2018年9月29日周六 上午5:51写道： > >> On 09/28/2018 04:42 PM, Eric Fried wrote: >> > On 09/28/2018 09:41 AM, Balázs Gibizer wrote: >> >> On Fri, Sep 28

Re: [openstack-dev] [placement] The "intended purpose" of traits

Jay Pipes 于2018年9月29日周六 上午5:51写道： > On 09/28/2018 04:42 PM, Eric Fried wrote: > > On 09/28/2018 09:41 AM, Balázs Gibizer wrote: > >> On Fri, Sep 28, 2018 at 3:25 PM, Eric Fried wrote: > >>> It's time somebody said this. > >>> > >>> Every time we turn a corner or look under a rug, we find

Re: [openstack-dev] [placement] The "intended purpose" of traits

Chris Dent 于2018年9月29日周六 上午1:19写道： > On Fri, 28 Sep 2018, Jay Pipes wrote: > > > On 09/28/2018 09:25 AM, Eric Fried wrote: > >> It's time somebody said this. > > Yes, a useful topic, I think. > ++, I'm interesting this topic also, since it confuses me for a long time... > > >> Every time we

Re: [openstack-dev] [nova] When can/should we change additionalProperties=False in GET /servers(/detail)?

That only means after 599276 we only have servers API and os-instance-action API stopped accepting the undefined query parameter. What I'm thinking about is checking all the APIs, add json-query-param checking with additionalProperties=True if the API don't have yet. And using another

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

Fred Li 于2018年9月17日周一 上午8:25写道： > There are many wechat groups about OpenStack, some of them are regional > (like southern east China, Beijing, Xi'an group), some of them are event > oriented, and some are for others. Yes, you need to be invited, which is > not convenient. So far as I know there

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

I'm happy to be the translator or forwarder for the nova issue if you guys need(although, the nova team isn't happy with me now, also i see it is not to my personal. I guess they won't be make me hard for other work I do.). I can see there are a lot of Chinese operators/users complain some

Re: [openstack-dev] Nominating Chris Dent for placement-core

+1 Eric Fried 于2018年8月31日周五 下午11:45写道： > The openstack/placement project [1] and its core team [2] have been > established in gerrit. > > I hereby nominate Chris Dent for membership in the placement-core team. > He has been instrumental in the design, implementation, and stewardship > of the

Re: [openstack-dev] [nova] [placement] extraction (technical) update

2018-08-27 23:31 GMT+08:00 Matt Riedemann : > On 8/24/2018 7:36 AM, Chris Dent wrote: > >> >> Over the past few days a few of us have been experimenting with >> extracting placement to its own repo, as has been discussed at >> length on this list, and in some etherpads: >> >>

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

t in 2018. > > 5. In OpenStack we have a tradition of the contributors having a > strong degree of self-determination. If that tradition is to be > upheld, then it would make sense that the people who designed and > wrote the code that is being extracted would get to choose wh

Re: [openstack-dev] [Nova] A multi-cell instance-list performance test

2018-08-17 2:44 GMT+08:00 Dan Smith : > > yes, the DB query was in serial, after some investigation, it seems > that we are unable to perform eventlet.mockey_patch in uWSGI mode, so > > Yikun made this fix: > > > > https://review.openstack.org/#/c/592285/ > > Cool, good catch :) > > > > >

Re: [openstack-dev] [nova] How to debug no valid host failures with placement

2018-08-02 4:09 GMT+08:00 Jay Pipes : > On 08/01/2018 02:02 PM, Chris Friesen wrote: > >> On 08/01/2018 11:32 AM, melanie witt wrote: >> >> I think it's definitely a significant issue that troubleshooting "No >>> allocation >>> candidates returned" from placement is so difficult. However, it's

Re: [openstack-dev] [nova] keypair quota usage info for user

Oh, right, sorry, I'm keeping to think about its about the user in specific tenant usage just like other resources. You are right, Keypair has nothing about the tenant, only about the user. Thanks. 2018-07-26 23:22 GMT+08:00 Chris Friesen : > On 07/25/2018 06:22 PM, Alex Xu wr

Re: [openstack-dev] [nova] keypair quota usage info for user

2018-07-26 1:43 GMT+08:00 Chris Friesen : > On 07/25/2018 10:29 AM, William M Edmonds wrote: > >> >> Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM: >> ... snip ... >> > 1. is it ok to show the keypair used info via API ? any original >> > rational not to do so or it was just like that from

Re: [openstack-dev] [nova] keypair quota usage info for user

2018-07-26 0:29 GMT+08:00 William M Edmonds : > > Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM: > ... snip ... > > 1. is it ok to show the keypair used info via API ? any original > > rational not to do so or it was just like that from starting. > > keypairs aren't tied to a tenant/project, so

Re: [openstack-dev] [nova] keypair quota usage info for user

2018-07-25 17:44 GMT+08:00 Ghanshyam Mann : > Hi All, > > During today API office hour, we were discussing about keypair quota usage > bug (newton) [1]. key_pair 'in_use' quota is always 0 even when request per > user which is because it is being set as 0 always [2]. > > From checking the history

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

The version API isn't protected by the microversion, since the version API is used to discover the microversion. 2018-07-07 5:37 GMT+08:00 Matt Riedemann : > On 7/6/2018 6:28 AM, Kristi Nikolla wrote: > >> If the answer is 'no', can we find a process that gets us there? Or >> are we doomed >> by

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

2018-07-06 10:03 GMT+08:00 Alex Xu : > > > 2018-07-06 2:55 GMT+08:00 melanie witt : > >> +openstack-dev@ >> >> On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: >> >>> But, I can not use nova command, endpoint nova have been redirected fro

Re: [openstack-dev] [Openstack] [nova][api] Novaclient redirect endpoint https into http

2018-07-06 2:55 GMT+08:00 melanie witt : > +openstack-dev@ > > On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: > >> But, I can not use nova command, endpoint nova have been redirected from >>> https to http. Here:http://prntscr.com/k2e8s6 (command: nova –insecure >>> service list) >>>

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?

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

t 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 resource provider? For exampl

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

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 > >

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

2018-05-17 9:38 GMT+08:00 Alex Xu <sou...@gmail.com>: > > > 2018-05-17 1:24 GMT+08:00 Jay Pipes <jaypi...@gmail.com>: > >> On 05/16/2018 01:01 PM, Nadathur, Sundar wrote: >> >>> Hi, >>> The Cyborg quota spec [1] proposes to implement

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

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

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

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

[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

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

enstack-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 similar to the issue with vGPU types > > <http://eavesdrop.openstack.org/irclogs

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

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

rt both reprogrammable FPGA > 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

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

2018-03-07 10:21 GMT+08:00 Alex Xu <sou...@gmail.com>: > > > 2018-03-06 22:45 GMT+08:00 Mooney, Sean K <sean.k.moo...@intel.com>: > >> >> >> >> >> *From:* Matthew Booth [mailto:mbo...@redhat.com] >> *Sent:* Saturday, March 3, 2018 4:15 P

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:

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

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: > >

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:

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

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 >>

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

[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

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 *

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

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: > >

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 >

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:

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

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

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

[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] [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

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

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

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

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 <ke...@benton.pub>: > Not sure what you meant to link to, but that's not a spec. :) > > On Wed, Mar 29, 2017 at 11:21 P

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

sion about it. Feel free to reply 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 >> microversion 2

[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

[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] RFC for Intel RDT/CAT Support in Nova for Virtual Machine QoS

@Jay, actually I'm here for CAT. I also have another idea about the proposal, so catch you about it, let us sync all the ideas. :) Thanks Alex 2017-02-22 11:17 GMT-05:00 Jay Pipes : > Hi Eli, > > Sorry for top-posting. Just a quick note to say I had a good conversation > on

[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] placement/resource providers update 11

2017-02-11 0:10 GMT+08:00 Ed Leafe : > Your regular reporter, Chris Dent, is on PTO today, so I'm filling in. > I'll be brief. > > After the flurry of activity to get as much in before the Ocata RCs, this > past week was relatively calm. Work continued on the patch to have Ironic

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

Hi, We have weekly Nova API meeting tomorrow. And it is the time to talk about the plan of Pike. I created an etherpad for Pike ideas https://etherpad.openstack.org/p/nova-api-pike, please free feel to add ideas and comments. The meeting is being held Wednesday UTC1300 and irc channel is

Re: [openstack-dev] [nova] The status of servers API's filters

2017-01-29 1:31 GMT+08:00 Matt Riedemann <mriede...@gmail.com>: > On 1/27/2017 3:37 AM, Alex Xu wrote: > >> The patches about validation the filters and sorts for servers API are >> merged [0]. But we still have something left [1]. >> >> The left is about the

[openstack-dev] [nova] The status of servers API's filters

The patches about validation the filters and sorts for servers API are merged [0]. But we still have something left [1]. The left is about the proposal of introducing the new rule 'os_compute_api:servers:all_tenants_visible' which is soft enforcement. The new rule will instead of the old hard

[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] Device tag in the API breaks in the old microversion

2017-01-25 0:27 GMT+08:00 Matt Riedemann : > On 1/24/2017 9:18 AM, Matt Riedemann wrote: > >> >> First, thanks to Kevin and Alex for finding this issue and explaining it >> in detail so we can understand the scope. >> >> This is a nasty unfortunate issue which I really wish

[openstack-dev] [nova] Device tag in the API breaks in the old microversion

Unfortunately the device tag support in the API was broken in the old Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks to Kevin Zheng to find out that. Actually there are two bugs, just all of them are about device tag. The first one [0] is a mistake in the initial

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

2017-01-19 23:43 GMT+08:00 Sylvain Bauza : > > > Le 19/01/2017 16:27, Matt Riedemann a écrit : > > Sylvain and I were talking about how he's going to work placement > > microversion requests into his filter scheduler patch [1]. He needs to > > make requests to the placement API

Re: [openstack-dev] [nova] Different length limit for tags in object definition and db model definition

2017-01-17 10:26 GMT+08:00 Matt Riedemann : > On 1/16/2017 7:12 PM, Zhenyu Zheng wrote: > >> Hi Nova, >> >> I just discovered something interesting, the tag has a limited length, >> and in the current implementation, it is 60 in the tag object definition: >>

[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] placement/resource providers update 6

2017-01-07 5:55 GMT+08:00 Matt Riedemann : > On 12/16/2016 6:40 AM, Chris Dent wrote: > >> >> ## Resource Provider Traits >> >> There's been some recent activity on the spec for resource provider >> traits. These are a way of specifying qualitative resource >>

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

Happy new year! Start Nova API meeting again. 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, It is really close to the holidays. But we didn't say we will cancel the meeting. I will be there if there are people. Thanks __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

2016-12-20 11:34 GMT+08:00 Qiming Teng <teng...@linux.vnet.ibm.com>: > 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 go

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

[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] [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. >

Re: [openstack-dev] [Nova] Stepping back

Yea, thanks for all the help you give, and yes, I learned from you a lot also. Really sad lost one teacher. Wish all the best to you! Thanks Alex 2016-11-24 9:56 GMT+08:00 Ghanshyam Mann : > Thanks a lot alaski for your incredible contribution in Nova. You

[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 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] About doing the migration claim with Placement API

2016-11-03 4:52 GMT+08:00 Jay Pipes <jaypi...@gmail.com>: > On 11/01/2016 10:14 AM, Alex Xu wrote: > >> Currently we only update the resource usage with Placement API in the >> instance claim and the available resource update periodic task. But >> there is no clai

[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] About doing the migration claim with Placement API

2016-11-02 16:26 GMT+08:00 Sylvain Bauza <sba...@redhat.com>: > > > Le 01/11/2016 15:14, Alex Xu a écrit : > > Currently we only update the resource usage with Placement API in the > instance claim and the available resource update periodic task. But there >

[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] About doing the migration claim with Placement API

Currently we only update the resource usage with Placement API in the instance claim and the available resource update periodic task. But there is no claim for migration with placement API yet. This works is tracked by https://bugs.launchpad.net/nova/+bug/1621709. In newton, we only fix one bit

Re: [openstack-dev] [api] [nova] microversion edge case query

2016-10-19 0:58 GMT+08:00 Ed Leafe : > On Oct 18, 2016, at 11:01 AM, Chris Dent wrote: > > > > If the requested microversion is greater than the maximum, a 404 still > > makes some sense (no mapping _now_), but a 406 could as well because it > > provides a

[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] Can all virt drivers provide a disk 'id' for the diagnostics API?

2016-09-23 20:38 GMT+08:00 Daniel P. Berrange : > On Fri, Sep 23, 2016 at 07:32:36AM -0500, Matt Riedemann wrote: > > On 9/23/2016 3:54 AM, Daniel P. Berrange wrote: > > > On Thu, Sep 22, 2016 at 01:54:21PM -0500, Matt Riedemann wrote: > > > > Sergey is working on a spec to

Re: [openstack-dev] [nova] Latest news on placement API and Ocata rough goals

Again, that looks like a stretch goal to me, given how small we already > discussed about that yet. But sure, Ocata would be fine for discussing > first. > > Anyway, in conclusion, we've got a ton of work to do and I'm going to >> spend time before the summit trying to get good agree

[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 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] [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

[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

  1   2   3   4   >