Skip to content
Merged
Changes from all commits
Commits
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
11 changes: 9 additions & 2 deletions docs/user/openstack/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -433,7 +433,7 @@ rm -rf ostest/

Groups of Compute nodes are managed using the [MachineSet][machine-set-code] resource. It is possible to create additional MachineSets post-install, for example to assign workloads to specific machines.

When running on OpenStack, the MachineSet has platform-specific fields:
When running on OpenStack, the MachineSet has platform-specific fields under `spec.template.spec.providerSpec.value`:

```yaml
apiVersion: machine.openshift.io/v1beta1
Expand Down Expand Up @@ -487,6 +487,7 @@ spec:
trunk: true
userDataSecret:
name: <node_role>-user-data
availabilityZone: <optional_openstack_availability_zone>
```

#### Using a Server Group
Expand All @@ -502,9 +503,15 @@ openstack --os-compute-api-version=2.15 server group create --policy=soft-anti-a
```

If the command is successful, the OpenStack CLI will return the ID of the newly
created Server Group. Paste it in the optional "serverGroupID" property of the
created Server Group. Paste it in the optional `serverGroupID` property of the
MachineSet.

#### Deploying on Availability Zones

In order to use Availability Zones, create one MachineSet per target
Availability Zone, and set the Availability Zone in the `availabilityZone`
property of the MachineSet.

[machine-set-code]: https://github.com/openshift/cluster-api-provider-openstack/blob/master/pkg/apis/openstackproviderconfig/v1alpha1/types.go
[server-group-docs]: https://docs.openstack.org/api-ref/compute/?expanded=create-server-group-detail#create-server-group

Expand Down