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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws natgateways parsing #682

Merged
merged 4 commits into from
Nov 22, 2017
Merged

aws natgateways parsing #682

merged 4 commits into from
Nov 22, 2017

Conversation

ratulm
Copy link
Member

@ratulm ratulm commented Nov 21, 2017

this is mostly parsing. deeper integration of nat gateways is not done. opened issue #681 for that.


This change is Reviewable

@ratulm ratulm requested a review from arifogel November 21, 2017 22:05
@arifogel
Copy link
Member

One comment about warning verbosity, and one about static routes. Otherwise looks good.


Reviewed 9 of 9 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.


projects/batfish/src/main/java/org/batfish/representation/aws_vpcs/AwsVpcConfiguration.java, line 256 at r1 (raw file):

    for (NatGateway ngw : _natGateways.values()) {
      _warnings.redFlag("NAT functionality not yet implemented for " + ngw.getId());

Is it really necessary to warn for every NAT gateway?


projects/batfish/src/main/java/org/batfish/representation/aws_vpcs/Route.java, line 117 at r1 (raw file):

        case NatGateway:
          // TODO: it is NOT clear that this is the right thing to do
          // for NATs with multiple interfaces, we should probably match on private IPs?

I think we need to generalize this function to produce a List<StaticRoute>. For NatGateway, there should be one for each next-hop-ip.


Comments from Reviewable

@ratulm
Copy link
Member Author

ratulm commented Nov 22, 2017

Review status: all files reviewed at latest revision, 2 unresolved discussions.


projects/batfish/src/main/java/org/batfish/representation/aws_vpcs/AwsVpcConfiguration.java, line 256 at r1 (raw file):

Previously, arifogel (Ari Fogel) wrote…

Is it really necessary to warn for every NAT gateway?

no, but it was easiest that way. we'll add more support soon anyway.


projects/batfish/src/main/java/org/batfish/representation/aws_vpcs/Route.java, line 117 at r1 (raw file):

Previously, arifogel (Ari Fogel) wrote…

I think we need to generalize this function to produce a List<StaticRoute>. For NatGateway, there should be one for each next-hop-ip.

ack. will do as part of proper nat processing


Comments from Reviewable

@arifogel
Copy link
Member

:lgtm:


Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.


Comments from Reviewable

@arifogel arifogel merged commit 69d2a24 into master Nov 22, 2017
@arifogel arifogel deleted the nat-parsing branch November 22, 2017 20:33
Sign up for free to 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.

None yet

2 participants