Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#144269245] Set MTU for Garden containers back to 1500 and add test #887

Merged
merged 2 commits into from Apr 26, 2017

Conversation

@dcarley
Copy link
Contributor

@dcarley dcarley commented Apr 25, 2017

What

garden-runc 1.3.0, which was included by the CF upgrade in 46019be, changed
the MTU of Guardian containers to match the host's external network
interface instead of always being 1500:

For our cells on AWS this meant a change from 1500 to 9001:

This didn't work well with IPsec, which we use to secure web traffic between
the routers and cells. Requests which generated responses larger than approx
9000 bytes were too large after the IPsec headers were added and never made
it back to the router.

It might have been nice to set this to a value a bit smaller than 9000, to
allow for the IPsec overhead, but we can't guarantee the MTU value of the
host interface because it gets set by AWS.

Ideally PMTU should mean that we wouldn't have to do this. We think that the
ICMP unreachable messages might not be getting back to the container (or
host?) correctly. It might be that we can revert this commit in future after
some more investigation.

Includes an acceptance test that:

Check that requests don't hang when the HTTP response is large (up to
200kB). This should prevent regressions of the MTU problem described in the
preceding commit.

How to review

馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵
This must not be deployed before #884 but it should be safe if they are deployed at the same time
馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵 馃悵

  1. Code review
  2. Deploy
  3. Confirm that availability-tests pass meaning that containers were migrated correctly
  4. Confirm that custom-acceptance-tests pass meaning that larger response sizes work

Who can review

Not @saliceti or @dcarley

@paroxp paroxp self-assigned this Apr 25, 2017
paroxp
paroxp approved these changes Apr 26, 2017
dcarley and others added 2 commits Apr 26, 2017
garden-runc 1.3.0, which was included by the CF upgrade in 46019be, changed
the MTU of Guardian containers to match the host's external network
interface instead of always being 1500:

- cloudfoundry/guardian@af8d612
- cloudfoundry/garden-runc-release@a9b22fd

For our cells on AWS this meant a change from 1500 to 9001:

- http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/network_mtu.html#jumbo_frame_instances

This didn't work well with IPsec, which we use to secure web traffic between
the routers and cells. Requests which generated responses larger than approx
9000 bytes were too large after the IPsec headers were added and never made
it back to the router.

It might have been nice to set this to a value a *bit* smaller than 9000, to
allow for the IPsec overhead, but we can't guarantee the MTU value of the
host interface because it gets set by AWS.

Ideally PMTU should mean that we wouldn't have to do this. We think that the
ICMP unreachable messages might not be getting back to the container (or
host?) correctly. It might be that we can revert this commit in future after
some more investigation.
Check that requests don't hang when the HTTP response is large (up to
200kB). This should prevent regressions of the MTU problem described in the
preceding commit.
@paroxp paroxp merged commit b192f29 into master Apr 26, 2017
2 checks passed
Loading
paroxp added a commit that referenced this issue Apr 26, 2017
[#144269245] Set MTU for Garden containers back to 1500 and add test
@paroxp paroxp deleted the mtu_and_dora branch Apr 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants