GitHub user wilderrodrigues opened a pull request:
https://github.com/apache/cloudstack/pull/150
Fixing the communication with VM via Public IP
- Pub IP port forwarding and static NAT fixed for single VPCs
- Pub IP port forwarding fixed for redundant VPCs
[wip] fix static NAT for redundant VPCs
XenServer 6.2 host running under our VMWare zone
Management Server running on my MacBook
MySQL running on my MacBook
Manual tests executed agains single/redundant VPC
1. Create Single VPC
2. Add ACL - port 22
3. Add 2 tiers
4. Add 1 VM to each tier
5. SSH into the VMs
6. Acquire a new pub IP
7. Add PF to the new pub IP associated with tier #1
8. SSH into the VM through the pub IP
9. Acquire a new pub IP
10. Create a static NAT connection associated with tier #2
11. SSH into the VM using the new pub IP
1. Create Redundant VPC
2. Add ACL - port 22
3. Add 2 tiers
4. Add 2 VMs to each tier
5. SSH into the VMs
6. Acquire a new pub IP
7. Add PF to the new pub IP associated with tier #1
8. SSH into the VM through the pub IP
9. Acquire a new pub IP
10. Create a static NAT connection associated with tier #2
11. SSH into the VM using the new pub IP
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/schubergphilis/cloudstack
fix_public_ip_iptables
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/150.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 #150
----
commit 556ca05a8b8acfc00cbc27dc8ce6e9cdc9d676ac
Author: wilderrodrigues <[email protected]>
Date: 2015-04-08T13:46:32Z
Fixing the communication with VM via Public IP
- Pub IP port forwarding and static NAT fixed for single VPCs
- Pub IP port forwarding fixed for redundant VPCs
[wip] fix static NAT for redundant VPCs
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
