OpenStack: Custom API and Ingress vip addresses#3366
OpenStack: Custom API and Ingress vip addresses#3366openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
|
/cc @Fedosin |
|
/label platform/openstack |
|
/retest |
There was a problem hiding this comment.
APIVIP is the static IP...
There was a problem hiding this comment.
IngressVIP is the static IP...
There was a problem hiding this comment.
fldPath.Child("ingressVIP")
There was a problem hiding this comment.
fldPath.Child("ingressVIP")
|
/hold race condition for ports |
|
/hold cancel |
|
/retest |
|
/lgtm |
There was a problem hiding this comment.
machinesNetwork -> machineNetwork
also it seems like we pick the 5th host in the first network range of the list.
There was a problem hiding this comment.
the 2 step check is same for API and ingress VIP, so maybe use one function for both..
There was a problem hiding this comment.
| MachineNetwork: []types.MachineNetworkEntry{ | |
| { | |
| CIDR: *ipnet.MustParseCIDR("10.0.0.0/16"), | |
| }, | |
| }, | |
| MachineNetwork: []types.MachineNetworkEntry{{ | |
| CIDR: *ipnet.MustParseCIDR("10.0.0.0/16"), | |
| }}, |
|
few nits, but i'll leave them upto openstack-approvers /approve /hold just to give people some time to fix the nits, please free to remove. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
co-authored-by: Fedosin mfedosin@redhat.com
|
/lgtm |
|
/retest |
|
/hold cancel |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
9 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@iamemilio: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
| * `region` (deprecated string): The OpenStack region where the cluster will be created. Currently this value is not used by the installer. | ||
| * `trunkSupport` (optional string): Whether OpenStack ports can be trunked (`1` for true or `0` for false) | ||
| * `clusterOSImage` (optional string): Either a URL with `http(s)` or `file` scheme to override the default OS image for cluster nodes or an existing Glance image name. | ||
| * `clusterOSimage` (optional string): Either a URL with `http(s)` or `file` scheme to override the default OS image for cluster nodes or an existing Glance image name. |
There was a problem hiding this comment.
This needs to match the Go JSON serialization. Fixed via #3439.
Customers may want to plumb the networking that enables external access to the cluster in a number of ways. To make their job easier, this feature allows them to select fixed IP addresses that they can reach the API and apps ingress at in their OpenShift cluster. This allows them to use/reuse pre-existing routing and external access schemes more easily. This adds an additional optional set of values to the openstack platform section of the install config as follows:
Note that the default values have not changed. APIVIP still defaults to the
5on the machineNetwork, and IngressVIP still defaults to the7.