<div dir="ltr"><a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Installation_and_Configuration_Guide/Safely_Removing_Compute_Resources.html">https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Installation_and_Configuration_Guide/Safely_Removing_Compute_Resources.html</a><br><div><br></div><div><pre class="" style="overflow:auto;font-family:"dejavu sans mono","liberation mono","bitstream vera mono","dejavu mono",monospace;font-size:0.9em;padding:15px;margin-top:1em;margin-bottom:1.8em;line-height:1.42857;word-wrap:break-word;border:1px solid rgb(26,26,26);border-radius:0px;white-space:pre-wrap;color:rgb(240,240,240)!important;background:rgb(51,51,51)"><strong class="" style="">nova service-disable <em class="" style="">HOST</em> nova-compute</strong></pre></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><b style="font-size:12.8000001907349px;color:rgb(136,136,136)"><font size="2">Rahul Sharma</font></b><br style="font-size:12.8000001907349px;color:rgb(136,136,136)"><font size="1" style="color:rgb(136,136,136)"><i>MS in Computer Science, 2016</i><br>College of Computer and Information Science, Northeastern University<br>Mobile:  801-706-7860<br>Email: <a href="mailto:rahulsharmaait@gmail.com" target="_blank">rahulsharmaait@gmail.com</a><br>Linkedin: <a href="http://www.linkedin.com/in/rahulsharmaait" target="_blank">www.linkedin.com/in/rahulsharmaait</a></font><br></div></div></div>
<br><div class="gmail_quote">On Tue, Aug 2, 2016 at 5:01 PM, Ken D'Ambrosio <span dir="ltr"><<a href="mailto:ken@jots.org" target="_blank">ken@jots.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
Thanks!<br>
<br>
-Ken<br>
<br>
_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to     : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
</blockquote></div><br></div>