Skip to content

Add MachineSet infra and server group content #25837

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 4 commits into from
Oct 14, 2020
Merged

Add MachineSet infra and server group content #25837

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
94a633e
Add MachineSet infra and server group content
maxwelldb Sep 28, 2020
25d0cd4
Merge branch 'master' into aa-workers-osdocs1364
maxwelldb Sep 28, 2020
83aef78
Feedback tweak
maxwelldb Sep 29, 2020
8838967
Add recommended policies
maxwelldb Sep 29, 2020
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
2 changes: 2 additions & 0 deletions machine_management/creating-infrastructure-machinesets.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,8 @@ You can save on costs by using preemptible VM instances at a lower price
compared to normal instances on GCP. You can xref:../machine_management/creating_machinesets/creating-machineset-gcp.adoc#machineset-creating-non-guaranteed-instance_creating-machineset-gcp[configure preemptible VM instances]
by adding `preemptible` to the MachineSet YAML file.

include::modules/machineset-yaml-osp.adoc[leveloffset=+3]

include::modules/machineset-creating.adoc[leveloffset=+2]

[id="moving-resources-to-infrastructure-machinesets"]
Expand Down
2 changes: 2 additions & 0 deletions modules/machineset-yaml-osp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,7 @@ spec:
namespace: openshift-machine-api
flavor: <nova_flavor>
image: <glance_image_name_or_location>
serverGroupID: <optional_UUID_of_server_group> <4>
kind: OpenstackProviderSpec
networks:
- filter: {}
Expand Down Expand Up @@ -78,3 +79,4 @@ $ 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> Enter the value that is returned when 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]. The server group must have `anti-affinity` or `soft-anti-affinity` policies.

@pierreprinetti pierreprinetti Sep 29, 2020

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, while I can't imagine a reason for setting affinity or soft-affinity, any policy (or none) is fine as far as OpenShift is concerned.

@pierreprinetti pierreprinetti Sep 29, 2020

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd go like:
"Can be used to set an anti-affinity policy for the MachineSet".