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

uuid management #129

Closed
shettyg opened this issue May 7, 2015 · 2 comments
Closed

uuid management #129

shettyg opened this issue May 7, 2015 · 2 comments

Comments

@shettyg
Copy link

shettyg commented May 7, 2015

According to current API, I see that you pass "name" of a network while creating it in libnetwork. libnetwork in turn provides only the uuid to the driver.

e.g: docker network create -d ovn --name=foo

For multi-host networking, from a different host, if someone does a "docker network ls", will libnetwork somehow share state and list both the name and uuid?

If it does indeed share state, how is it going to store that persistent information?

@mavenugo
Copy link
Contributor

mavenugo commented May 7, 2015

@shettyg Yes. libnetwork will distribute the states and docker network ls will list a consistent name and uuid in all the clustered nodes. As described in the design document (https://github.com/docker/libnetwork/blob/master/docs/design.md), the Network and Endpoint objects have a global scope and the UUID is unique across the cluster.
The shared states work is not complete yet. But the general consensus is to use a distributed KV store.

@shettyg
Copy link
Author

shettyg commented May 7, 2015

Thanks @mavenugo. That answers my question. Closing

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

No branches or pull requests

2 participants