<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)">Ken, thanks for yor reply.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)">Since in our setup, we use active/active mysql clone, so i think that order is the only way to ensure what i want.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)">So, simple question, making order "Advisory", and tiking into consideration that "maybe" keystone starts before mysql, making it fail because of database connecrion.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)">If i set on the keystone clone (and all the dependant clones) on-fail="restart" for start and monitor actions (of course setting the cib option <span style="color:rgb(51,51,51);font-family:consolas,"liberation mono",menlo,courier,monospace;font-size:12px;white-space:pre">start-failure-is-fatal=false </span>) to make sure that if it fails, it will restart till everything is ok.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)">would that make sense to "workaround" that ?</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small;color:rgb(68,68,68)">best.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 9, 2017 at 12:18 AM, Ken Gaillot <span dir="ltr"><<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 02/06/2017 05:25 PM, Alejandro Comisario wrote:<br>
> guys, really happy to post my first doubt.<br>
><br>
> i'm kinda having an "conceptual" issue that's bringing me, lots of issues<br>
> i need to ensure that order of starting resources are mandatory but<br>
> that is causing me a huge issue, that is if just one of the members of<br>
> a clone goes down and up (but not all members) all resources depending<br>
> on it are restarted (wich is bad), my workaround is to set order as<br>
> advisory, but that doesnt asure strict order startup.<br>
><br>
> eg. clone_b runs on servers_B, and depends on clone_a that runs on servers_A.<br>
><br>
> I'll put an example on how i have everything defined between this two clones.<br>
><br>
> ### clone_A running on servers A (location rule)<br>
> primitive p_mysql mysql-wss \<br>
> op monitor timeout=55 interval=60 enabled=true on-fail=restart \<br>
> op start timeout=475 interval=0 on-fail=restart \<br>
> op stop timeout=175 interval=0 \<br>
> params socket="/var/run/mysqld/<wbr>mysqld.sock"<br>
> pid="/var/run/mysqld/mysqld.<wbr>pid" test_passwd="XXX" test_user=root \<br>
> meta is-managed=true<br>
><br>
> clone p_mysql-clone p_mysql \<br>
> meta target-role=Started interleave=false globally-unique=false<br>
><br>
> location mysql_location p_mysql-clone resource-discovery=never \<br>
> rule -inf: galera ne 1<br>
><br>
> ### clone_B running on servers B (location rule)<br>
> primitive p_keystone apache \<br>
> params configfile="/etc/apache2/<wbr>apache2.conf" \<br>
> op monitor on-fail=restart interval=60s timeout=60s \<br>
> op start on-fail=restart interval=0 \<br>
> meta target-role=Started migration-threshold=2 failure-timeout=60s<br>
> resource-stickiness=300<br>
><br>
> clone p_keystone-clone p_keystone \<br>
> meta target-role=Started interleave=false globally-unique=false<br>
><br>
> location keystone_location p_keystone-clone resource-discovery=never \<br>
> rule -inf: keystone ne 1<br>
><br>
> order p_clone-mysql-before-p_<wbr>keystone INF: p_mysql-clone p_keystone-clone:start<br>
><br>
> Again just to make my point, if p_mysql-clone looses even one member<br>
> of the clone, ONLY when that member gets back, all members of<br>
> p_keystone-clone gets restarted, and thats NOT what i need, so if i<br>
> change the order from mandatory to advisory, i get what i want<br>
> regarding behaviour of what happens when instances of the clone comes<br>
> and goes, but i loos the strictness of the startup order, which is<br>
> critial for me.<br>
><br>
> How can i fix this problem ?<br>
> .. can i ?<br>
<br>
</div></div>I don't think pacemaker can model your desired situation currently.<br>
<br>
In OpenStack configs that I'm familiar with, the mysql server (usually<br>
galera) is a master-slave clone, and the constraint used is "promote<br>
mysql then start keystone". That way, if a slave goes away and comes<br>
back, it has no effect.<br>
<br>
______________________________<wbr>_________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><table border="0" cellpadding="0" cellspacing="0" style="width:295px;border:none;font-size:12px;color:rgb(51,51,51);margin-top:0px"><tbody><tr><td><font face="monospace, monospace"><strong><span style="font-size:13px;line-height:24px;color:white;padding:4px;background:rgb(103,189,197)">Alejandro Comisario</span></strong><br><strong><span style="font-size:13px;line-height:24px;color:white;padding:4px;background:black">CTO | NUBELIU</span></strong><br></font><span style="font-family:Helvetica,sans-serif;font-size:13px;display:block;margin:3px 0px 1px"><font face="monospace, monospace">E-mail: <a href="mailto:alejandro@nubeliu.com" target="_blank">alejandro@nubeliu.com</a></font></span><font face="monospace, monospace"><span style="font-size:13px">Cell: +54 9 11 3770 1857</span><br><span style="font-size:13px;color:rgb(103,189,197);line-height:5px">_</span><br><span style="font-size:13px;color:rgb(103,189,197)"><a href="http://www.nubeliu.com/" style="color:rgb(103,189,197);text-decoration:none" target="_blank">www.nubeliu.com</a></span><br><img src="http://i1260.photobucket.com/albums/ii571/scomisario/logo_zpsfc01fd9e.png" border="0" style="margin-top:4px"></font></td></tr></tbody></table><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>