GitHub user wilderrodrigues opened a pull request:
https://github.com/apache/cloudstack/pull/167
Make the routers iptables config persistent through reboot/crash
- After configuration save the ipdated in files
* /etc/iptables/router_rules.v4 and /etc/iptables/router_rules.v6
* Reload the configuration on reboot via the /etc/rc.local using
iptables-restore
- All the information about the router VMs is now persisted due to the work
on the rVPC/Persistent SystemVM done in the few months ago. The missing bit was
the iptables configuration, which was not surviving a crash or reboot not done
via the management server.
- Manual tests
* Create single VPC, 3 Tiers, 3 VMs, 3 pub IPs
* Connect to router and reboot it
* Wait for the router to come back and check IPtables/connect to VMs
* Create redundant VPC, 3 Tiers, 3 VMs, 3 pub IPs
* Connect to router and reboot it
* Wait for the router to come back and check IPtables/connect to VMs
* Create isolated network, 1 VM, 1 pub IP
* Connect to router and reboot it
* Wait for the router to come back and check IPtables/connect to VM
Tests executed against XenServer 6.2 compliant host
This fix CLOUDSTACK-4605
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/schubergphilis/cloudstack
fix/persistent_iptables-REBASE-II
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/167.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #167
----
commit 2fad87d3f3fec380ba5d595ee95f5caa88b37ee8
Author: wilderrodrigues <wrodrig...@schubergphilis.com>
Date: 2015-04-14T13:03:35Z
Make the routers persistent
- After configuration save the ipdated in files
* /etc/iptables/router_rules.v4 and /etc/iptables/router_rules.v6
* Reload the configuration on reboot via the /etc/rc.local using
iptables-restore
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
