<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><br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> Raoul Scarazzini <rasca@redhat.com><br>
<b>Sent:</b> Monday, August 22, 2016 3:51 AM<br>
<b>To:</b> Wesley Hayutin; Boris Derzhavets; Attila Darazs<br>
<b>Cc:</b> David Moreau Simard; rdo-list<br>
<b>Subject:</b> Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi everybody,<br>
sorry for the late response but I was on PTO. I don't understand the<br>
meaning of the cleanup commands, but maybe it's just because I'm not<br>
getting the whole picture.<br>
<br>
<span id="ms-rterangepaste-start"></span>
<div>><br>
I have to confirm that fault was mine PCS CLI is working on TripeO QuickStart<br>
but requires pcs cluster restart on particular node which went down<br>
via ` nova stop controller-X` and was brought up via `nova start controller-X`<br>
Details here :-<br>
<br>
http://bderzhavets.blogspot.ru/2016/08/emulation-rdo-triple0-quickstart-ha.html<br>
<br>
VENV been set up with instack-virt-setup doesn't require ( on bounced Controller node )<br>
<br>
# pcs cluster stop<br>
# pcs cluster start<br>
<br>
Before issuing start.sh<br>
<br>
#!/bash -x<br>
pcs resource cleanup rabbitmq-clone ;<br>
sleep 10<br>
pcs resource cleanup neutron-server-clone ;<br>
sleep 10<br>
pcs resource cleanup openstack-nova-api-clone ;<br>
sleep 10<br>
pcs resource cleanup openstack-nova-consoleauth-clone ;<br>
sleep 10<br>
pcs resource cleanup openstack-heat-engine-clone ;<br>
sleep 10<br>
pcs resource cleanup openstack-cinder-api-clone ;<br>
sleep 10<br>
pcs resource cleanup openstack-glance-registry-clone ;<br>
sleep 10<br>
pcs resource cleanup httpd-clone ;<br>
<br>
# . ./start.sh <br>
<br>
In worse case scenario I have to issue start.sh twice from different Controllers<br>
pcs resource cleanup openstack-nova-api-clone attempts to start corresponding<br>
service , which is down at the moment. In fact two cleanups above start all<br>
Nova Services && one neutron cleanup starts all neutron agents as well.<br>
I was also kept track of Galera DB via `clustercheck`<br>
<br>
Thanks.<br>
Boris<br>
><br>
</div>
<span id="ms-rterangepaste-end"></span><br>
<br>
I guess we're hitting a version problem here: if you deploy the actual<br>
master (i.e. with quickstart) you'll get the environment with the<br>
constraints limited to the core services because of [1] and [2] (so none<br>
of the mentioned services exists in the cluster configuration).<br>
<br>
Hope this helps,<br>
<br>
[1] <a id="LPlnk896235" href="https://review.openstack.org/#/c/314208/">https://review.openstack.org/#/c/314208/</a><br>
[2] <a href="https://review.openstack.org/#/c/342650/">https://review.openstack.org/#/c/342650/</a><br>
<br>
-- <br>
Raoul Scarazzini<br>
rasca@redhat.com<br>
<br>
On 08/08/2016 14:43, Wesley Hayutin wrote:<br>
> Attila, Raoul<br>
> Can you please investigate this issue.<br>
> <br>
> Thanks!<br>
> <br>
> On Sun, Aug 7, 2016 at 3:52 AM, Boris Derzhavets<br>
> <bderzhavets@hotmail.com <<a href="mailto:bderzhavets@hotmail.com">mailto:bderzhavets@hotmail.com</a>>> wrote:<br>
> <br>
> TripleO HA Controller been installed via instack-virt-setup has PCS<br>
> CLI like :-<br>
> <br>
> pcs resource cleanup neutron-server-clone<br>
> pcs resource cleanup openstack-nova-api-clone<br>
> pcs resource cleanup openstack-nova-consoleauth-clone<br>
> pcs resource cleanup openstack-heat-engine-clone<br>
> pcs resource cleanup openstack-cinder-api-clone<br>
> pcs resource cleanup openstack-glance-registry-clone<br>
> pcs resource cleanup httpd-clone<br>
> <br>
> been working as expected on bare metal<br>
> <br>
> <br>
> Same cluster been setup via QuickStart (Virtual ENV) after bouncing<br>
> one of controllers<br>
> <br>
> included in cluster ignores PCS CLI at least via my experience (<br>
> which is obviously limited<br>
> <br>
> either format of particular commands is wrong for QuickStart )<br>
> <br>
> I believe that dropping (complete replacing ) instack-virt-setup is<br>
> not a good idea in general. Personally, I believe that like in case<br>
> with packstack it is always good<br>
> <br>
> to have VENV configuration been tested before going to bare metal<br>
> deployment.<br>
> <br>
> My major concern is maintenance and disaster recovery tests , rather<br>
> then deployment itself . What good is for me TripleO Quickstart<br>
> running on bare metal if I cannot replace<br>
> <br>
> crashed VM Controller just been limited to Services HA ( all 3<br>
> Cluster VMs running on single<br>
> <br>
> bare metal node )<br>
> <br>
> <br>
> Thanks<br>
> <br>
> Boris.<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> ------------------------------------------------------------------------<br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> rdo-list mailing list<br>
> rdo-list@redhat.com <<a href="mailto:rdo-list@redhat.com">mailto:rdo-list@redhat.com</a>><br>
> <a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a>><br>
> <br>
> To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
> <<a href="mailto:rdo-list-unsubscribe@redhat.com">mailto:rdo-list-unsubscribe@redhat.com</a>><br>
> <br>
> <br>
</div>
</span></font></div>
</div>
</body>
</html>