On 8/2/2016 5:34 PM, David Medberry wrote:
nova service-disable $SHORTNAME nova-compute --reason
NO_MORE_SCHEDULING_HERE
will prevent new VMs from going on but doesn't do anything with existing.
On Tue, Aug 2, 2016 at 3:01 PM, Ken D'Ambrosio <k...@jots.org
<mailto:k...@jots.org>> wrote:
Hi, all. Trying to figure out how to disable a compute node from
getting new VMs scheduled for it on my Liberty cloud. I did see the
"nova host-update --maintenance" command, but (as noted elsewhere)
it seems not to work for KVM-based VMs. Is there a way to
accomplish what I'm looking to do? Note that I'm not looking to
take the host down, just take it out of the pool of compute hosts
ready to accept new VMs.
Thanks!
-Ken
_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
<mailto:openstack@lists.openstack.org>
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Yup, also, docs.o.o!
http://docs.openstack.org/ops-guide/ops_maintenance_compute.html#planned-maintenance
--
Thanks,
Matt Riedemann
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
