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

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

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

eds 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-operators@lists.openstack.

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

Re: [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On 24 May 2016 at 10:16, Matthew Booth wrote: > During its periodic task, ImageCacheManager does a checksum of every image > in the cache. It verifies this checksum against a previously stored value, > or creates that value if it doesn't already exist.[1] Based on this >

Re: [Openstack-operators] [nova][neutron] What are your cells networking use cases?

On 25 February 2016 at 10:01, Tim Bell wrote: > > CERN info added.. Feel free to come back for more information if needed. > > Tim > On 24/02/16 22:47, "Edgar Magana" wrote: > >>It will be awesome if we can add this doc into the networking guide :-)

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

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 and deleted_at), which at the YVR

Re: [Openstack-operators] [nova] Backlog Specs: a way to send requirements to the developer community

as backlog specs reviews would be a great way to get feedback from the developer community. On Thu, May 14, 2015 at 8:47 PM, John Garbutt j...@johngarbutt.com You can read more about Nova's backlog specs here: http://specs.openstack.org/openstack/nova-specs/specs/backlog/ Let me give more detail

Re: [Openstack-operators] [nova] Are we happy with libvirt-python = 1.2.0 ?

On 15 May 2015 at 13:28, Daniel P. Berrange berra...@redhat.com wrote: On Fri, May 15, 2015 at 11:51:22AM +0100, Daniel P. Berrange wrote: On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote: There are some workarounds in the code [3] I'd like to see removed by bumping the minimum

Re: [Openstack-operators] [openstack-dev] [nova] Can we bump MIN_LIBVIRT_VERSION to 1.2.2 in Liberty?

On 15 May 2015 at 12:28, Daniel P. Berrange berra...@redhat.com wrote: One other thing I should have mentioned is that we don't actually have one single minimum libvirt version. We actually have a couple of different minimum versions based on either the architecture or the hypervisor. For

Re: [Openstack-operators] [nova] Can we bump MIN_LIBVIRT_VERSION to 1.2.2 in Liberty?

On 15 May 2015 at 11:51, Daniel P. Berrange berra...@redhat.com wrote: On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote: The minimum required version of libvirt in the driver is 0.9.11 still [1]. We've been gating against 1.2.2 in Ubuntu Trusty 14.04 since Juno. The libvirt

Re: [Openstack-operators] [nova] Can we bump MIN_LIBVIRT_VERSION to 1.2.2 in Liberty?

On 15 May 2015 at 17:41, Daniel P. Berrange berra...@redhat.com wrote: On Fri, May 15, 2015 at 05:27:35PM +0100, John Garbutt wrote: On 15 May 2015 at 11:51, Daniel P. Berrange berra...@redhat.com wrote: On Thu, May 14, 2015 at 02:23:25PM -0500, Matt Riedemann wrote: The minimum required

[Openstack-operators] [nova] Backlog Specs: a way to send requirements to the developer community

Hi, I was talking with Matt (VW) about how best some large deployment working sessions could send their requirements to Nova. As an operator, if you have a problem that needs fixing or use case that needs addressing, a great way of raising that issue with the developer community is a Backlog