Skip to content

CLOUDSTACK-8881: Fixed Static and PF configuration issue - #882

Merged
asfgit merged 1 commit into
apache:masterfrom
jayapalu:CLOUDSTACK-8881
Sep 27, 2015
Merged

CLOUDSTACK-8881: Fixed Static and PF configuration issue#882
asfgit merged 1 commit into
apache:masterfrom
jayapalu:CLOUDSTACK-8881

Conversation

@jayapalu

Copy link
Copy Markdown
Contributor
  1. For static nat filter rules are not configured in VR.
  2. Corrected vm ip in PF rule.

@asfbot

Copy link
Copy Markdown

cloudstack-pull-rats #718 SUCCESS
This pull request looks good

@wilderrodrigues

Copy link
Copy Markdown
Contributor

@jayapalu@karuturi

We, @remibergsma, Funs and I will test the 3 PRs which are VR related now.

@asfbot

Copy link
Copy Markdown

cloudstack-pull-analysis #667 SUCCESS
This pull request looks good

remibergsma added a commit to remibergsma/cloudstack that referenced this pull request Sep 24, 2015
CLOUDSTACK-8881: Fixed Static and PF configuration issue1. For static nat filter rules are not configured in VR.
2. Corrected vm ip in PF rule.
* pr/882:
CLOUDSTACK-8881: Fixed Static and PF configuration issue
Signed-off-by: Remi Bergsma <github@remi.nl>
@asfgit
asfgit merged commit 40138d2 into apache:masterSep 27, 2015
asfgit pushed a commit that referenced this pull request Sep 27, 2015
[BLOCKER] Combined PRs that fix VR issuesTonight I worked with @wilderrodrigues to figure out what is wrong with the virtual router. As we couldn't test single PRs any more (because of other issues with them causing tests to fail) we added all VR related PRs in a separate branch and started testing from there.
We combined the following PRs into this PR:
#836#851#867#870#881#882#842
After that, one issue remains: the VPC does not get a default gateway. Which is strange, because we already solved it in PR #738. When I look back, it was fixed again in PR #784. It could very well be that either one fixed one specific case, but also breaking the other. We need to investigate this, and make sure there will be a fix that works both for VPCs and VRs.
When we manually add the default gateway on the VPC, most tests pass and also spinning up two VPCs with one tier each, having a VM and them using s2s to VPN them together works fine. See for more details the report Wilder sent earlier.
Tomorrow we'll try to figure out how to fix the default gateway and merge this. Then we should have a base to work from again. Any PR that fixes another blocker, should at least then be rebased against the fixed master so we can run the tests against the PR branch. I'm not saying everything is fixed, I'm just saying that we can spin up a cloud that has working VMs.
When, in the mean time, someone has the time to checkout this branch and make the default route work for both VPC and VR that would be awesome. After that we should double check and verify the test results.
Pinging @karuturi to let her know the current status.
Regards,
Wilder / Remi
* pr/887:
Fixing the index out of bounds error in the check_if_link_up() function
small cleanups
Fixing the defaut route for VPC routers
Formatting the get_gateway() method in the CsDatabag.py file
Fixing the dhcpsrvr iptables file
Formatting the router_proxy.sh script
CLOUDSTACK-8881: Fixed Static and PF configuration issue
CLOUDSTACK-8905: Fixed hooking egress rules
CLOUDSTACK-8891: Fixed default iptables rules on VR for guest traffic
Configured dnsmasq to listen on all interfaces so that vpn client gets dns
CLOUDSTACK-8864: Not able to add TCP port forwarding rule in VPN for specific ports
CLOUDSTACK-8863: VM doesn't reconnect to internet post VR RESTART/STOP-START/RECREATE
CLOUDSTACK-8843: Fixed issue in default iptables rules on shared network VR
Signed-off-by: Remi Bergsma <github@remi.nl>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@jayapalu@asfbot@wilderrodrigues@asfgit