Adding back the openstack-operators list that Matt added.
On 06/04/2018 05:13 PM, Sean McGinnis wrote:
On 06/04/2018 04:17 PM, Doug Hellmann wrote:
Excerpts from Matt Riedemann's message of 2018-06-04 15:38:48 -0500:
On 6/4/2018 1:07 PM, Sean McGinnis wrote:
Python 3 First
==
On
+openstack-operators since we need to have more operator feedback in our
community-wide goals decisions.
+Melvin as my elected user committee person for the same reasons as
adding operators into the discussion.
On 6/4/2018 3:38 PM, Matt Riedemann wrote:
On 6/4/2018 1:07 PM, Sean McGinnis wro
+openstack-operators to see if others have the same use case
On 5/31/2018 5:14 PM, Moore, Curt wrote:
We recently upgraded from Liberty to Pike and looking ahead to the code
in Queens, noticed the image download deprecation notice with
instructions to post here if this interface was in use. As
On 06/04/2018 05:43 AM, Tobias Urdin wrote:
Hello,
I have received a question about a more specialized use case where we need to
isolate several hypervisors to a specific project. My first thinking was
using nova flavors for only that project and add extra specs properties to
use a specific host
Hi,
Apologies if this has been asked before but Google didn't turn up anything
useful.
We are currently using Fuel to deploy OpenStack but given that it seems to be
unmaintained have choose to switch to OpenStack-Ansible. The current setup
routes all external traffic i.e. for floating IPs th
Saw now in the docs that multiple aggregate_instance_extra_specs keys
should be a comma-separated list.
But other than that, would the below do what I'm looking for?
Has a very high maintenance level when having a lot of hypervisors and
steadily adding new ones, but I can't see any other way to fu
Hello,
Thanks for the reply Matt.
The hard thing here is that I have to ensure it the other way around as
well i.e other instances cannot be allowed landing on those "reserved"
hypervisors.
I assume I could do something like in [1] and also set key-value
metadata on all flavors to select a host ag
Hi!
We had a double session on extended maintenance at the Forum in
Vancouver, here is a late summary of it. Feel free to add to it if you
remember extra things.
The first part of the session was to present the Extended Maintenance
process as implemented after the discussion at the PTG in Du
On 6/4/2018 6:43 AM, Tobias Urdin wrote:
I have received a question about a more specialized use case where we
need to isolate several hypervisors
to a specific project. My first thinking was using nova flavors for only
that project and add extra specs properties to use a specific host
aggregate
Hello,
I have received a question about a more specialized use case where we
need to isolate several hypervisors
to a specific project. My first thinking was using nova flavors for only
that project and add extra specs properties to use a specific host
aggregate but this
means I need to assign v
10 matches
Mail list logo
