This repository was archived by the owner on Aug 1, 2023. It is now read-only.
[rfr] Making SubnetID optional during pool and vip creation #607
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jrperritt could you PTAL |
|
This repo is closed to changes. In addition, the options in this repo (and the new one) are for OpenStack proper, not customizations. Custom options may be passed to functions by satisfying the interface of the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At eBay, we have made changes to openstack to not have SubnetID mandatory during loadbalancer pool and vip creation. The LbaaS scheduler will find the right LB and the right subnet to create a vip and pool. And hence this can be optional.
This patch is needed to integrate Kubernetes with our internal private cloud LBaaS
cc @ashw7n @khgandhi