[openstack-dev] [Nova][Cinder] Operations: adding new nodes in "disabled" state, allowed for test tenant only

Joe Gordon joe.gordon0 at gmail.com
Thu Dec 4 13:26:59 UTC 2014

On Wed, Dec 3, 2014 at 3:31 PM, Mike Scherbakov <mscherbakov at mirantis.com>

> Hi all,
> enable_new_services in nova.conf seems to allow add new compute nodes in
> disabled state:
> https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L507-L508,
> so it would allow to check everything first, before allowing production
> workloads host a VM on it. I've filed a bug to Fuel to use this by default
> when we scale up the env (add more computes) [1].
> A few questions:
>    1. can we somehow enable compute service for test tenant first? So
>    cloud administrator would be able to run test VMs on the node, and after
>    ensuring that everything is fine - to enable service for all tenants
Although there may be more then one way to set this up in nova, this can
definitely be done via nova host aggregates. Put new compute services into
an aggregate that only specific tenants can access (controlled via
 scheduler filter).

>    1.
>    2. What about Cinder? Is there a similar option / ability?
>    3. What about other OpenStack projects?
> What is your opinion, how we should approach the problem (if there is a
> problem)?
> [1] https://bugs.launchpad.net/fuel/+bug/1398817
> --
> Mike Scherbakov
> #mihgen
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141204/6647d6b9/attachment.html>

More information about the OpenStack-dev mailing list