<div dir="ltr"><font face="courier new, monospace">In that documentation it looks like each openstack service gets it own IP (keystone is being assigned 192.168.42.103 and glance is getting 192.168.42.104). </font><div><br>
</div><div style><font face="courier new, monospace">I might be missing something too because in the section titled "Configure the VIP" it create a primitive called "p_api-ip" (or p_ip_api if you read the text above it) and then in "Adding Keystone resource to Pacemaker" it creates a group with "p_ip_keystone"???</font></div>
<div style><font face="courier new, monospace"><br></font></div><div style><font face="courier new, monospace"><br></font></div><div style><font face="courier new, monospace">Stranger yet, "</font><span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif">Configuring OpenStack Services to use High Available Glance API" says: "</span><span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif;font-size:13.63636302947998px">For Nova, for example, if your Glance API service IP address is 192.168.42.104 as in the configuration explained here, you would use the following line in your </span><code class="" style="color:rgb(0,0,0);font-size:13.63636302947998px">nova.conf</code><span style="color:rgb(0,0,0);font-family:Verdana,Geneva,sans-serif;font-size:13.63636302947998px"> file : </span><span style="color:rgb(35,48,45);font-family:Monaco,'Courier New','DejaVu Sans Mono','Bitstream Vera Sans Mono',monospace;font-size:11.818181991577148px">glance_api_servers = 192.168.42.103" But, in the step before it set: "</span><span style="color:rgb(35,48,45);font-family:Monaco,'Courier New','DejaVu Sans Mono','Bitstream Vera Sans Mono',monospace;font-size:11.818181991577148px">registry_host = 192.168.42.104"?</span></div>
<div style><br></div><div style><font color="#23302d" face="Monaco, Courier New, DejaVu Sans Mono, Bitstream Vera Sans Mono, monospace"><span style="font-size:12px">So I am not sure which ip you would connect to here... </span></font></div>
<div style><font color="#23302d" face="Monaco, Courier New, DejaVu Sans Mono, Bitstream Vera Sans Mono, monospace"><span style="font-size:12px"><br></span></font></div><div style><font color="#23302d" face="Monaco, Courier New, DejaVu Sans Mono, Bitstream Vera Sans Mono, monospace"><span style="font-size:12px">Sam</span></font></div>
<div style><font face="courier new, monospace"><br></font></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 13, 2013 at 1:29 PM, JuanFra Rodriguez Cardoso <span dir="ltr"><<a href="mailto:juanfra.rodriguez.cardoso@gmail.com" target="_blank">juanfra.rodriguez.cardoso@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Samuel:<div><br></div><div>Yes, it's possible with pacemaker. Look at <a href="http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html" target="_blank">http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html</a>.</div>
<div><br></div><div>Regards,</div><div><div>JuanFra</div>
<br><br><div class="gmail_quote">2013/2/13 Samuel Winchenbach <span dir="ltr"><<a href="mailto:swinchen@gmail.com" target="_blank">swinchen@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
<div dir="ltr"><font face="courier new,monospace">Hi All,</font><div><font face="courier new,monospace"><br></font></div><div><font face="courier new,monospace">I currently have a HA OpenStack cluster running where the OpenStack services are kept alive with a combination of haproxy and keepalived.</font></div>
<div><font face="courier new,monospace"><br></font></div><div><font face="courier new, monospace">Is it possible to configure pacemaker so that all the OpenStack services are served by the same IP? With keepalived I have a virtual ip that can move from server to server and haproxy sends the request to a machine that has a "live" service. This allows one (public) ip to handle all incoming requests. I believe it is the combination of VRRP/IPVS that allows this.</font></div>
<div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">Is it possible to do something similar with pacemaker? I really don't want to have an IP for each service, and I don't want to make it a requirement that all OpenStack services must be running on the same server.</font></div>
<div><font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">Thanks... I hope this question is clear, I feel like I sort of butchered the wording a bit.</font></div><div>
<font face="courier new, monospace"><br></font></div><div><font face="courier new, monospace">Sam</font></div></div>
<br></div></div>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>