[openstack-dev] [Nova][Cinder] Operations: adding new nodes in "disabled" state, allowed for test tenant only
Ivan Kolodyazhny
e0ne at e0ne.info
Wed Dec 3 14:02:24 UTC 2014
Hi Mike,
We've got the similar option in Cinder too:
https://github.com/openstack/cinder/blob/master/cinder/db/api.py#L58
Regards,
Ivan Kolodyazhny
On Wed, Dec 3, 2014 at 3:31 PM, Mike Scherbakov <mscherbakov at mirantis.com>
wrote:
> 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
> 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/20141203/a5dd0e11/attachment.html>
More information about the OpenStack-dev
mailing list