CNV-10445 [1926199] VM Migration of mixed CPU (AMD,Intel) #30340
Conversation
openshift-ci-robot
added
the
size/XS
|
Deploy preview for osdocs ready! Built with commit 0990a18 |
|
/lgtm |
|
@ILpinto: changing LGTM is restricted to collaborators In response to this:
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. |
There was a problem hiding this comment.
I think that we should change the sentence to :
To be able to migrate virtual machines into the cluster, ensure that all nodes in a single pool use the same type of CPU. For example, nodes in one pool can use AMD processors and nodes in another pool can use Intel processors, and so on. Avoid mixing different CPU types in the same pool.
Thanks for the suggestion. I'll see what the peer reviewers prefer in terms using "into the" vs. "to a" --- our style guidelines are pretty specific in cases like this. |
bgaydosrh
force-pushed
the
CNV-10445
branch
2 times, most recently
from
5d73438 to
5d7fca7
Compare
ousleyp
added
CNV
bgaydosrh
force-pushed
the
CNV-10445
branch
2 times, most recently
from
2dc1f74 to
3a8516d
Compare
openshift-ci-robot
added
the
do-not-merge/hold
bgaydosrh
force-pushed
the
CNV-10445
branch
2 times, most recently
from
4496d8f to
3beff99
Compare
bgaydosrh
force-pushed
the
CNV-10445
branch
2 times, most recently
from
05bcf5d to
1273f0d
Compare
bgaydosrh
force-pushed
the
CNV-10445
branch
2 times, most recently
from
cbf98bd to
a034d34
Compare
openshift-ci-robot
removed
the
do-not-merge/hold
|
@bgaydosrh, I think we are ok to move on , aren't we? |
yes, I dropped my "hold". If the text is good, you can /lgtm it, but I would like to see the "CPU pool" term dropped from this PR title. |
Moving this to Peer Review for final check and merge. |
bgaydosrh
changed the title
|
/cherrypick enterprise-4.8 |
|
/cherrypick enterprise-4.7 |
|
@sjhala-ccs: new pull request created: #31624 In response to this:
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. |
|
@sjhala-ccs: new pull request created: #31625 In response to this:
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. |
|
/cherrypick enterprise-4.6 |
|
@sjhala-ccs: new pull request created: #31626 In response to this:
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. |
|
/cherrypick enterprise-4.5 |
|
@sjhala-ccs: new pull request created: #31627 In response to this:
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. |
8 participants
Label for enterprise-4.5, 4.6, 4.7, 4.8
Added this bullet to the prereqs listed in the Configuring your cluster for OpenShift Virtualization assembly:
Before you migrate virtual machines to a cluster, ensure that all nodes in a single pool use the same type of CPU. For example, place nodes that use AMD processors in one pool and place nodes that use Intel processors in a different pool. Do not mix different CPU types in the same pool.
Jira: https://issues.redhat.com/browse/CNV-10445
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1926199
Test Build: https://deploy-preview-30340--osdocs.netlify.app/openshift-enterprise/latest/virt/install/preparing-cluster-for-virt.html
Tagging @kobi86 for Code Review
Tagging Israel Pinto for QE Review in Jira record.