Re: [Openstack-operators] [openstack-dev] [Nova] Reconciling flavors and block device mappings

On Fri, Aug 26, 2016, at 11:01 AM, John Griffith wrote: > > > On Fri, Aug 26, 2016 at 7:37 AM, Andrew Laski > <and...@lascii.com> wrote: >> >> >> On Fri, Aug 26, 2016, at 03:44 >> AM,kostiantyn.volenbovs...@swisscom.com >> wrote: >> >

Re: [Openstack-operators] [Nova] Reconciling flavors and block device mappings

complex use cases. But it's an option. > > BR, > Konstantin > > > -Original Message- > > From: Andrew Laski [mailto:and...@lascii.com] > > Sent: Thursday, August 25, 2016 10:20 PM > > To: openstack-...@lists.openstack.org > > Cc: openstack-operators@l

Re: [Openstack-operators] [openstack-dev] [Nova] Reconciling flavors and block device mappings

On Fri, Aug 26, 2016, at 06:31 AM, Chris Dent wrote: > On Thu, 25 Aug 2016, Andrew Laski wrote: > > > Allow block device mappings, when present, to mostly determine instance > > packing. By that I mean that the scheduler only takes into account local > > disk that would

[Openstack-operators] [Nova] Reconciling flavors and block device mappings

Cross posting to gather some operator feedback. There have been a couple of contentious patches gathering attention recently about how to handle the case where a block device mapping supersedes flavor information. Before moving forward on either of those I think we should have a discussion about

Re: [Openstack-operators] Kilo ->-> Mitaka anyone have notes :)

On Sun, Jun 26, 2016, at 07:58 PM, Sam Morrison wrote: > I’ve done kilo -> mitaka with Keystone and all worked fine. Nothing > special I needed to do. > > If you’re wanting to do live upgrades with nova you can’t skip a version > from my understanding. Correct. Not without doing the work

Re: [Openstack-operators] [Glance] Default policy in policy.json

On Tue, Jun 21, 2016, at 12:27 PM, Adam Young wrote: > On 06/20/2016 10:09 PM, Michael Richardson wrote: > > On Fri, 17 Jun 2016 16:27:54 + > > > >> Also which would be preferred "role:admin" or "!"? Brian points out on [1] > >> that "!" would in effect, notify the admins that a policy is

Re: [Openstack-operators] [Nova] Significance of Error Vs Failed status

On Wed, May 11, 2016, at 11:10 AM, David Medberry wrote: > Kekane, > > Hi, > > This setting, how does it display in the "nova show $UUID" or in the > "openstack server show $UUID"? Ie, I don't want a VM showing ERROR > state if the VM itself is not in error. A failed migration doesn't >

Re: [Openstack-operators] [openstack-dev] [nova][cells] Should flavors in the API DB for cells v2 be soft-deletable?

On 01/08/16 at 12:43pm, John Garbutt wrote: On 7 January 2016 at 19:59, Matt Riedemann wrote: There is a cells v2 change up for review [1] which creates the flavor tables in the API DB. I noted that those table definitions include the soft-delete columns (deleted

Re: [Openstack-operators] Better error messages for API policy enforcements

On 12/02/15 at 03:24pm, Robert Starmer wrote: I can't think of a case where better error response and log messages are not useful/desired. I agree with this, but I don't think that custom error messages defined in policy.json are the way to go. The API response should be standard across

Re: [Openstack-operators] [openstack-dev] [nova] can we deprecate the xvp console?

On 11/05/15 at 10:39am, Matt Riedemann wrote: I noticed today that nova.console.xvp hits the database directly for console pools. We should convert this to objects so that the console service does not have direct access to the database (this is the only console I see that hits the database

Re: [Openstack-operators] Insert an entry into the instance action list

On 09/21/15 at 05:15pm, Tim Bell wrote: The instance action list is a very useful tool for our end users to see what has gone on with their VMs. Working with people in teams means that sometimes one person does not get to hear what another one has done and so raises helpdesk cases like "one of