-
Notifications
You must be signed in to change notification settings - Fork 879
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
Fix internal macvlan network to work in swarm #2419
Conversation
Please sign your commits following these rules: $ git clone -b "2418-fix" git@github.com:lemrouch/libnetwork.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842357810328
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f Amending updates the existing PR. You DO NOT need to open a new one. |
can you sign the commit with above instruction? |
Hi, my impression was dco-signed — All commits are signed and All checks have passed means it's already done. |
you need to amend commit with -s option. I think that is what expected from the above message. if you have already done it, not sure why we received 'sing your commit' messages. |
There was unsigned merge fixed by: |
What can I do to get this commit merged? |
…ing to stop working in a cluster.
@lemrouch if the intent of this PR is to separate the notion of |
I see so both the above code flows are redundant for your case ( config-from networks ), have you tested these changes out ? Can you please share a working example |
Yes, I have tested them in combination with #2407 |
Thanks, please share a snippet of the working commands when possible |
Example is in #2418 |
About lines 65 and 93 mentioned above: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM , thanks for sharing the working example in #2418 (comment)
ptal @selansen
Thanks! |
also do we need a similar change for ipvlan ? |
Frankly I don't know. I have not read nor tried that code. I can check it on Monday. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@lemrouch can you please make similar changes in https://github.com/docker/libnetwork/blob/6659f7f4d8c1ec7a412a33f8973423ad38d22982/drivers/ipvlan/ipvlan_network.go#L197 |
thanks, will merge on green |
Do you know what went wrong? I'm not familiar with your tests. |
can you please rebase to the latest master, we fixed a bunch of flaky tests a while back |
|
Using dummy interface allows communication beween containers only if they are running on the same node in swam. Signed-off-by: Pavel Matěja <pavel@verotel.cz>
Using dummy interface allows communication beween containers only if they are running on the same node in swarm. Signed-off-by: Pavel Matěja <pavel@verotel.cz>
moby#2419 and moby#2407 attempted to seperate out empty parent and internal for macvlan and ipvlan networks However it didnt pass the integration tests in moby moby/moby#40596 and exposed some more plumbing that needed to be done to make sure we seperate the two things If the -o parent is empty we create a dummylink and if internal is set we dont add a default gateway and make sure north-south communication cannot take place (only east-west / container-container can) Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com>
moby#2419 and moby#2407 attempted to seperate out empty parent and internal for macvlan and ipvlan networks However it didnt pass the integration tests in moby moby/moby#40596 and exposed some more plumbing that needed to be done to make sure we seperate the two things If the -o parent is empty we create a dummylink and if internal is set we dont add a default gateway and make sure north-south communication cannot take place (only east-west / container-container can) Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com>
moby#2419 and moby#2407 attempted to seperate out empty parent and internal for macvlan and ipvlan networks However it didnt pass the integration tests in moby moby/moby#40596 and exposed some more plumbing that needed to be done to make sure we separate the two things If the -o parent is empty we create a dummylink and if internal is set we dont add a default gateway and make sure north-south communication cannot take place (only east-west / container-container can) Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com>
moby#2419 and moby#2407 attempted to seperate out empty parent and internal for macvlan and ipvlan networks However it didnt pass the integration tests in moby moby/moby#40596 and exposed some more plumbing that needed to be done to make sure we separate the two things If the -o parent is empty we create a dummylink and if internal is set we dont add a default gateway and make sure north-south communication cannot take place (only east-west / container-container can) Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com>
moby/libnetwork#2419 and moby/libnetwork#2407 attempted to seperate out empty parent and internal for macvlan and ipvlan networks However it didnt pass the integration tests in moby moby#40596 and exposed some more plumbing that needed to be done to make sure we separate the two things If the -o parent is empty we create a dummylink and if internal is set we dont add a default gateway and make sure north-south communication cannot take place (only east-west / container-container can) Signed-off-by: Arko Dasgupta <arko.dasgupta@docker.com>
Using dummy interface allows communication beween containers only if
they are running on the same node in swam.
Signed-off-by: Pavel Matěja pavel@verotel.cz