RE: rVPC

-Original Message- From: Wei ZHOU [mailto:ustcweiz...@gmail.com] Sent: 28 November 2016 06:05 To: dev@cloudstack.apache.org Subject: Re: rVPC Hi Paul, CloudStack is designed like it. Not only RVR on VPC, but also RVR for isolated network, the MAC on public interface are the same on MASTER

Re: rVPC

> > We've found that the rVPC seems to use the same MAC address on the public > interface of both the Master and Backup rVPC nodes - was this by design? > > Kind regards, > > Paul Angus > > > paul.an...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > >

rVPC

Hey Wilder, I hope that you are well. We've found that the rVPC seems to use the same MAC address on the public interface of both the Master and Backup rVPC nodes - was this by design? Kind regards, Paul Angus paul.an...@shapeblue.com  www.shapeblue.com 53 Chandos Place, Covent Garden

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user DaanHoogland commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-184246895 blwah --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-184191105 @DaanHoogland A private gw uses a single ip address so there's your issue :-) --- If your project is set up for it, you can reply to this email and have your

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user DaanHoogland commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-184181722 @wilderrodrigues had a quick look. Why can't the gateway interface be up on the backup? Ip conflict? cause otherwise it seems no issue to me. Do the gateways

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-183966121 During the tests we found a couple of issues: 1. Default route was being set to private gateway interface after the master router went through a

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

GitHub user wilderrodrigues opened a pull request: https://github.com/apache/cloudstack/pull/1413 Fix unique mac address per rVPC router This PR fixes an issue we faced yesterday in production with Redundant VPCs and Private Gateways. In that case, we ended up with 2

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-183682371 I have done manual tests, but please do not merge it before I push the existing integrations tests that I'm improving now to cover those findings.

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-183715170 Manual Tests: * Master Router ``` root@r-23-VM:~# ip addr | grep eth3 | grep state | awk '{print $9;}' UP root@r-23-VM:~# ip addr |

[GitHub] cloudstack pull request: Fix unique mac address per rVPC router

Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/1413#issuecomment-183729063 LGTM Master router: 

[GitHub] cloudstack pull request: CLOUDSTACK-8935 - Cannot remove rVPC netw...

Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/967#issuecomment-150497392 I'm running the new test now. Once done, I will push it and you can proceed with testing the PR. Cheers, Wilder --- If your project is set up

[Master] Testing latest with rVPC code

Hi all, I just went through a test marathon to make sure things are working. Of course my tests do not cover everything, but it helps to give some confidence. From now we expect to get more contributors involved and to increase test coverage and make sure everything is working just fine.