On 12/18/2015 06:00 AM, Akshay Kumar Sanghai wrote:
> Hi,
> I have a network ,net1 with 2 VMs connected to it. One router R1 is
> connected to the n/w which connects to ext-net. I have another router
> R2 that connects to a diff network net2 in the tenant. Can i create
> matching rules for the netw
On 12/18/2015 09:16 AM, Serguei Bezverkhi (sbezverk) wrote:
> Hello team,
>
>
>
> I would appreciate if you could share approach you use for OpenStack
> node redundancy from network failure perspective. Example in case of a
> failure of an upstream switch and if a node does not have redundant
>
Hi Serguei,
We have pairs of Top of Rack switches in MLAG configurations. On the
Server-side, we are using OVS LACP bonds in balance-tcp mode. We
haven't had any kernel issues with bonding on Ubuntu kernels 3.13, 3.19,
and 4.2.
I'm not sure what you mean by "Openstack will remove the isolated n
Thanks Elena for update.
When i have tested also it is not working.
Thanks for the confirmation.
On Mon, Dec 21, 2015 at 6:14 PM, Elena Ezhova wrote:
> Hi!
>
> For all I know VPNaaS currently doesn't support DVR + floating IPs, there
> is a bug for that [1]. Another issue is that VPNaaS + DVR
Hi!
For all I know VPNaaS currently doesn't support DVR + floating IPs, there
is a bug for that [1]. Another issue is that VPNaaS + DVR doesn't work
correctly in case there are several controllers [2].
Thanks,
Elena
[1] https://bugs.launchpad.net/neutron/+bug/1476469
[2] https://bugs.launchpad.n
Hi Team,
I have tested vpnaas with centralized router. It seems working perfectly.
It is also working with neutron DVR. But if we assign any floating IP to
instance, it will stop working.
Is it expected behaviour?
Can you please confirm it?
--
--
Regards,
Geo Varghese
On 18/12/2015 17:55, Bajin, Joseph wrote:
> That was me..
>
> We are using McRouter which then speaks to memcached to talk to all the
> memcache servers that you have up and running. It keeps track of what is
> up and down so it knows where to send traffic. You can get pretty
> complicated with
