cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wilderrodrigues <>
Subject [GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9015 - Redundant VPC V...
Date Mon, 16 Nov 2015 08:49:49 GMT
GitHub user wilderrodrigues opened a pull request:

    [4.6.1] CLOUDSTACK-9015 - Redundant VPC Virtual Router's state is BACKUP & BACKUP

    This PR closes #1064
    All the details can be found in the original PR, which won't be merged because it was
created agains master. Once this PR is closed, the original one will be also closed.

You can merge this pull request into a Git repository by running:

    $ git pull fix/rVPC-CLOUDSTACK-9015

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1070
commit cd05a252fb6c76ceff88f3dc83d3699be18556a7
Author: Wilder Rodrigues <>
Date:   2015-11-12T17:13:51Z

    CLOUDSTACK-9015 - Make sure the Backup router can talk to the Master router after a stop/start/reboot
       - Stop KeepaliveD/ConntrackD if the eth2 (guest) interface is not configured and UP
       - Only setup the redundancy after all the router configuration is done
       - Open the FW for the VRRP communitation
         - and
       - Set keepalived.conf.templ by default to use interface eth2 (guest)
         - It will be reconfigured anyway, but having eth2 there is more clear

commit 952d9a84d23b3070b1073ed8ea53275de1c556e1
Author: Wilder Rodrigues <>
Date:   2015-11-12T17:32:53Z

    CLOUDSTACK-9015 - Add test to cover the rVPC routers stop/start/reboot scenario
       - Stop/reboot master router should make the backup router become master
       - Start the stopped router should make be the backup router


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 feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message