Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Eugene,

yes thanks for your response. I saw this review before and i take a look
into this since some weeks for any changes ;).
Thats not a problem, i know many features are on your todo list, i know
this kind of problems :) but the question is more, is there any solution
for "now".

So anyone must be solved this problem, this spof, otherwise you can't
use the lbaas in a prod system. That, let's say workaround, are
interesting me.


Cheers and thanks :)
Heiko
On 01.04.2014 11:45, Eugene Nikanorov wrote:
> Hi Heiko,
>
> That kind of failover mechanism was on our roadmap:
> https://review.openstack.org/#/c/59743/
> However right now the work is deferred as we're discussing general design
> of HA feature.
> I can't guarantee that will be something included in Juno, but there's
> strong demand for this feature so it has high priority on our list.
>
> Thanks,
> Eugene.
>
>
> On Tue, Apr 1, 2014 at 1:21 PM, Édouard Thuleau <thuleau at gmail.com> wrote:
>
>> Just point you a blueprint [1] develop during the I release (but
deferring
>> to Juno) to bring L3 HA.
>> It use VRRP mechanism with keepalived that you could reuse for LBaaS.
>> It also uses conntrackd to synchronize connections between routers
(master
>> and slave). I don't know how to configure LB synchronization.
>>
>> [1] https://blueprints.launchpad.net/neutron/+spec/l3-high-availability
>>
>> Édouard.
>>
>>
>> On Tue, Apr 1, 2014 at 10:52 AM, Heiko Krämer
<hkraemer at anynines.com>wrote:
>>
>>>
> Hi guys,
>
> i'm looking since days for a solution to solve the SPOF (single point of
> failure) of the lbaas. A easy solution with a config option is not
> available yet.
>
> The next option is to install/configure some not OpenStack related tools
> like pacemaker. I realise my L3-Agent faiover with an self writen RA for
> pacemaker to switch routers on broken l3 agent to the running on with
> the neutron API.
> The same can be workin with LbaaS but there's a problem again:
>
>  - No API function to switch a pool from agent A to agent b
>  - configurations of HAProxy replicate => this can be solvd with drbd or
> some shared network storage like NFS
>  - Devices are not the same => L3 switch router from agent A (broken) to
> agent B the devices names are not the same
>  -
>
> Is there any solution to solve this SPOF ? I mean a LB should not only
> scale/balancing your cluster/application the second task is the failover
> of broken members.
>
>
>
>
> Thx and cheers
> Heiko
>
>>>
>>>
>>> _______________________________________________
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to     : openstack at lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>

- -- 
anynines.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTOpLaAAoJELxFogM4ixOFDrMIAMMOzVFrAOl5KvaESi9oHBHv
VCJ9QPsEDr09qLnUv+8KZFERzvLxAgyQTrl1WNGvn9atTi9Aa50Z31mdwujxlUdf
oCHTZfXfmyaADNlkZNOPggD/A+M6/KvB0wcHEjB7E5g9l0k/yKdAfjEJCFGOug03
rnj8nGB+WwcBUmBHwAWOItlDG+eFPWlb9jKflgUo/GEzcaJI5FFJaFoMC6yiUMsK
nPc7l/5KfAHRwQ2RUK2ZE1lwRcpyLm5kUaU18LuDeinaG/qJoJAA5BeoTwcClrZ4
meW8YehfqZqofJiWXTGBIFKnaob5RQch0pbAbbnQE6JiceUSuEW/Isr3hJFezKI=
=kcpO
-----END PGP SIGNATURE-----