<html><head></head><body><div class="">Hi Marica:<br> Can you give me your modified RA to me?And is that with your RA you configure the pacemaker just like the guide?I mean I notice that when the former network node down,the l3-agent of the back node must bind the router which belong to the former node.</div><div> </div><hr style="WIDTH: 210px; HEIGHT: 1px" color="#b5c4df" size="1" align="left"><div><span><div style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt">walterxj</div></span></div><blockquote style="margin-Top: 0px; margin-Bottom: 0px; margin-Left: 0.5em"><div> </div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><div style="PADDING-RIGHT: 8px; PADDING-LEFT: 8px; FONT-SIZE: 12px;FONT-FAMILY:tahoma;COLOR:#000000; BACKGROUND: #efefef; PADDING-BOTTOM: 8px; PADDING-TOP: 8px"><div><b>From:</b> <a href="mailto:marica.antonacci@gmail.com">Marica Antonacci</a></div><div><b>Date:</b> 2014-05-14 18:55</div><div><b>To:</b> <a href="mailto:walterxj@gmail.com">walterxj</a></div><div><b>CC:</b> <a href="mailto:openstack@lists.openstack.org">openstack</a></div><div><b>Subject:</b> Re: [Openstack] pacemaker would be wrong when both node have same hostname</div></div></div><div><div class=""><style type="text/css">div.FoxDIV_20140514185632316 { font-size: 10.5pt }
</style><div class="FoxDIV_20140514185632316"><div foxmail_class="mail_content_body" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi all,<div><br></div><div>we are currently using pacemaker to manage 2 network nodes (node1, node2) and we have modified the neutron L3 agent RA in order to dynamically change the hostname of the active network node: start() function sets the hostname “network-controller" to be used by the scheduler; the stop() function restores the old hostname (“node1” or “node2”). It seems to work, yet it’s a rude patch :) A more general solution that exploits neutron functionalities would be very appreciated!</div><div><br></div><div>Best,</div><div>Marica </div><div><br><div><div>Il giorno 14/mag/2014, alle ore 12:34, walterxj <<a href="mailto:walterxj@gmail.com">walterxj@gmail.com</a>> ha scritto:</div><br class="Apple-interchange-newline">
<div class=""><blockquote type="cite"><div style="line-height: 1.5; font-size: 10.5pt; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div><span></span>hi:</div><div> the high-availability-guide (<a id="yui_3_10_3_1_1400063442661_1817" rel="nofollow" href="http://docs.openstack.org/high-availability-guide/content/ch-network.html" style="font-size: 10.5pt; line-height: 1.5; background-color: window;">http://<wbr>docs.openstack.<wbr>org/high-<wbr>availability-<wbr>guide/content/<wbr>ch-network.<wbr>html</a>) says that Both nodes should have the same hostname since the Networking scheduler will be aware of one node, for example a virtual router attached to a single L3 node.</div><div><br></div><div> <span style="font-size: 10.5pt; line-height: 1.5; background-color: window;">But when I test it on two servers with same hostname,after installing corosync and pacemaker service on them(with no resource configured),the crm_mon output goes into endless loop.And in the log of corosync,there are so many messages like:May 09 22:25:40 [2149] TEST crmd: warning: crm_get_peer: Node 'TEST' and 'TEST' share the same cluster nodeid: 1678901258.After this I set diffrent nodeid in /etc/corosync/</span><wbr style="font-size: 10.5pt; line-height: 1.5; background-color: window;"><span style="font-size: 10.5pt; line-height: 1.5; background-color: window;">corosync.</span><wbr style="font-size: 10.5pt; line-height: 1.5; background-color: window;"><span style="font-size: 10.5pt; line-height: 1.5; background-color: window;">conf of each test node,but it didn't help.</span></div> So,I set diffrent hostname for each server,and then configure pacemaker just like the manual except the hostname,the neutron-dhcp-agent and neutron-<wbr>metadata-<wbr>agent works well,but neutron-l3-agent not(VM instance can't not access the external net,further more the gateway of the VM instance can't be accessed either).<br> After two days checking,finally I found that we can use "netron l3-agent-<wbr>router-<wbr>remove network1_l3_agentid external-routeid" and "netron l3-agent-router-add network2_l3_agentid external-routeid" to let the backup l3-agent to work when the former network node is down.(assume the two node's names are network1 and network2)<wbr>,alternatively,<wbr>we can update the mysql table routerl3agentbi<wbr>ndings in neutron base directly.If it make sense,I think we can change the scrip neutron-agent-l3 , in it's neutron_<wbr>l3_agent_<wbr>start() function,only need few lines to make it work well.<div><br></div><hr size="1" align="left" style="width: 210px; height: 1px;"><div><span>Walter Xu</span></div>_______________________________________________<br>Mailing list:<span class="Apple-converted-space"> </span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>Post to :<span class="Apple-converted-space"> </span><a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>Unsubscribe :<span class="Apple-converted-space"> </span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a></div></blockquote></div>
</div><br></div></div></div></div></div></blockquote></body></html>