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