Re: [openstack-dev] [Openstack-operators] [nova] Looking for feedback on a spec to limit max_count in multi-create requests

On 10/12/2017 4:09 AM, Saverio Proto wrote: Hello Matt, starting 1000 instances in production works for me already. We are on Openstack Newton. I described my configuration here: https://cloudblog.switch.ch/2017/08/28/starting-1000-instances-on-switchengines/ If things blow up for you with

Re: [openstack-dev] [nova] [ocata] nova-api error 404 instance not found

On 10/12/2017 6:56 AM, Kim-Norman Sahm wrote: You're right. i've used the "old" wsgi based nova api. after switch to nova-api binary is looks fine. Thanks Kim Great. I think we should probably delete those old unsupported wsgi files in stable/ocata since they won't work. When they were

Re: [openstack-dev] [nova] [ocata] nova-api error 404 instance not found

On 10/11/2017 3:48 AM, Kim-Norman Sahm wrote: Hi Matt, i'm using the ubuntu packages v15.0.6 the instances are mapped to the correct cell: mysql> select * from nova_api.instance_mappings where instance_uuid = -> "e564c631-896c-458c-93ab-b1c88f444fff";

Re: [openstack-dev] [nova] [ocata] nova-api error 404 instance not found

On 10/10/2017 3:53 AM, Kim-Norman Sahm wrote: Hi, i've upgraded from newton to ocata and i my last problem (i hope so) is in the nova-api. if i try to create a new instance (horizon or cli) i get an "404 instance no found" error but is instance is created and started as well. nova-api.log:

Re: [openstack-dev] Sydney Forum Topic Submission

On 9/21/2017 3:15 PM, Shamail Tahir wrote: You can expect the draft schedule to be released on October 9th, 2017. I still see a lot of unreviewed forum topic submissions: http://forumtopics.openstack.org/ Is there a plan to have that list narrowed down by end of week or early next week?

Re: [openstack-dev] [nova] Should we make rebuild + new image on a volume-backed instance fail fast?

On 10/6/2017 1:10 PM, Mathieu Gagné wrote: I don't think there ever was a technical limitation to add support for it. See the review comments with the -1 votes on the patches I linked originally. There are valid technical reasons for the -1s on those, including on this one from Paul Murray

[openstack-dev] [nova] Looking for feedback on a spec to limit max_count in multi-create requests

I've been chasing something weird I was seeing in devstack when creating hundreds of instances in a single request where at some limit, things blow up in an unexpected way during scheduling and all instances were put into ERROR state. Given the environment I was running in, this shouldn't have

[openstack-dev] [nova] Should we make rebuild + new image on a volume-backed instance fail fast?

This came up in IRC discussion the other day, but we didn't dig into it much given we were all (2 of us) exhausted talking about rebuild. But we have had several bugs over the years where people expect the root disk to change to a newly supplied image during rebuild even if the instance is

Re: [openstack-dev] [nova][ironic] Concerns over rigid resource class-only ironic scheduling

On 9/7/2017 2:48 PM, Nisha Agarwal wrote: Hi Ironic Operators, From Pike, ironic nodes get scheduled based on just the resource class from nova. Do you guys see any concerns over this "rigid resource class only ironic scheduling"? To be more specific, at your datacentre/production

Re: [openstack-dev] [Infra][Nova] Requesting +1/-1 reporting permission for s390x libvirt/kvm (zkvm) Nova CI

On 10/4/2017 8:11 AM, Jeremy Stanley wrote: It should just be a matter of one of the 5 nova-release group members (re?)adding your CI system's account at https://review.openstack.org/#/admin/groups/nova-ci when they're ready to do so. Done. -- Thanks, Matt

Re: [openstack-dev] [ptl][tc] Accessible upgrade support

On 10/3/2017 1:52 PM, Sean McGinnis wrote: I'm hoping this will get a little more attention. We recently started discussing removing governance tags that did not have any projects asserting them. I think this makes a lot of sense. Some tags were defined apparently in the hope that it would get

Re: [openstack-dev] [nova] key_pair update on rebuild (a whole lot of conversations)

On 10/3/2017 3:16 PM, Sean Dague wrote: There is currently a spec up for being able to specify a new key_pair name during the rebuild operation in Nova - https://review.openstack.org/#/c/375221/ For those not completely familiar with Nova operations, rebuild triggers the "reset this vm to

Re: [openstack-dev] [nova] Queens spec review sprint next week

On 10/2/2017 8:28 AM, Matt Riedemann wrote: On 9/28/2017 6:45 PM, Matt Riedemann wrote: Let's do a Queens spec review sprint. What day works for people that review specs? Monday came up in the team meeting today, but Tuesday could be good too since Monday's are generally evil. Let's do

Re: [openstack-dev] [all] Zuul v3 Status - and Rollback Information

On 10/3/2017 11:40 AM, Monty Taylor wrote: Our nodepool quota will be allocated 80% to Zuul v2, and 20% to ZUul v3.  This will slow v2 down slightly, but allow us to continue to exercise v3 enough to find problems. Zuul v2 and v3 can not both gate a project or set of projects.  In general,

Re: [openstack-dev] [nova] Should we allow passing new user_data during rebuild?

On 10/3/2017 10:53 AM, Matt Riedemann wrote: However, if the only reason one would need to pass personality files during rebuild is because we don't persist them during the initial server create, do we really need to also allow passing user_data for rebuild? Given personality files were

[openstack-dev] [nova] Should we allow passing new user_data during rebuild?

We plan on deprecating personality files from the compute API in a new microversion. The spec for that is here: https://review.openstack.org/#/c/509013/ Today you can pass new personality files to inject during rebuild, and at the PTG we said we'd allow passing new user_data to rebuild as a

Re: [openstack-dev] [Openstack-operators] [openstack-operators] [nova] Nova-scheduler filter, for domain level isolation

On 9/20/2017 5:17 AM, Georgios Kaklamanos wrote: Hello, Usecase: We have to deploy instances that belong in different domains, to different compute hosts. Does anyone else have the same usecase? If so, how did you implement it? [The rest of the mail is a more detailed explanation on the

Re: [openstack-dev] [nova] Queens spec review sprint next week

On 9/28/2017 6:45 PM, Matt Riedemann wrote: Let's do a Queens spec review sprint. What day works for people that review specs? Monday came up in the team meeting today, but Tuesday could be good too since Monday's are generally evil. Let's do the Queens spec review on Tuesday October 3rd

Re: [openstack-dev] [nova][stable] attn: No approvals for stable/newton right now

On 9/29/2017 7:31 PM, Dan Smith wrote: Hi all, Due to a zuulv3 bug, we're running an old nova-network test job on master and, as you would expect, failing hard. As a workaround in the meantime, we're[0] going to disable that job entirely so that it runs nowhere. This makes it not run on

[openstack-dev] [nova] Did you know archive_deleted_rows isn't super terrible anymore?

For awhile now actually. Someone was asking about when archive_deleted_rows would actually work, and the answer is, it should since at least mitaka: https://review.openstack.org/#/q/I77255c77780f0c2b99d59a9c20adecc85335bb18 And starting in Ocata there is the --until-complete option which

Re: [openstack-dev] [nova] Forum topics brainstorming

On 9/28/2017 4:45 PM, Matt Riedemann wrote: 2. Placement update and direction Same as the Cells v2 discussion - a Pike update and the focus items for Queens. This would also be a place we can mention the Ironic flavor migration to custom resource classes that happens in Pike. Someone else

[openstack-dev] [nova] Queens spec review sprint next week

Let's do a Queens spec review sprint. What day works for people that review specs? Monday came up in the team meeting today, but Tuesday could be good too since Monday's are generally evil. -- Thanks, Matt __

Re: [openstack-dev] [nova] Forum topics brainstorming

On 9/21/2017 4:01 PM, Matt Riedemann wrote: So this shouldn't be news now that I've read back through a few emails in the mailing list (I've been distracted with the Pike release, PTG planning, etc) [1][2][3] but we have until Sept 29 to come up with whatever forum sessions we want to propose

[openstack-dev] [nova] gate-grenade-dsvm-neutron-multinode-live-migration-nv job broken since ~8/18

I just noticed this today, but the gate-grenade-dsvm-neutron-multinode-live-migration-nv job in the nova check queue has been 100% fail since around August 18th. I've reported a bug with the details: https://bugs.launchpad.net/nova/+bug/1720191 It has something to do with

Re: [openstack-dev] [nova] reset key pair during rebuilding

On 9/23/2017 8:58 AM, LIU Yulong wrote: Hi nova developers, This mail is proposed to reconsider the key pair resetting of instance. The nova queens PTG discuss is here: https://etherpad.openstack.org/p/nova-ptg-queens  L498. And there are

Re: [openstack-dev] [tc][nova][ironic][mogan] Evaluate Mogan project

On 9/25/2017 6:27 AM, Zhenguo Niu wrote: Hi folks, First of all, thanks for the audiences for Mogan project update in the TC room during Denver PTG. Here we would like to get more suggestions before we apply for inclusion. Speaking only for myself, I find the current direction of one

Re: [openstack-dev] [nova] api.fault notification is never emitted

Cross-posting to the operators list since they are the ones that would care about this. Basically, the "notify_on_api_faults" config option hasn't worked since probably Kilo when the 2.1 microversion wsgi stack code was added. Rackspace added it back in 2012:

Re: [openstack-dev] vGPUs support for Nova

On 9/25/2017 5:40 AM, Jay Pipes wrote: On 09/25/2017 05:39 AM, Sahid Orentino Ferdjaoui wrote: There is a desire to expose the vGPUs resources on top of Resource Provider which is probably the path we should be going in the long term. I was not there for the last PTG and you probably already

Re: [openstack-dev] Garbage patches for simple typo fixes

On 9/22/2017 9:24 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote: Isn't it possible to ignore these patches in stackalytics? If the motivation is to look better there, this would solve the problem. That's a technical solution to a social problem. See my reply elsewhere in this thread. How

Re: [openstack-dev] Garbage patches for simple typo fixes

On 9/22/2017 9:59 AM, Matt Riedemann wrote: Figuring out what is useless or not is probably not worth the effort here. We already skip long running tempest dsvm jobs in certain patches, like with docs or unit test only changes. Updating a code comment in code isn't going to catch

Re: [openstack-dev] Garbage patches for simple typo fixes

On 9/22/2017 9:50 AM, Rajath Agasthya (rajagast) wrote: On 9/21/17, 10:19 PM, "Jeremy Freudberg" wrote: 3) Delay spin-up of resource-intensive/long-running CI jobs until after some initial review has been added or time has passed. Authorized contributors,

Re: [openstack-dev] Garbage patches for simple typo fixes

On 9/22/2017 7:10 AM, Tom Barron wrote: FWIW I think it is better not to attribute motivation in these cases. Perhaps the code submitter is trying to pad stats, but perhaps they are just a new contributor trying to learn the process with a "harmless" patch, or just a compulsive clean-upper who

[openstack-dev] Garbage patches for simple typo fixes

I just wanted to highlight to people that there seems to be a series of garbage patches in various projects [1] which are basically doing things like fixing a single typo in a code comment, or very narrowly changing http to https in links within docs. Also +1ing ones own changes. I've been

[openstack-dev] [nova] Your semi-monthly file injection and shelve mailer

Just thought everyone might like to know about this. I realized tonight that if you shelve an instance and it's offloaded, which is the default behavior, any injected files you had in the original instance are gone, and you can't specify them again on unshelve. We're awesome. The More You

Re: [openstack-dev] [nova] About live-resize spec

On 9/21/2017 3:13 AM, Claudiu Belu wrote: I don't know how soon the capabilities thing can become a real thing, but IMO, we can go with Matt's suggestion of disabling the feature by default through policy. I wouldn't hold my breath on a capabilities API, so I think a policy rule is what

Re: [openstack-dev] [Openstack-operators] [nova] Is there any reason to exclude originally failed build hosts during live migration?

On 9/21/2017 6:17 AM, Saverio Proto wrote: Why the change is called: Ignore original retried hosts when live migrating ? Isn't it implementing the opposite ? Dont Ignore ? Heh, you're right. I'll fix. Beyond that, any feedback on the actual intent here? -- Thanks, Matt

Re: [openstack-dev] [tc][nova][mogan] How to show respect to the original authors?

On 9/21/2017 11:55 AM, Mike Perez wrote: On 15:56 Sep 20, Flavio Percoco wrote: On 20/09/17 12:21 +, Jeremy Stanley wrote: On 2017-09-20 07:51:29 -0400 (-0400), Davanum Srinivas wrote: [...] please indicate which file from Nova, so if anyone wanted to cross check for fixes etc can go look

[openstack-dev] [nova] Forum topics brainstorming

So this shouldn't be news now that I've read back through a few emails in the mailing list (I've been distracted with the Pike release, PTG planning, etc) [1][2][3] but we have until Sept 29 to come up with whatever forum sessions we want to propose. There is already an etherpad for Nova [4].

[openstack-dev] [nova] Pike 16.0.1 bug fix release proposed

FYI, I've got a release proposed for Pike 16.0.1: https://review.openstack.org/#/c/505796/ This includes several bug fixes for regressions introduced in 16.0.0. A lot of these have to do with properly making allocations in Placement or cleaning up allocations from Placement during move

[openstack-dev] [nova] Is there any reason to exclude originally failed build hosts during live migration?

It's a weird question, so I'll explain. An issue came up in IRC today where someone was trying to live migrate an instance to a specified host, and the RetryFilter in the scheduler was kicking out the specified host, even though other similar instances were live migrating to that specified

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

On 9/20/2017 8:33 AM, Alex Xu wrote:  is there any use-case that people update server's metadata such frequently? If you have automation tooling updating the metadata for whatever reason it could be a problem. This was the reported bug FWIW: https://bugs.launchpad.net/nova/+bug/1650188

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

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['meta'] in the code)

Re: [openstack-dev] [nova] About live-resize spec

On 9/20/2017 12:16 AM, Chen CH Ji wrote: spec [1] has been there since 2014 and some patches proposed but abandoned after that, can someone please provide some info/background about why it's postponed or due to some limitations that nova hasn't been implemented yet? some operators suggested

Re: [openstack-dev] [nova] [notification] not transforming HostAPI related versioned notifications

On 9/20/2017 4:06 AM, Balazs Gibizer wrote: Do you feel we need something more user facing documentations about these decisions? No, this is fine. Thanks for explaining. -- Thanks, Matt __ OpenStack Development Mailing

Re: [openstack-dev] [nova] [notification] not transforming HostAPI related versioned notifications

On 9/19/2017 10:35 AM, Balazs Gibizer wrote: Hi, Similar to my earlier mail about not transforming legacy notifications in the networking area [1] now I want to propose not to transform HostAPI related notifications. We have the following legacy notifications on our TODO list [2] to be

[openstack-dev] [nova] live migration tests are top fail in CI right now

The live migration job is failing at a pretty high rate right now (around 50%). It's the top failure: http://status.openstack.org/elastic-recheck/#1718295 It looks like it started within the last 24 hours, but I'm not sure what would be causing it, as I don't see any nova changes related to

Re: [openstack-dev] [nova] Queens PTG recap - everything else

On 9/19/2017 7:52 AM, Belmiro Moreira wrote: I didn't find any mention to nested quotas. Was it discussed in the PTG? and what can we expect for Queens? There is no one driving the unified limits work [1] so nested quotas is stalled and we didn't spend any time discussing it at the PTG. [1]

[openstack-dev] [nova] Queens PTG recap - everything else

There was a whole lot of other stuff discussed at the PTG. The details are in [1]. I won't go into everything here, so I'm just highlighting some of the more concrete items that had owners or TODOs. Ironic -- The Ironic team came over on Wednesday afternoon. We talked a bit, had some

[openstack-dev] [nova][neutron] Queens PTG recap - nova/neutron

There were a few nova/neutron interactions at the PTG, one on Tuesday [1] and one on Thursday [2]. Priorities -- 1. Neutron port binding extension for live migration: This was discussed at the Ocata summit in Barcelona [3] and resulted in a Neutron spec [4] and API definition in

[openstack-dev] [nova][cinder] Queens PTG recap - nova/cinder

On Thursday morning at the PTG the Nova and Cinder teams got together to talk through some items. Details are in the etherpad [1]. Bug 1547142 [2] --- This is a long-standing bug where Nova does not terminate connections when shelve offloading an instance. There was some confusion

[openstack-dev] [nova] Queens PTG team photos

Here are the links to the Nova team photos from the PTG. https://photos.app.goo.gl/JoYZyouzm0J670mH3 https://photos.app.goo.gl/YMo96j6KKc044XdG2 -- Thanks, Matt __ OpenStack Development Mailing List (not for usage

[openstack-dev] [nova] Queens PTG recap - placement

Placement related items came up a lot at the Queens PTG. Some on Tuesday [1], some on Wednesday [2], some on Thursday [3] and some on Friday [4]. Priorities for Queens - The priorities for placement/scheduler related items in Queens are: 1. Migration allocations [5] - we

[openstack-dev] [nova] Queens PTG recap - cells

The full etherpad for cells discussions at the PTG is here [1]. We mostly talked about the limitations with multiple cells identified in Pike [2] and priorities. Top priorities for cells in Queens -- * Alternate hosts: with multiple cells in a tiered (super)

Re: [openstack-dev] [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 9/13/2017 9:52 AM, Arne Wiebalck wrote: On 13 Sep 2017, at 16:52, Matt Riedemann <mriede...@gmail.com> wrote: On 9/13/2017 3:24 AM, Arne Wiebalck wrote: I’m reviving this thread to check if the suggestion to address potentially stale connection data by an admin command (or a sch

Re: [openstack-dev] [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 9/13/2017 10:31 AM, Morgenstern, Chad wrote: I have been studying how to perform failover operations with Cinder --failover. Nova is not aware of the failover event. Being able to refresh the connection state especially for Nova would come in very handy, especially in admin level dr

Re: [openstack-dev] git review -d + git rebase changing author?

On 7/17/2017 6:31 PM, melanie witt wrote: On Tue, 18 Jul 2017 09:22:31 +0900, Ghanshyam Mann wrote: Yes, this is same case when we do fetch patch set using git checkout, i do not think its something to do with gite review -d. Doing that shouldn't change the author, at least in my experience.

Re: [openstack-dev] [Openstack-operators] [nova][cinder] Is there interest in an admin-api to refresh volume connection info?

On 9/13/2017 3:24 AM, Arne Wiebalck wrote: I’m reviving this thread to check if the suggestion to address potentially stale connection data by an admin command (or a scheduled task) made it to the planning for one of the upcoming releases? It hasn't, but we're at the PTG this week so I can

Re: [openstack-dev] [nova] [notification] cleaning up networking related notifications

On 9/8/2017 5:52 AM, Balazs Gibizer wrote: The addFixedIp REST API was deprecated in Pike [1] (in microversion 2.44). As a result the legacy create_ip.start and create_ip.end notifications will not be emitted after microversion 2.44. We had a TODO[2] to transform this notification to the

Re: [openstack-dev] [nova][ironic] Concerns over rigid resource class-only ironic scheduling

On 9/7/2017 2:48 PM, Nisha Agarwal wrote: Hi Ironic Operators, From Pike, ironic nodes get scheduled based on just the resource class from nova. Do you guys see any concerns over this "rigid resource class only ironic scheduling"? To be more specific, at your datacentre/production

[openstack-dev] [nova] Pike blueprint burndown chart

I sent a similar email after Ocata was released [1] and these are our blueprint burndown chart results for Pike [2]. Comparing to Ocata, the trends and numbers are nearly identical. Things ramp up until the spec freeze, then tail off, with a little spike toward the end which is generally

Re: [openstack-dev] [nova] Can we remove the monkey_patch_modules config option?

On 8/30/2017 1:16 PM, Lokesh Jain wrote: Hi Matt, Thank you for pointing this out and bringing this to my attention. We are using the monkey_patch options to add more nova capabilities. Specifically we are using it to replace Nova’s nova/network/neutronv2/api.get_port_vnic_info function for

Re: [openstack-dev] [nova] Should we add the 'force' option to the cold migrate API too?

On 8/30/2017 11:35 AM, Chris Friesen wrote: (We might even want to fail a live migration/evacuation with a forced destination that could cause a conflict in these non-shareable resources, but that'd be a behaviour change and therefore a new microversion.) That's

[openstack-dev] [nova] Should we add the 'force' option to the cold migrate API too?

Given the recent bugs [1][2] due to the force flag in the live migrate and evacuate APIs related to Placement, and some other long standing bugs about bypassing the scheduler [3], I don't think we should add the force option to the cold migrate API, as (re-)proposed in Takashi's cold migrate

[openstack-dev] [nova] How about a post test hook to dump allocations?

Chris and I were talking about the various bugs related to not cleaning up allocations during failures, of which I've reported two more today [1][2]. The discovery process here is really just me doing code inspection, then opening a bug, writing a recreate functional test and then fixing the

[openstack-dev] [nova] Pike retrospective

Like in Newton and Ocata, I've started an etherpad for a Pike retrospective: https://etherpad.openstack.org/p/nova-pike-retrospective We'll go over this at the PTG so please fill in your thoughts before that happens so we can try and come away with action items at the PTG. -- Thanks, Matt

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

On 8/22/2017 8:18 PM, Matt Riedemann wrote: 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 involved

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

On 8/25/2017 7:54 AM, Chris Dent wrote: * https://bugs.launchpad.net/nova/+bug/1712411 Allocations may not be removed from dest node during failed migrations Started with the functional recreate test patch: https://review.openstack.org/#/c/498627/ -- Thanks, Matt

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

On 8/28/2017 5:09 PM, Matt Riedemann wrote: There are some issues with this, mainly around the fact this is talking about scheduling, as I expect it to work today when I came into reading this, but it's talking in detail about the alternatives stuff which was not implemented in Pike, so I

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

On 8/25/2017 7:54 AM, Chris Dent wrote: There's a stack that documents (with visual aids!) the flow of scheduler and placement. It is pretty much ready: https://review.openstack.org/#/c/475810/ I see I am late to the party here, but I've left comments in the now-merged patch. There are

Re: [openstack-dev] [nova]notification update week 35

On 8/28/2017 10:52 AM, Balazs Gibizer wrote: [Undecided] https://bugs.launchpad.net/nova/+bug/1700496 Notifications are emitted per-cell instead of globally Devstack config has already been modified so notifications are emitted to the top level MQ. It seems that only a nova cells doc update is

Re: [openstack-dev] [nova] Can we remove the monkey_patch_modules config option?

On 8/28/2017 9:51 AM, Alex Schultz wrote: JFYI,https://review.openstack.org/#/c/494305/ Since this was just added, someone is looking to use it or is using it. Thanks for pointing this out. I've asked in the puppet review that the submitter of that change explain if/why they are using this

[openstack-dev] [nova] Can we remove the monkey_patch_modules config option?

I'm having a hard time tracing what this is necessary for. It's related to the notify_decorator which is around for legacy notifications but I don't actually see that decorator used anywhere. Given there are other options related to the notify_decorator, like "default_publisher_id" if we can

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

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 And another bug that Alex pointed out tonight not yet

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

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 involved which helps grow our contributor base. Beyond

Re: [openstack-dev] [ironic] [nova] [tripleo] heads up: custom resource classes, bare metal scheduling and you

On 8/22/2017 12:36 PM, Dmitry Tantsur wrote: All operators running ironic will have to set the resource class field before upgrading to Pike and change their flavors before upgrading to Queens. See our upgrade notes [6] for details. It might be worth mentioning that the ironic virt driver in

[openstack-dev] [nova] RequestSpec questions about force_hosts/nodes and requested_destination

I don't dabble in the RequestSpec code much, but in trying to fix bug 1712008 [1] I'm venturing in there and have some questions. This is mostly an email to Sylvain for when he gets back from vacation but I wanted to dump it before moving forward. Mainly, what is the difference between

Re: [openstack-dev] Minimum version of shred in our supported distros?

On 8/20/2017 1:11 AM, Michael Still wrote: Specifically we could do something like this: https://review.openstack.org/#/c/495532 Sounds like we're OK with doing this in Queens given the other discussion in this thread. However, this is part of a much larger series. It looks like it doesn't

Re: [openstack-dev] [Nova] On idmapshift deprecation

On 8/20/2017 3:28 AM, Michael Still wrote: I'm going to take the general silence on this as permission to remove the idmapshift binary from nova. You're welcome. The reality is that no one is using the LXC code as far as I know. Rackspace was the only one ever contributing changes for LXC

[openstack-dev] [nova] Things for next week (8/14-8/18)

Several cores are on vacation (myself, sdague, bauzas, stephenfin). RC1 is cut, and we know we have some things for RC2. Those are tracked at the top of the etherpad here: https://etherpad.openstack.org/p/nova-pike-release-candidate-todo dansmith is the only person on the release team that

[openstack-dev] [nova][docs] O search where art thou?

Before the great docs migration, searching for something in the nova devref was restricted to the nova devref: https://docs.openstack.org/nova/ocata/search.html?q=rbd_keywords=yes=default Now searching for something in the nova docs searches docs.o.o, ask.o.o, maybe other places, but it's

[openstack-dev] [nova] Thanks gibi!

Apparently we don't have community contributor awards at the PTG, only the summit, and seeing as that's several months away now, which is kind of an eternity, I wanted to take the time now to thank gibi (Balazs Gibizer to his parents) for all the work he's been doing in Nova. Not only does

[openstack-dev] [nova] Self-nomination for PTL in Queens

Hi everyone, This is my self-nomination to continue running as Nova PTL for the Queens cycle. If elected, this would be my fourth term as Nova PTL. While I try to continually improve, at this point I have a fairly steady way of doing things and most people are probably used to that by now.

Re: [openstack-dev] [all][barbican][freezer][horizon][karbor][keystone][mistral][nova][pack-deb][refstack][solum][storlets][swift][tacker][telemetry][watcher][zaqar] Last days for PTL candidate announ

On 8/7/2017 2:50 PM, Kendall Nelson wrote: Hello Everyone :) A quick reminder that we are in the last days for PTL candidate announcements. If you want to stand for PTL, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your

Re: [openstack-dev] [python-openstackclient][python-openstacksdk][neutron][nova] supporting resource extensions with our CLI

On 8/3/2017 1:39 PM, Boden Russell wrote: I think we have a gap in our OSC CLI for non-stadium plugin/driver projects (neutron plugin projects, nova driver projects) that implement RESTful resource API attribute extensions. For details, go directly to [1]. For a summary read on... For

Re: [openstack-dev] VMWare Type Snapshot for Openstack 4.3

On 8/4/2017 8:41 AM, Tom Kennedy wrote: Is there an Openstack document that shows how to extend openstack to do something like this? The create snapshot API is this in upstream Nova: https://developer.openstack.org/api-ref/compute/#create-image-createimage-action There is no distinction

Re: [openstack-dev] VMWare Type Snapshot for Openstack 4.3

On 8/3/2017 3:16 PM, Tom Kennedy wrote: I see that this is implemented in nova(nova/api/openstack/compute/contrib/server_snapshot.py) , but is not available in Horizon. I think you're looking at some forked code because that doesn't exist in upstream Nova:

[openstack-dev] [trove] Can we move some non-voting broken jobs to the experimental queue?

I don't dabble in Trove-land often but today I pushed a change and was watching it in zuul, and noticed that the change runs 26 jobs in the check queue. Several of those (cassandra, couch, mongo, percona) all failed nearly immediately with something in the diskimage builder, like this:

Re: [openstack-dev] Trying again on wait_for_compute in devstack

On 8/2/2017 10:04 AM, Matt Riedemann wrote: and we're not going to use it in multinode scenarios. Why would you not run this in multinode scenarios? That's the only time this is really a problem, because in the single node case we're discovering and mapping the compute node late enough

Re: [openstack-dev] Trying again on wait_for_compute in devstack

On 8/2/2017 6:17 AM, Sean Dague wrote: and we're not going to use it in multinode scenarios. Why would you not run this in multinode scenarios? That's the only time this is really a problem, because in the single node case we're discovering and mapping the compute node late enough that it's

[openstack-dev] [nova][docs] Concerns with docs migration

Now that Stephen Finucane is back from enjoying his youth and gallivanting all over Europe, and we talked about a few things in IRC this morning on the docs migration for Nova, I wanted to dump my concerns here for broader consumption. 1. We know we have to fix a bunch of broken links by

[openstack-dev] [nova] Working toward Pike RC1

Now that we're past feature freeze for Pike, I've started an etherpad for tracking items needed to get done before the first release candidate here: https://etherpad.openstack.org/p/nova-pike-release-candidate-todo Just a reminder but Pike RC1 is Thursday August 10th. -- Thanks, Matt

Re: [openstack-dev] [Cinder][Nova][Requirements] Lib freeze exception for os-brick

On 7/31/2017 5:21 PM, Tony Breeds wrote: We need a +1 from the release team (are they okay to accept a late release of glance_store); and a +1 from glance (are they okay to do said release) Glance doesn't actually need this minimum version bump for os-brick, the fix is for some attached

Re: [openstack-dev] [Cinder] Requirements for re-adding Gluster support

On 7/26/2017 4:16 PM, Eric Harney wrote: From a technical point of view there are not a lot of steps involved here, we can restore the previous gate jobs and driver code and I expect things would still be in working order. I can help coordinate these things with the new owner. Note that the

Re: [openstack-dev] [nova] hardware offload support for openvswitch feature exception

On 7/26/2017 10:42 PM, Moshe Levi wrote: Hi all, In the last few week I was working on hardware offload support for openvswitch. The idea is to leverage SR-IOV technology with OVS control plane management. Just last month the ovs community merged all the required patches to enable this

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/26/2017 11:34 AM, Matt Riedemann wrote: On 7/26/2017 11:23 AM, Matt Riedemann wrote: Given this, what else do you need? Please be clear about what your use case is and how it is not solved using the 2.53 microversion. There may need to be changes to the CLI but let's separate

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/26/2017 11:23 AM, Matt Riedemann wrote: Given this, what else do you need? Please be clear about what your use case is and how it is not solved using the 2.53 microversion. There may need to be changes to the CLI but let's separate that concern from the REST API changes. I think your

Re: [openstack-dev] [OpenStack-Dev][Nova] - https://launchpad.net/bugs/1667794 Changing hostname not to be treated as a pattern instead exact match will be done.

On 7/26/2017 12:24 AM, nidhi.h...@wipro.com wrote: Hello All, This is follow up mail on my y'days mail regarding bug _https://bugs.launchpad.net/python-novaclient/+bug/1667794_ It looks like all the cli commands that are related to http://10.141.67.190:8774/v2.1/os-hypervisors/wipro/servers api

Re: [openstack-dev] [nova][searchlight] status of an instance on the REST API and in the instance notifications

On 7/19/2017 10:54 AM, Balazs Gibizer wrote: On Wed, Jul 19, 2017 at 5:38 PM, McLellan, Steven wrote: Thanks Balazs for noticing and replying to my message! The Status field is quite important to us since it's the indicator of VM state that Horizon displays most

[openstack-dev] Heads up - nova conductor fleet round 2 is coming to devstack

The second iteration of the nova conductor fleet change to devstack is approved: https://review.openstack.org/#/c/477556/ The first attempt blew up a few jobs because of things like quotas and notifications which are now fixed on master, either in the devstack change itself (for

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

On 7/21/2017 6:54 AM, Chris Dent wrote: ## Custom Resource Classes for Ironic A spec for custom resource classes is being updated to reflect the need to update the flavor and allocations of a previously allocated ironic node that how has a custom resource class (such as CUSTOM_SILVER_IRON):

<    1   2   3   4   5   6   7   8   9   10   >