Skip to content

Conversation

@maxwelldb
Copy link
Contributor

  • Add OSP-specific MachineSet example to infrastructure docs assembly
  • Add server group property to sample YAML
  • Add server group property guidance to sample callouts

Context:

@pierreprinetti Does this look copacetic to you?

@maxwelldb maxwelldb self-assigned this Sep 28, 2020
@openshift-ci-robot openshift-ci-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 28, 2020
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 28, 2020
@openshift-docs-preview-bot

The preview will be available shortly at:

----
<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.
Copy link
Member

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.

Copy link
Member

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".

@maxwelldb
Copy link
Contributor Author

@pierreprinetti How about 83aef78, then, if any policy works?

Would it make sense to say that we recommend anti-affinity or soft-anti-affinity policies for most deployments, or is that too prescriptive?

@pierreprinetti
Copy link
Member

or is that too prescriptive?

No Sir, that would be copacetic.

@maxwelldb
Copy link
Contributor Author

@pierreprinetti TY. Added recommendation in 8838967.

Copy link
Member

@pierreprinetti pierreprinetti left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@maxwelldb
Copy link
Contributor Author

Thanks! @pierreprinetti

@maxwelldb maxwelldb added this to the Next Release milestone Sep 30, 2020
@maxwelldb maxwelldb requested a review from gpei September 30, 2020 23:10
@maxwelldb maxwelldb requested review from gpei and morenod and removed request for gpei October 8, 2020 22:50
@sunzhaohua2
Copy link

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 14, 2020
Copy link
Contributor

@kalexand-rh kalexand-rh left a comment

Choose a reason for hiding this comment

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

LGTM

@maxwelldb
Copy link
Contributor Author

Thanks!

@maxwelldb maxwelldb merged commit 774217f into openshift:master Oct 14, 2020
@maxwelldb
Copy link
Contributor Author

maxwelldb commented Oct 14, 2020

/cherry-pick enterprise-4.5

@maxwelldb
Copy link
Contributor Author

maxwelldb commented Oct 14, 2020

/cherry-pick enterprise-4.6

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Oct 14, 2020

@maxwelldb: #25837 failed to apply on top of branch "enterprise-4.6":

Applying: Add MachineSet infra and server group content
Using index info to reconstruct a base tree...
M	machine_management/creating-infrastructure-machinesets.adoc
M	modules/machineset-yaml-osp.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/machineset-yaml-osp.adoc
Auto-merging machine_management/creating-infrastructure-machinesets.adoc
CONFLICT (content): Merge conflict in machine_management/creating-infrastructure-machinesets.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Add MachineSet infra and server group content
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick enterprise-4.6

Instructions 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.

@openshift-cherrypick-robot
Copy link

openshift-cherrypick-robot commented Oct 14, 2020

@maxwelldb: new pull request created: #26463

Details

In response to this:

/cherry-pick enterprise-4.5

Instructions 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.

maxwelldb added a commit to maxwelldb/openshift-docs that referenced this pull request Oct 14, 2020
* Add MachineSet infra and server group content

* Feedback tweak

* Add recommended policies
@maxwelldb maxwelldb deleted the aa-workers-osdocs1364 branch October 14, 2020 19:52
@yuvalk yuvalk mentioned this pull request Mar 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.5 branch/enterprise-4.6 lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants