<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>TripleO HA Controller been installed via <span>instack-virt-setup </span> has PCS CLI like :-</p>
<p></p>
<pre>pcs resource cleanup neutron-server-clone
pcs resource cleanup openstack-nova-api-clone
pcs resource cleanup openstack-nova-consoleauth-clone
pcs resource cleanup openstack-heat-engine-clone
pcs resource cleanup openstack-cinder-api-clone
pcs resource cleanup openstack-glance-registry-clone
pcs resource cleanup httpd-clone</pre>
been working as expected on bare metal
<p></p>
<p><br>
</p>
<p>Same cluster been setup via QuickStart (Virtual ENV) after bouncing one of controllers
<br>
</p>
<p>included in cluster ignores PCS CLI at least via my experience ( which is obviously limited</p>
<p>either format of particular commands is wrong for QuickStart )</p>
<p>I believe that dropping (complete replacing ) instack-virt-setup is not a good idea in general. Personally, I believe that like in case with packstack it is always good</p>
<p>to have VENV configuration been tested before going to bare metal deployment. <br>
</p>
<p>My major concern is maintenance and disaster recovery tests , rather then deployment itself . What good is for me TripleO Quickstart running on bare metal if I cannot replace</p>
<p>crashed VM Controller just been limited to Services HA ( all 3 Cluster VMs running on single</p>
<p>bare metal node )<br>
</p>
<p><br>
</p>
<p>Thanks <br>
</p>
<p>Boris.<br>
</p>
<br>
<br>
<br>
<br>
<div style="color: rgb(49, 55, 57);">
<div class="PlainText">
<hr tabindex="-1" style="display:inline-block; width:98%">
<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;"></span></font></div>
</div>
</body>
</html>