openstack team mailing list archive

[Samuel Winchenbach <swinchen@xxxxxxxxx>]

T
he only real problem is that it would consume a lot of IP addresses when
exposing the public interfaces.   I _think_ I may have the solution in your
blog actually:
http://www.sebastien-han.fr/blog/2012/10/19/highly-available-lvs/
and
http://clusterlabs.org/wiki/Using_ldirectord

I am trying to weigh the pros and cons of this method vs keepalived/haproxy
and just biting the bullet and using one IP per service.



On Thu, Feb 14, 2013 at 4:17 AM, Sébastien Han <han.sebastien@xxxxxxxxx>wrote:

> What's the problem to have one IP on service pool basis?
>
> --
> Regards,
> Sébastien Han.
>
>
> On Wed, Feb 13, 2013 at 8:45 PM, Samuel Winchenbach <swinchen@xxxxxxxxx>wrote:
>
>> What if the VIP is created on a different host than keystone is started
>> on?   It seems like you either need to set net.ipv4.ip_nonlocal_bind = 1
>> or create a colocation in pacemaker (which would either require all
>> services to be on the same host, or have an ip-per-service).
>>
>>
>>
>>
>> On Wed, Feb 13, 2013 at 2:28 PM, Razique Mahroua <
>> razique.mahroua@xxxxxxxxx> wrote:
>>
>>> There we go
>>> https://review.openstack.org/#/c/21581/
>>>
>>> *Razique Mahroua** - **Nuage & Co*
>>> razique.mahroua@xxxxxxxxx
>>> Tel : +33 9 72 37 94 15
>>>
>>>
>>> Le 13 févr. 2013 à 20:15, Razique Mahroua <razique.mahroua@xxxxxxxxx> a
>>> écrit :
>>>
>>> I'm currently updating that part of the documentation - indeed it states
>>> that two IPs are used, but in fact, you end up with only one VIP for the
>>> API service.
>>> I'll send the patch tonight
>>>
>>> *Razique Mahroua** - **Nuage & Co*
>>> razique.mahroua@xxxxxxxxx
>>> Tel : +33 9 72 37 94 15
>>>
>>> <NUAGECO-LOGO-Fblan_petit.jpg>
>>>
>>> Le 13 févr. 2013 à 20:05, Samuel Winchenbach <swinchen@xxxxxxxxx> a
>>> écrit :
>>>
>>> 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).
>>>
>>> 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"???
>>>
>>>
>>> Stranger yet, "Configuring OpenStack Services to use High Available
>>> Glance API" says:  "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 nova.conf file : glance_api_servers
>>> = 192.168.42.103"  But, in the step before it set:  "registry_host =
>>> 192.168.42.104"?
>>>
>>> So I am not sure which ip you would connect to here...
>>>
>>> Sam
>>>
>>>
>>>
>>> On Wed, Feb 13, 2013 at 1:29 PM, JuanFra Rodriguez Cardoso <
>>> juanfra.rodriguez.cardoso@xxxxxxxxx> wrote:
>>>
>>>> Hi Samuel:
>>>>
>>>> Yes, it's possible with pacemaker. Look at
>>>> http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html.
>>>>
>>>> Regards,
>>>> JuanFra
>>>>
>>>>
>>>> 2013/2/13 Samuel Winchenbach <swinchen@xxxxxxxxx>
>>>>
>>>>>  Hi All,
>>>>>
>>>>> I currently have a HA OpenStack cluster running where the OpenStack
>>>>> services are kept alive with a combination of haproxy and keepalived.
>>>>>
>>>>> 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.
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>> Thanks... I hope this question is clear, I feel like I sort of
>>>>> butchered the wording a bit.
>>>>>
>>>>> Sam
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>