<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>If you are interested in manually mucking around with local virsh
domain states, and you don't want nova to interfere, you can just
stop the local nova-compute service and it won't be doing any
syncing. Once you get those instances back into their desired
state, you can restart nova-compute and it won't be any wiser.<br>
</p>
<p>You can obviously shoot yourself in the foot using this method,
but I can understand in some cases that large hammers and manual
virsh commands are necessary.</p>
Cheers!<br>
<br>
<div class="moz-cite-prefix">On 2016-11-16 17:32, Mohammed Naser
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1AD1A2EC-E910-45EF-B0FD-F0D9DD87BE4F@vexxhost.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div>Typically, you should not be managing your VMs by virsh.
After a power outage, I would recommend sending a start API call
to instances that are housed on that specific hypervisor<br>
<br>
Sent from my iPhone</div>
<div><br>
On Nov 16, 2016, at 4:26 PM, Gustavo Randich <<a
href="mailto:gustavo.randich@gmail.com" moz-do-not-send="true">gustavo.randich@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>When a VM is shutdown without using nova API (kvm
process down, libvirt failed to start instance on host
boot, etc.), Openstack "freezes" the shutdown power state
in the DB, and then re-applies it if the VM is not started
via API, e.g.:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0
40px;border:none;padding:0px">
<div># virsh shutdown <domain></div>
<div><br>
</div>
<div>[ sync power states -> stop instance via API ],
because hypervisor rules ("power_state is always updated
from hypervisor to db")</div>
<div><br>
</div>
<div># virsh startup <domain></div>
<div><br>
</div>
<div>[ sync power states -> stop instance via API ],
because database rules</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>I understand this behaviour is "by design", but I'm
confused about the asymmetry: if VM is shutdown without
using nova API, should I not be able to start it up again
without nova API?</div>
<div><br>
</div>
<div>This is a common scenario in power outages or failures
external to Openstack, when VMs fail to start and we need
to start them up again using virsh.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>OpenStack-operators mailing list</span><br>
<span><a href="mailto:OpenStack-operators@lists.openstack.org"
moz-do-not-send="true">OpenStack-operators@lists.openstack.org</a></span><br>
<span><a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators"
moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-operators mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a>
</pre>
</blockquote>
<br>
</body>
</html>