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

Avoid persisting ipam data if it can be reconstructed #1130

Merged
merged 1 commit into from
Jun 4, 2016
Merged

Avoid persisting ipam data if it can be reconstructed #1130

merged 1 commit into from
Jun 4, 2016

Conversation

aboch
Copy link
Contributor

@aboch aboch commented Apr 20, 2016

Related: moby/moby#23078

Signed-off-by: Alessandro Boch aboch@docker.com

@sanimej
Copy link

sanimej commented Apr 29, 2016

LGTM

@sanimej
Copy link

sanimej commented May 5, 2016

@aboch Thanks for adding the capability for the remote drivers

- Also restore older behavior where overlap check is not run
  when preferred pool is specified. Got broken by recent changes

Signed-off-by: Alessandro Boch <aboch@docker.com>
@mavenugo
Copy link
Contributor

mavenugo commented Jun 4, 2016

LGTM

@mavenugo mavenugo merged commit a8923f0 into moby:master Jun 4, 2016
@chenchun
Copy link
Contributor

I think such of the non-atomic problems should be solved if we can make use of atomic operations? I know that all storage backend zookeeper/consol/etcd/boltdb support atomic put/delete of multiple KVs. Perhaps libkv should support atomic put/delete of multiple KVs.

@aboch aboch deleted the noips branch June 27, 2016 18:43
WeiZhang555 pushed a commit to WeiZhang555/moby that referenced this pull request Nov 25, 2016
… shutdown

cherry-pick from upstream
see moby/libnetwork#1119
and moby/libnetwork#1130

Signed-off-by: Alessandro Boch <aboch@docker.com>
Signed-off-by: Jana Radhakrishnan <mrjana@docker.com>
Signed-off-by: Lei Jitang <leijitang@huawei.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants