Skip to content

[enterprise-4.7] [OSP] MachineSet primary subnet support #28663

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

Merged
maxwelldb merged 8 commits into from
Jan 18, 2021
Merged

[enterprise-4.7] [OSP] MachineSet primary subnet support #28663

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
d0b07c4
Document multi-network OSP machinesets
maxwelldb Dec 23, 2020
606654e
Cannot/does not clarification
maxwelldb Jan 11, 2021
8961b25
Update modules/installation-osp-custom-subnet.adoc
maxwelldb Jan 18, 2021
4a17365
Update modules/installation-osp-custom-subnet.adoc
maxwelldb Jan 18, 2021
f2bd53a
Update modules/installation-osp-custom-subnet.adoc
maxwelldb Jan 18, 2021
1844bdc
Update modules/installation-osp-custom-subnet.adoc
maxwelldb Jan 18, 2021
9b4d41c
Update modules/installation-osp-custom-subnet.adoc
maxwelldb Jan 18, 2021
aed646d
Reordering an UL element
maxwelldb Jan 18, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions modules/installation-osp-custom-subnet.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,19 +11,21 @@

Optionally, you can deploy a cluster on a {rh-openstack-first} subnet of your choice. The subnet's GUID is passed as the value of `platform.openstack.machinesSubnet` in the `install-config.yaml` file.

This subnet is used as the cluster's primary subnet; nodes and ports are created on it.
This subnet is used as the cluster's primary subnet. By default, nodes and ports are created on it. You can create nodes and ports on a different {rh-openstack} subnet by setting the value of the `platform.openstack.machinesSubnet` property to the subnet's UUID.

Before you run the {product-title} installer with a custom subnet, verify that:
Before you run the {product-title} installer with a custom subnet, verify that your configuration meets the following requirements:

* The target network and subnet are available.
* The subnet that is used by `platform.openstack.machinesSubnet` has DHCP enabled.
* The CIDR of `platform.openstack.machinesSubnet` matches the CIDR of `networking.machineNetwork`.
* The installation program user has permission to create ports on this network, including ports with fixed IP addresses.

* DHCP is enabled on the target subnet.
Clusters that use custom subnets have the following limitations:

* You can provide installer credentials that have permission to create ports on the target network.
* If you plan to install a cluster that uses floating IP addresses, the `platform.openstack.machinesSubnet` subnet must be attached to a router that is connected to the `externalNetwork` network.

* If your network configuration requires a router, it is created in {rh-openstack}. Some configurations rely on routers for floating IP address translation.
* If the `platform.openstack.machinesSubnet` value is set in the `install-config.yaml` file, the installation program does not create a private network or subnet for your {rh-openstack} machines.

* Your network configuration does not rely on a provider network. Provider networks are not supported.
* You cannot use the `platform.openstack.externalDNS` property at the same time as a custom subnet. To add DNS to a cluster that uses a custom subnet, configure DNS on the {rh-openstack} network.

[NOTE]
====
Expand Down
8 changes: 6 additions & 2 deletions modules/machineset-yaml-osp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,13 @@ spec:
image: <glance_image_name_or_location>
serverGroupID: <optional_UUID_of_server_group> <4>
kind: OpenstackProviderSpec
networks:
networks: <5>
- filter: {}
subnets:
- filter:
name: <subnet_name>
tags: openshiftClusterID=<infrastructure_ID>
primarySubnet: <rhosp_subnet_UUID> <6>
securityGroups:
- filter: {}
name: <infrastructure_ID>-<node_role>
Expand All @@ -73,4 +74,7 @@ $ oc get -o jsonpath='{.status.infrastructureName}{"\n"}' infrastructure cluster
----
<2> Specify the node label to add.
<3> Specify the infrastructure ID and node label.
<4> To set a server group policy for the machine set, enter the value that is returned from link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/command_line_interface_reference/server#server_group_create[creating a server group]. For most deployments, `anti-affinity` or `soft-anti-affinity` policies are recommended.
<4> To set a server group policy for the MachineSet, enter the value that is returned from
link:https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/command_line_interface_reference/server#server_group_create[creating a server group]. For most deployments, `anti-affinity` or `soft-anti-affinity` policies are recommended.
<5> Required for deployments to multiple networks. If deploying to multiple networks, this list must include the network that is used as the `primarySubnet` value.
<6> Specify the {rh-openstack} subnet that you want the endpoints of nodes to be published on. Usually, this is the same subnet that is used as the value of `machinesSubnet` in the `install-config.yaml` file.