[Yahoo-eng-team] [Bug 2013228] [NEW] Non-admin users unable to create SR-IOV switch dev ports

Public bug reported: Currently only admin users can create SR-IOV direct ports that are marked as switch_dev, i.e. the ones that do OVS hardware offload. If we use Neutron RBAC to allow access to the binding profile, users can create big problems by modifying it after port binding when nova has s

[Yahoo-eng-team] [Bug 1974070] [NEW] Ironic builds fail when landing on a cleaning node, it doesn't try to reschedule

s you just deleted. In an idea world this would trigger a re-schedule, a bit like when you hit errors in the resource tracker such as ComputeResourcesUnavailable ** Affects: nova Importance: Low Assignee: John Garbutt (johngarbutt) Status: In Progress ** Changed in: nova S

[Yahoo-eng-team] [Bug 1891346] Re: Cannot delete nova-compute service due to service ID conflict

** Changed in: nova Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1891346 Title: Cannot delete nova-compute service due to service ID co

[Yahoo-eng-team] [Bug 1835400] [NEW] Issues booting with os_distro=centos7.0

Public bug reported: If we have os_distro=centos this isn't known by os-info, so we get: Cannot find OS information - Reason: (No configuration information found for operating system centos7): OsInfoNotFound: No configuration information found for operating system centos7 If we "fix" it to os_di

[Yahoo-eng-team] [Bug 1525101] Re: floating ip info is not updated correctly when remove a fix ip which is associated to a floating ip

*** This bug is a duplicate of bug 1444966 *** https://bugs.launchpad.net/bugs/1444966 Because we have deprecated this API, I have marked it as will not fix. ** Changed in: nova Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Yahoo!

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

Hi, Basically we should kill quota classes. It required out of tree stuff that was never implemented, AFAIK. When I checked with Kevin about this, my memory says the idea was out of tree authorization plugin would populate context.quota_class with something like "i_have_big_credit_limit" or "i_h

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

Back to the deprecation for a moment... My plan was to tell folks to use Traits to influence placement decisions, rather than capabilities. We probably can't remove the feature till we have deploy templates, but it seems wrong not to warn our users to avoid using capabilities, when 80% of the use

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Fri, 28 Sep 2018 at 00:46, Jay Pipes wrote: > On 09/27/2018 06:23 PM, Matt Riedemann wrote: > > On 9/27/2018 3:02 PM, Jay Pipes wrote: > >> A great example of this would be the proposed "deploy template" from > >> [2]. This is nothing more than abusing the placement traits API in > >> order to

Re: [Openstack-operators] [openstack-dev] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Thu, 20 Sep 2018 at 16:02, Matt Riedemann wrote: > On 9/20/2018 4:16 AM, John Garbutt wrote: > > Following on from the PTG discussions, I wanted to bring everyone's > > attention to Nova's plans to deprecate ComputeCapabilitiesFilter, > > including most of

Re: [openstack-dev] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Thu, 20 Sep 2018 at 16:02, Matt Riedemann wrote: > On 9/20/2018 4:16 AM, John Garbutt wrote: > > Following on from the PTG discussions, I wanted to bring everyone's > > attention to Nova's plans to deprecate ComputeCapabilitiesFilter, > > including most of

Re: [Openstack-operators] [openstack-dev] [all] Consistent policy names

tl;dr +1 consistent names I would make the names mirror the API ... because the Operator setting them knows the API, not the code Ignore the crazy names in Nova, I certainly hate them Lance Bragstad wrote: > I'm curious if anyone has context on the "os-" part of the format? My memory of the Nov

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

tl;dr +1 consistent names I would make the names mirror the API ... because the Operator setting them knows the API, not the code Ignore the crazy names in Nova, I certainly hate them Lance Bragstad wrote: > I'm curious if anyone has context on the "os-" part of the format? My memory of the Nov

[Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

if anyone has needs that the ResourceClass and Traits scheme does not currently address, or can think of a problem with a transition to the newer approach. Many thanks, John Garbutt IRC: johnthetubaguy ___ OpenStack-operators mailing list OpenStack-o

[openstack-dev] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

if anyone has needs that the ResourceClass and Traits scheme does not currently address, or can think of a problem with a transition to the newer approach. Many thanks, John Garbutt IRC: johnthetubaguy __ OpenStack Development

Re: [openstack-dev] [nova] Review runways this cycle

Hi So I am really excited for us to try runways out, ASAP. On 20 March 2018 at 23:44, melanie witt wrote: > We were thinking of starting the runways process after the spec review > freeze (which is April 19) so that reviewers won't be split between spec > reviews and reviews of work in runways.

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

On 23 January 2018 at 04:04, Ed Leafe wrote: > On Jan 22, 2018, at 5:09 PM, Matt Riedemann wrote: > > To anyone that cares, I don't plan on running for Nova PTL again for the > Rocky release. Queens was my fourth tour and it's definitely time for > someone else to get the opportunity to lead her

[openstack-dev] [ironic] Remove in-tree policy and config?

Hi, While I was looking at the traits work, I noticed we still have policy and config in tree for ironic and ironic inspector: http://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/policy.json.sample http://git.openstack.org/cgit/openstack/ironic/tree/etc/ironic/ironic.conf.sample http:/

[Yahoo-eng-team] [Bug 1724524] Re: Ironic nodes report CUSTOM_CUSTOM_FOO resource class

longer affects: nova/pike ** Changed in: nova Status: In Progress => Won't Fix ** Changed in: nova Assignee: John Garbutt (johngarbutt) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenSt

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

On 19 October 2017 at 15:38, Jay Pipes wrote: > On 10/16/2017 05:31 AM, Nisha Agarwal wrote: > >> Hi Matt, >> >> As i understand John's spec https://review.openstack.org/#/c/507052/ < >> https://review.openstack.org/#/c/507052/>, it is actually a replacement >> for capabilities(qualitative only)

[Yahoo-eng-team] [Bug 1724589] [NEW] Unable to transition to Ironic Node Resource Classes in Pike

Public bug reported: In Pike we ask people to: * Update Ironic Node with a Resource Class * Update flavors to request the new Resource Class (and not request VCPU, RAM, DISK), using the docs: https://docs.openstack.org/ironic/latest/install/configure-nova-flavors.html#scheduling-based-on-resour

[Yahoo-eng-team] [Bug 1724524] [NEW] Ironic nodes report CUSTOM_CUSTOM_FOO resource class

shows CUSTOM_CUSTOM_FOO resources ** Affects: nova Importance: High Assignee: John Garbutt (johngarbutt) Status: In Progress ** Tags: placement -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute

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

On 16 October 2017 at 17:55, Eric Fried wrote: > * Adding references to the specs: ironic side [1]; nova side [2] (which > just merged). > > * Since Jay is on vacation, I'll tentatively note his vote by proxy [3] > that ironic should be the source of truth - i.e. option (a). I think > the upshot

Re: [openstack-dev] [doc][ptls][all] Documentation publishing future

On Mon, 22 May 2017 at 10:43, Alexandra Settle wrote: > We could also view option 1 as the longer-term goal, > and option 2 as an incremental step toward it +1 doing option 2 then option 1. It just seems a good way to split up the work. Thanks, johnthetubaguy

Re: [Openstack-operators] [openstack-dev] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

+1 on not forcing Operators to transition to something new twice, even if we did go for option 3. Do we have an agreed non-distruptive upgrade path mapped out yet? (For any of the options) We spoke about fallback rules you pass but with a warning to give us a smoother transition. I think that's my

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

+1 on not forcing Operators to transition to something new twice, even if we did go for option 3. Do we have an agreed non-distruptive upgrade path mapped out yet? (For any of the options) We spoke about fallback rules you pass but with a warning to give us a smoother transition. I think that's my

[openstack-dev] [forum] Writing applications for the VM and Baremetal Platform

A quick summary of what happened in the writing applications for the VM and Baremetal forum session. The etherpad is available here: https://etherpad.openstack.org/p/BOS-forum-using-vm-and-baremetal We had a good number of API users and API developers talking together about the issues facing API u

[Openstack-operators] [forum] [vm&bm] Action required to help improve Ops <-> Dev feedback loops

These are my reflections on the three VM and Baremetal working group sessions at the summit. Many thanks to everyone who was able to attend and helped kick start these discussions. The etherpad is available here: https://etherpad.openstack.org/p/BOS-forum-operating-vm-and-baremetal The first two o

[openstack-dev] [forum] [vm&bm] Action required to help improve Ops <-> Dev feedback loops

Hi, On the ops list I have started a thread about the forum session sumary and the actions needed to keep things going. Please do join in over there: http://lists.openstack.org/pipermail/openstack-operators/2017-May/013448.html Many thanks, johnthetubaguy

Re: [openstack-dev] [nova] Boston Forum session recap - claims in the scheduler (or conductor)

gt;> filtering such that hosts are grouped by cell and then they can be sent >>> to the cells for retries as necessary. >>> >> >> That's already proposed for reviews in >> https://review.openstack.org/#/c/465175/ >> >> >>> There was als

Re: [openstack-dev] [tc][swg] Updates on the TC Vision for 2019

On 17 May 2017 at 20:02, Dean Troyer wrote: > On Wed, May 17, 2017 at 1:47 PM, Doug Hellmann wrote: >> The timeline depends on who signed up to do the next revision. Did >> we get someone to do that, yet, or are we still looking for a >> volunteer? (Note that I am not volunteering here, just ask

Re: [openstack-dev] [tc][all] Do we need a #openstack-tc IRC channel

On 16 May 2017 at 16:08, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2017-05-16 10:49:54 -0400: >> On 05/16/2017 09:38 AM, Davanum Srinivas wrote: >> > Folks, >> > >> > See $TITLE :) >> > >> > Thanks, >> > Dims >> >> I'd rather avoid #openstack-tc and just use #openstack-dev. >> #

[Openstack-operators] [forum] An experiment to help improve feedback loops, please get involved.

Hi, I am trying an experiment to improve the User/Dev/Ops feedback loops in the following Forum sessions: Mon 11:15am-11:55am - Operating the VM and Baremetal platform (1/2) Wed 11:00am-11:40am - Operating the VM and Baremetal platform (2/2) https://etherpad.openstack.org/p/BOS-forum-operating-vm

Re: [openstack-dev] [nova] Compute Node restart

On 27 April 2017 at 06:45, Ajay Kalambur (akalambu) wrote: > I am just issuing a reboot command on the compute node > > Not a reboot –f > > From: Mark Mielke > Date: Wednesday, April 26, 2017 at 8:42 PM > To: "OpenStack Development Mailing List (not for usage questions)" > , Ajay Kalambur > Subj

Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

On 28 April 2017 at 12:17, Sean Dague wrote: > On 04/28/2017 12:50 AM, Blair Bethwaite wrote: >> We at Nectar are in the same boat as Mike. Our use-case is a little >> bit more about geo-distributed operations though - our Cells are in >> different States around the country, so the local glance-ap

Re: [openstack-dev] [nova] Owners needed for approved but orphaned OSIC blueprints

Hi, Matt, thanks for pulling that list together. I have context on most of those, if people would like to take those on. I hope to review most of those an clarify where everything is at. I am going to take a look at where we are at with policy stuff first. Thanks, johnthetubaguy On 24 April 20

Re: [openstack-dev] [tc][election] Questions for Candidates

On 12 April 2017 at 17:19, Kendall Nelson wrote: > -What is one trait you have that makes it difficult to work in groups like > the TC and how do you counteract it? My inability to say no to more work (and being too interested in everything). I think I am slowly getting better at focusing, deleg

Re: [openstack-dev] [tc][elections]questions about one platform vision

On 12 April 2017 at 12:04, Davanum Srinivas wrote: > On Wed, Apr 12, 2017 at 6:51 AM, John Garbutt wrote: >> On 12 April 2017 at 03:54, joehuang wrote: >>> What's the one platform will be in your own words? What's your proposal and >>> your focus to he

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 12 April 2017 at 10:07, Thierry Carrez wrote: > Ildiko Vancsa wrote: >>> On 2017. Apr 12., at 3:18, Monty Taylor >> > wrote: >>> [...] >>> Email allows someone to compose an actual structured narrative, and >>> for replies to do the same. Some of us are loquatious a

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 11 April 2017 at 09:58, Thierry Carrez wrote: > Matt Riedemann wrote: >> Lots of projects have alternating meeting times to accommodate >> contributors in different time zones, especially Europe and Asia. >> >> The weekly TC meeting, however, does not. >> >> I have to assume this has come up be

Re: [openstack-dev] [tc][elections]questions about one platform vision

On 12 April 2017 at 03:54, joehuang wrote: > What's the one platform will be in your own words? What's your proposal and > your focus to help one platform vision being achieved? The more I think about this, the less I like the phrase "one platform". I like to think of OpenStack as group of const

Re: [openstack-dev] [ironic][nova] Suggestion required on pci_device inventory addition to ironic and its subsequent changes in nova

On 10 April 2017 at 11:31, wrote: > On Mon, 2017-04-10 at 11:50 +0530, Nisha Agarwal wrote: >> Hi team, >> >> Please could you pour in your suggestions on the mail? >> >> I raised a blueprint in Nova for this https://blueprints.launchpad.ne >> t/nova/+spec/pci-passthorugh-for-ironic and two RFEs

Re: [openstack-dev] [tc] [elections] Available time and top priority

On 10 April 2017 at 10:16, Thierry Carrez wrote: > All the candidates are top community members with a lot of > responsibilities on their shoulders already. My experience tells me that > it is easy to overestimate the time we can dedicate to Technical > Committee matters, and how much we can push

Re: [openstack-dev] [nova] allow_instance_snapshots config option is not used consistently

On 10 April 2017 at 01:56, Matt Riedemann wrote: > I found a fun little legacy nugget of compute API non-interoperability joy > tonight. > > The "allow_instance_snapshots" config option disables the createImage server > action API. Completely config driven and therefore not discoverable. > > What

[openstack-dev] [nova] remove-mox-pike blueprint

Hi, I added some notes on the blueprint: https://blueprints.launchpad.net/nova/+spec/remove-mox-pike I have seen quite a few patches trying to remove the use of "self.stub_out". While possibly interesting in the future, I think this should be out of scope for the mox removal blueprint. The aim of

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 15 March 2017 at 12:33, Sean Dague wrote: > On 03/15/2017 08:10 AM, John Garbutt wrote: >> On 15 March 2017 at 11:58, Jay Pipes wrote: >>> On 03/15/2017 07:44 AM, Sean Dague wrote: >>>> >>>> On 03/14/2017 11:00 PM, Monty Taylor wrote: >>>&g

Re: [openstack-dev] [nova] [notification] BlockDeviceMapping in InstancePayload

On 13 March 2017 at 17:14, Balazs Gibizer wrote: > Hi, > > As part of the Searchlight integration we need to extend our instance > notifications with BDM data [1]. As far as I understand the main goal is to > provide enough data about the instance to Searchlight so that Nova can use > Searchlight

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 13 March 2017 at 21:10, Zane Bitter wrote: > Yes. this is a problem with the default policy - if you have *any* role in a > project then you get write access to everything in that project. I don't > know how I can even call this role-based, since everybody has access to > everything regardless

Re: [openstack-dev] [nova] [placement] experimenting with extracting placement

On 13 March 2017 at 15:17, Jay Pipes wrote: > On 03/13/2017 11:13 AM, Dan Smith wrote: >> >> Interestingly, we just had a meeting about cells and the scheduler, >> which had quite a bit of overlap on this topic. >> >>> That said, as mentioned in the previous email, the priorities for Pike >>> (and

Re: [openstack-dev] [swg][tc] Moving Stewardship Working Group meeting

On 15 March 2017 at 09:50, Thierry Carrez wrote: > Colette Alexander wrote: >> Currently the Stewardship Working Group meetings every other Thursday at >> 1400 UTC. >> >> We've had a couple of pings from folks who are interested in joining us >> for meetings that live in US Pacific Time, and that

Re: [openstack-dev] [oslo][devstack][all] ZooKeeper vs etcd for Tooz/DLM

On 15 March 2017 at 11:58, Jay Pipes wrote: > On 03/15/2017 07:44 AM, Sean Dague wrote: >> >> On 03/14/2017 11:00 PM, Monty Taylor wrote: >> >>> >>> a) awesome. when the rest of this dips momentarily into words that might >>> sound negative, please hear it all wrapped in an "awesome" and know tha

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On 15 March 2017 at 03:23, Monty Taylor wrote: > On 03/15/2017 12:05 AM, Joshua Harlow wrote: >> So just fyi, this has been talked about before (but prob in context of >> zookeeper or various other pluggable config backends). >> >> Some links: >> >> - https://review.openstack.org/#/c/243114/ >> -

Re: [openstack-dev] [nova][docs] Broken nova instructions

On 9 March 2017 at 11:05, Alexandra Settle wrote: > I have attached the error logs that our tester, Brian Moss, sent to me > earlier this morning. > He has noted that some people have been able to get the instructions to work, > but many others haven't. > Also, noted that some are failing on Ubu

[Yahoo-eng-team] [Bug 1523668] Re: valid instance name before proceed

*** This bug is a duplicate of bug 1603728 *** https://bugs.launchpad.net/bugs/1603728 ** This bug has been marked a duplicate of bug 1603728 search with error regex causes a 500 error -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subs

[Yahoo-eng-team] [Bug 1669746] [NEW] sample config for host is unclear

Public bug reported: When we default the host and my_ip setting using oslo_config we end up reporting the details of the infra worker that generated the docs. We should make use of the sample default to add some text that looks better in the docs. In addition the description of host doesn't menti

Re: [openstack-dev] [nova][keystone] Pike PTG recap - quotas

On 27 February 2017 at 21:18, Matt Riedemann wrote: > We talked about a few things related to quotas at the PTG, some in > cross-project sessions earlier in the week and then some on Wednesday > morning in the Nova room. The full etherpad is here [1]. > > Counting quotas > --- > > Mela

[Yahoo-eng-team] [Bug 1607350] Re: floating-ip info doesn't contain information about instance if associated (with nova network installation)

While this bug is correct, this feature has now been deprecated, and is bug frozen. ** Changed in: nova Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.l

[Yahoo-eng-team] [Bug 1662626] [NEW] live-migrate left in migrating as domain not found

e 2701, in undefine 2017-02-05 02:33:46.364 19770 ERROR nova.compute.manager [instance: 62034d78-3144-4efd-9c2c-8a792aed3d6b] if ret == -1: raise libvirtError ('virDomainUndefine() failed', dom=self) 2017-02-05 02:33:46.364 19770 ERROR nova.compute.manager [instance: 62034d78-3144-4

Re: [openstack-dev] [nova] Final mascot

On 3 February 2017 at 02:59, Matt Riedemann wrote: > The Foundation wants to have the mascots finalized before the PTG. This is > just an opportunity for people to raise issues with it if they have any. Honestly it looks a bit aggressive / sharp / pointy. Maybe less spikes on the outside? I duno.

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

On 26 January 2017 at 14:14, Ed Leafe wrote: > On Jan 26, 2017, at 7:50 AM, Sylvain Bauza wrote: >> >> That's where I think we have another problem, which is bigger than the >> corner case you mentioned above : when upgrading from Newton to Ocata, >> we said that all Newton computes have be upgra

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

On 26 January 2017 at 13:50, Sylvain Bauza wrote: > Le 26/01/2017 05:42, Matt Riedemann a écrit : >> This is my public hand off to Sylvain for the work done tonight. >> > > Thanks Matt for your help yesterday, was awesome to count you in even > you're personally away. > > >> Starting with the mult

Re: [openstack-dev] [swg][tc] An attempt to clarify/discuss: what exactly is the Stewardship Working Group, anyhow?

On 8 December 2016 at 15:33, Thierry Carrez wrote: > Colette Alexander wrote: >> [...] >> What are the sorts of things you'd like to see tackled? > > John Garbutt recently proposed that the TC works on defining visions for > itself[1] and OpenStack in general[2] an

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

+1 from me. He will be a great add. I really enjoyed working with him as part of OSIC early on in his Nova journey, and I trust him to a great job as part of the core team. John On Sun, 4 Dec 2016 at 00:00, Michael Still wrote: > +1, I'd value him on the team. > > Michael > > On Sat, Dec 3, 20

Re: [openstack-dev] [nova] [telemetry] PostgreSQL gate broken

On 24 November 2016 at 13:52, Chris Friesen wrote: > On 11/24/2016 05:57 AM, Julien Danjou wrote: >> >> Hi, >> >> It seems Nova broke its PostgreSQL support recently, and that impacts >> Telemetry as we do gate on PostgreSQL. I opened a bug: >> >>https://bugs.launchpad.net/nova/+bug/1644513 >>

[Yahoo-eng-team] [Bug 1580967] Re: nova limits does not show keypair count properly

So the problem here is keypairs are owned by the user, and not owned by the tenant. The API you mention lists what a tenant has used, and any limits that apply to the tenant. So in this case, the API is saying for every user in the tenant they are allowed 100 keypairs. In a similar way, every ser

[Yahoo-eng-team] [Bug 1580552] Re: Developer Guide: Nova API v2 is deprecated

As per my previous comments, the v2.0 API is not deprecated. Once version of the code behind the API was deprecated and has been removed. The Public API should be just as it always was, and should keep working. ** Changed in: nova Status: In Progress => Won't Fix ** Changed in: nova

[Yahoo-eng-team] [Bug 1631918] [NEW] _determine_version_cap fails with MessagingTimeout when starting nova-compute

process to exit, but it doesn't seem to quite fully exit the process. It seems like this happens only when CONF.upgrade_levels.compute = "auto" This was spotted in this OSA change: https://review.openstack.org/#/c/367752 ** Affects: nova Importance: Medium Assigne

[openstack-dev] [all] Cross Project Summit Sessions Planning

Hi, In Barcelona, between Tuesday 3:55pm (Oct 25) and Wednesday 2:55pm (Oct 26) we have some dedicated time to discuss and resolve some of the issues that span across our OpenStack Community. As before, we will be doing proposals for this via etherpad. Please propose items into here: https://ethe

[Yahoo-eng-team] [Bug 1616240] Re: Traceback in vif.py execv() arg 2 must contain only strings

So sbezverk_ confirmed the issue was the --config-dir that priv-sep was passing to the worker. I am looking into a fix for that now. ** Also affects: oslo.privsep Importance: Undecided Status: New ** Changed in: nova Status: New => Invalid -- You received this bug notification

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

On 4 August 2016 at 14:18, Andrew Laski wrote: > On Thu, Aug 4, 2016, at 08:20 AM, Sean Dague wrote: >> On 08/03/2016 08:54 PM, Andrew Laski wrote: >> > I've brought some of these thoughts up a few times in conversations >> > where the Nova team is trying to decide if a particular change warrants

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

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 >> behavior in all cases at which point users can no longer rely on >> microversions to signal non breaking changes. And where we

Re: [openstack-dev] [ironic] [nova] [neutron] get_all_bw_counters in the Ironic virt driver

On 29 July 2016 at 19:58, Sean Dague wrote: > On 07/29/2016 02:29 PM, Jay Pipes wrote: >> On 07/28/2016 09:02 PM, Devananda van der Veen wrote: >>> On 07/28/2016 05:40 PM, Brad Morgan wrote: I'd like to solicit some advice about potentially implementing get_all_bw_counters() in the Ironi

Re: [openstack-dev] [ironic][neutron][nova] Sync port state changes.

On 26 July 2016 at 10:52, Sam Betts (sambetts) wrote: > On 26/07/2016 09:32, "John Garbutt" wrote: > >>On 22 July 2016 at 11:51, Vasyl Saienko wrote: >>> Kevin, thanks for reply, >>> >>> On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote: &g

Re: [openstack-dev] [ironic][neutron][nova] Sync port state changes.

On 22 July 2016 at 11:51, Vasyl Saienko wrote: > Kevin, thanks for reply, > > On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote: >> >> Hi, >> >> Once you solve the issue of getting the baremetal ports to transition to >> the ACTIVE state, a notification will automatically be emitted to Nova of

Re: [openstack-dev] [nova][neutron] neutron port duplication

On 22 July 2016 at 14:54, Andrey Volkov wrote: > Hi, nova and neutron teams, > > While booting new instance nova requests port for that instance in the > neutron. > It's possible to have a situation when neutron doesn't response due timeout > or connection break and nova retries port creation. It

Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven Tests (DDT)

On 25 July 2016 at 13:56, Bhor, Dinesh wrote: > > > -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Monday, July 25, 2016 5:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] Remove duplicate code using Data Driven > Tests (DDT) > > O

Re: [openstack-dev] [nova][scheduler] A simple solution for better scheduler performance

On 15 July 2016 at 09:26, Cheng, Yingxin wrote: > It is easy to understand that scheduling in nova-scheduler service consists > of 2 major phases: > A. Cache refresh, in code [1]. > B. Filtering and weighing, in code [2]. > > Couple of previous experiments [3] [4] shows that “cache-refresh” is th

[Yahoo-eng-team] [Bug 1599111] Re: HTTP exception thrown: Unexpected API Error

nova-docker is not part of upstream nova, or supported by upstream Nova. Moving to the nova-docker project. ** Also affects: nova-docker Importance: Undecided Status: New ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member o

[Yahoo-eng-team] [Bug 1537625] Re: invalid path for plugin skeleton in api_plugins.rst

This doc should not be fixed, it has now been removed. ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1537625 Title: i

[Yahoo-eng-team] [Bug 1558503] Re: Flavor m1.tiny could not be found Exception while creating instance

So I think this is actually python-novaclient. It checks to see if its a valid id, and correctly gets 404. This seems like the correct/expected behaviour. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineerin

[Yahoo-eng-team] [Bug 1504725] Re: rabbitmq-server restart twice, log is crazy increasing until service restart

** Changed in: nova Status: Confirmed => Invalid ** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1504725 Title: rabbitmq-server restart twice, log is cr

[Yahoo-eng-team] [Bug 1533867] Re: In cell mode and latest kilo code, nova get-vnc-console throw 500 error

Given this is for cells, and cells is now largely frozen code, marking as opinion. ** Changed in: nova Status: Confirmed => Opinion ** Tags added: cells -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (no

[Yahoo-eng-team] [Bug 1483236] Re: It´s not possible to disable the nova compute service on one compute node

So that behaviour is as designed. Disabled only stops new instances landing on that host. You can still manage your existing instances. The intent is to allow an admin to migrate or live-migrate instances off the host. I think we probably want some extra level of disabled to signal that existing

[Yahoo-eng-team] [Bug 1482029] Re: Delete "vm that has snapshot" spend more time

This is too old to be useful, let's kill this one. ** Changed in: nova Status: Confirmed => Incomplete ** Changed in: nova Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Comp

[Yahoo-eng-team] [Bug 1475655] Re: Unit_add call fails for fcp volumes when target port has not been configured

This sounds like something that needs fixing in the appropriate os-brick logic for system z ** Also affects: os-brick Importance: Undecided Status: New ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engi

[Yahoo-eng-team] [Bug 1475256] Re: sriov: VFs attributes (vlan, mac address) are not cleaned up after port delete

Looks like this got fixed in libvirt. ** Tags added: neutron sriov ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/

[Bug 1463911] Re: IPV6 fragmentation and mtu issue

** No longer affects: nova -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463911 Title: IPV6 fragmentation and mtu issue To manage notifications about this bug go to: https://bugs.launchpad.net/neu

[Yahoo-eng-team] [Bug 1463911] Re: IPV6 fragmentation and mtu issue

** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1463911 Title: IPV6 fragmentation and mtu issue Status in neutron: Confirmed Status in linux package in Ubunt

[Kernel-packages] [Bug 1463911] Re: IPV6 fragmentation and mtu issue

** No longer affects: nova -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1463911 Title: IPV6 fragmentation and mtu issue Status in neutron: Confirmed Status in linux package in Ubunt

[Yahoo-eng-team] [Bug 1461734] Re: duplicate detach volume in nova

So I think cinder has fixed this now they have improved state handling. It moves into the detaching state, which causes the duplicates to fail. We need to double check this again on master, so marking as invalid for now, while we wait for a valid repo steps and logs capturing the error that occurs

[Yahoo-eng-team] [Bug 1459542] Re: Move check whether instance is booted from volume from libvirt/driver.py to API

So this behaviour is correct. The volume size is inferred from the flavor, unless the user chooses otherwise. It's really not related. The quota and usage in Nova is only tracking local disk, cinder tracks all volumes. Given all that, marking this as invalid for now. ** Changed in: nova St

[Yahoo-eng-team] [Bug 1456474] Re: Nova-scheduler & Nova-cert stopped after server restart

So please report this issue with the package author. This is not an upstream bug, we have no packing upstream. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compu

[Bug 1452032] Re: Device descriptor not removed with different iqn and multipath enabled.

So to fix this on stable releases, the bug should be targeted for that stable release.this is still invalid for master. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bu

[Yahoo-eng-team] [Bug 1452032] Re: Device descriptor not removed with different iqn and multipath enabled.

So to fix this on stable releases, the bug should be targeted for that stable release.this is still invalid for master. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenSt

[Yahoo-eng-team] [Bug 1443796] Re: Missing dest type in block_device_mapping_v2

This wishlist bug has been open a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. This bug can be reopened (set back to "New") if someone decides to work on this. ** Changed in: nova Status: Co

[Yahoo-eng-team] [Bug 1439861] Re: encrypted iSCSI volume attach fails to attach when multipath-tools installed

*** This bug is a duplicate of bug 1439869 *** https://bugs.launchpad.net/bugs/1439869 ** This bug has been marked a duplicate of bug 1439869 encrypted iSCSI volume attach fails when iscsi_use_multipath is enabled -- You received this bug notification because you are a member of Yahoo! En

[Yahoo-eng-team] [Bug 1427522] Re: affinity server group is limited on one host

This wishlist bug has been open a year without any activity. I'm going to move it to "Opinion / Wishlist", which is an easily-obtainable queue of older requests that have come on. This bug can be reopened (set back to "New") if someone decides to work on this. ** Changed in: nova Status: Co

[Yahoo-eng-team] [Bug 1571839] Re: NoSuchOptError: no such option in group neutron: auth_plugin

*** This bug is a duplicate of bug 1574988 *** https://bugs.launchpad.net/bugs/1574988 This but has already been fixed here: https://github.com/openstack/nova/commit/2647f91ae97844a73176fc1c8663d9b186bdec1a ** This bug has been marked a duplicate of bug 1574988 -- You received this bug

[Yahoo-eng-team] [Bug 1569555] Re: Request is wrong for compute v2.1 os-flavor-access list

We should say Fix Released for this. ** Changed in: nova Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1569555 Title: Requ

[Yahoo-eng-team] [Bug 1412285] Re: InstanceInfoCacheNotFound exception

Looks like this got fixed, marking it as invalid. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1412285 Title:

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

On 15 June 2016 at 02:37, Sean Dague wrote: > On 06/14/2016 07:28 PM, Monty Taylor wrote: >> >> On 06/14/2016 05:42 PM, Doug Hellmann wrote: > > >> >> I think this is the most important thing to me as it relates to this. >> I'm obviously a huge proponent of clouds behaving more samely. But I >> a

  1   2   3   4   5   6   7   8   9   >