[Openstack-operators] [nova] Bug heads up: Significant increase in DB connections with cells since Newton

Hey Folks, I wanted to give everyone a heads up that we have found and fixed a bug [1] on master where the number of database connections had increased so much that we were starting to hit a "OperationalError (pymysql.err.OperationalError) (1040, u'Too many connections')" in the gate on some

Re: [Openstack-operators] [nova][ironic][scheduler][placement] IMPORTANT: Getting rid of the automated reschedule functionality

On Tue, 23 May 2017 20:58:20 +0100 (IST), Chris Dent wrote: If we're talking big crazy changes: Why not take the "small VM driver" (presumably nova-compute) out of Nova? What stays behind is _already_ orchestration but missing some features and having a fair few bugs. I've suggested this a cou

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

On Thu, 8 Jun 2017 08:58:20 -0500, Matt Riedemann wrote: Nova stores the output of the Cinder os-initialize_connection info API in the Nova block_device_mappings table, and uses that later for making volume connections. This data can get out of whack or need to be refreshed, like if your ceph

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

On Thu, 7 Sep 2017 14:57:24 -0500, Matt Riedemann wrote: Some more background information is in the ironic spec here: https://review.openstack.org/#/c/500429/ Also, be aware of these release notes for Pike related to baremetal scheduling: http://docs-draft.openstack.org/77/501477/1/check/gat

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

On Thu, 14 Sep 2017 11:15:26 -0600, Ed Leafe wrote: On Sep 14, 2017, at 10:30 AM, melanie witt wrote: I was thinking, if it's possible to assign more than one resource class to an Ironic node, maybe you could get similar behavior to the old non-exact filters. So if you have an od

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

On Wed, 20 Sep 2017 13:47:18 -0500, Matt Riedemann wrote: Presumably there was a good reason why the instance failed to build on a host originally, but that could be for any number of reasons: resource claim failed during a race, configuration issues, etc. Since we don't really know what origin

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

On Fri, 29 Sep 2017 13:49:55 -0500, Matt Riedemann wrote: 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 starti

Re: [Openstack-operators] CentOS upgrade killed my Liberty system

On Tue, 10 Oct 2017 09:59:03 -0700, Christopher Hull wrote: Browser hangs for a while then shows "Internal Server Error" /var/log/httpd/error shows this... [Tue Oct 10 09:32:53.860393 2017] [core:error] [pid 27391] [client 172.22.10.130:53239 ] End of script output

[Openstack-operators] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

Hello Stackers, This is a heads up to any of you using the AggregateCoreFilter, AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler. These filters have effectively allowed operators to set overcommit ratios per aggregate rather than per compute node in <= Newton. Beginning

Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi

> On Jan 25, 2018, at 21:23, Logan V. wrote: > > There is a small patch in the bug which resolves the config drive > ordering. Without that patch I don't know of any workaround. The > config drive will always end up first in the boot order and the > instance will always fail to boot in that situa

Re: [Openstack-operators] [openstack-dev] Race in FixedIP.associate_pool

> On Jan 29, 2018, at 16:45, Arun SAG wrote: > > If anyone is running into db race while running database in > master-slave mode with async replication, The bug has been identified > and getting fixed here > https://bugs.launchpad.net/oslo.db/+bug/1746116 Thanks for your persistence in tracking

Re: [Openstack-operators] [openstack-dev] [nova] Rocky PTG early planning

> On Jan 8, 2018, at 10:33, Matt Riedemann wrote: > > As the Queens release winds to a close, I've started thinking about topics > for Rocky that can be discussed at the PTG. > > I've created an etherpad [1] for just throwing various topics in there, > completely free-form at this point; just

Re: [Openstack-operators] [openstack-dev] [nova] The createBackup API

+openstack-operators Operator feedback wanted: do you have users that pass rotation parameter '0' to the createBackup API in order to delete backups? Do you have users using the createBackup API in general? On Fri, 30 Mar 2018 10:44:40 +0800, Alex Xu wrote: There is spec proposal to fix a bug

Re: [Openstack-operators] [nova] Rocky forum topics brainstorming

+openstack-operators (apologies that I forgot to add originally) On Mon, 9 Apr 2018 10:09:12 -0700, Melanie Witt wrote: Hey everyone, Let's collect forum topic brainstorming ideas for the Forum sessions in Vancouver in this etherpad [0]. Once we've brainstormed, we'll select

Re: [Openstack-operators] [nova] Rocky forum topics brainstorming

On Fri, 13 Apr 2018 08:00:31 -0700, Melanie Witt wrote: +openstack-operators (apologies that I forgot to add originally) On Mon, 9 Apr 2018 10:09:12 -0700, Melanie Witt wrote: Hey everyone, Let's collect forum topic brainstorming ideas for the Forum sessions in Vancouver in this etherp

[Openstack-operators] [nova] proposal to postpone nova-network core functionality removal to Stein

Hello Operators and Devs, This cycle at the PTG, we had decided to start making some progress toward removing nova-network [1] (thanks to those who have helped!) and so far, we've landed some patches to extract common network utilities from nova-network core functionality into separate utility

Re: [Openstack-operators] [openstack-dev] [nova] proposal to postpone nova-network core functionality removal to Stein

On Thu, 31 May 2018 15:04:53 -0500, Matt Riedemann wrote: On 5/31/2018 1:35 PM, melanie witt wrote: This cycle at the PTG, we had decided to start making some progress toward removing nova-network [1] (thanks to those who have helped!) and so far, we've landed some patches to extract c

[Openstack-operators] [nova] increasing the number of allowed volumes attached per instance > 26

Hello Stackers, Recently, we've received interest about increasing the maximum number of allowed volumes to attach to a single instance > 26. The limit of 26 is because of a historical limitation in libvirt (if I remember correctly) and is no longer limited at the libvirt level in the present

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

+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) First of all, it seems that the nova client is hitting /v2.1

[Openstack-operators] [nova] Denver Stein ptg planning

Hello Devs and Ops, I've created an etherpad where we can start collecting ideas for topics to cover at the Stein PTG. Please feel free to add your comments and topics with your IRC nick next to it to make it easier to discuss with you. https://etherpad.openstack.org/p/nova-ptg-stein Cheers,

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

On Tue, 25 Sep 2018 12:08:03 -0500, Matt Riedemann wrote: On 9/25/2018 8:36 AM, John Garbutt wrote: Another thing is about existing flavors configured for these capabilities-scoped specs. Are you saying during the deprecation we'd continue to use those even if the filter is disabl

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

On Thu, 27 Sep 2018 17:23:26 -0500, 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 allow passthrough of instance configuration data from

[Openstack-operators] [nova][xenapi] can we deprecate the xenapi-specific 'nova-console' service?

Greetings Devs and Ops, Today I noticed that our code does not handle the 'nova-console' service properly in a multi-cell deployment and given that no one has complained or reported bugs about it, we're wondering if anyone still uses the nova-console service. The documentation [1] says that th

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

On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote: On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits endpoint, is highly coupled with RAX's turnstile middleware and I can

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

On Wed, 24 Oct 2018 12:54:00 -0700, Melanie Witt wrote: On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote: On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits end

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

On Thu, 25 Oct 2018 14:12:51 +0900, ボーアディネシュ[bhor Dinesh] wrote: We were having a similar use case like *Preemptible Instances* called as *Rich-VM’s* which are high in resources and are deployed each per hypervisor. We have a custom code in production which tracks the quota for such instance