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.

Sign up for GitHub

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

Jump to bottom

improve vxnet choose #15

Open
jolestar opened this issue Jul 27, 2017 · 3 comments
Open

improve vxnet choose #15

jolestar opened this issue Jul 27, 2017 · 3 comments
Assignees
@martinyunify
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@jolestar
Copy link
Contributor

hostnic-cni use a random strategy to choose vxnet currently, if vxnet is full, will raise a error.
@martinyunify martinyunify mentioned this issue Aug 23, 2017
Merged
@martinyunify
Copy link
Contributor

add retry but vxnet capacity is not a stable way to choose vxnet since nics can be deleted from other host

@martinyunify
Copy link
Contributor

manage vxnet for end user. user can also specify vxnet for use.

@martinyunify martinyunify added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 7, 2017
@martinyunify
Copy link
Contributor

hostnic daemon is deployed to each k8s node and we can add tag for each node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martinyunify martinyunify

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jolestar @martinyunify