MTV-2772: Scheduling target VMs #781
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RichardHoch
force-pushed
the
MTV-2772_target_vm_scheduling
branch
3 times, most recently
from
fa48ee0 to
8e77bc9
Compare
nunzy1
reviewed
Oct 23, 2025
...tion/doc-Migrating_your_virtual_machines/assemblies/assembly_advanced-migration-options.adoc
Outdated
Show resolved
Hide resolved
nunzy1
reviewed
Oct 23, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
nunzy1
reviewed
Oct 23, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
nunzy1
reviewed
Oct 23, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
nunzy1
reviewed
Oct 23, 2025
nunzy1
reviewed
Oct 23, 2025
nunzy1
reviewed
Oct 23, 2025
| + | ||
| Node Affinity and Node Anti-Affinity rules offer more flexible placement control than rigid Node Selector rules, because they support conditionals such as `or`, `and`, or `not`. For example, you could require that a VM be powered on "only if it is migrated to node A _or_ if it is migrated to an SSD disk, but it _cannot_ be migrated to a node for which `license-tier=silver` is true." | ||
| + | ||
| Additionally, both types of rules allow you to include both _hard_ and _soft_ conditions in the same rule. A hard condition is a requirement, and a soft condition is a preference. The previous example used only hard conditions. A rule that states that "a VM can be powered on if it is migrated to node A _or_ if it is migrated to an SSD disk, but it is preferred not to migrate it to a node for which `license-tier=silver` is true" is an example of a rule that uses soft conditions. |
Collaborator
There was a problem hiding this comment.
The example in the parens -- is that the way the rule must be worded? If not, maybe:
A rule that states that "a VM can be powered on if it is migrated to node A or if it is migrated to an SSD disk, but the preference is to not migrate to a node for which license-tier=silver is true" is...
Collaborator
Author
nunzy1
reviewed
Oct 23, 2025
nunzy1
reviewed
Oct 23, 2025
nunzy1
reviewed
Oct 23, 2025
nunzy1
reviewed
Oct 23, 2025
Collaborator
Author
|
@RichardHoch After you bring live migration and UDN into the new framework, remove the // in // UDNs are discussed in greater detail in xref:about-udn_mtv[About user defined networks]. Migration procedures have been updated to include UDNs. in selecting-migration-network-for-virt-provider.adoc . |
Pkylas007
reviewed
Oct 29, 2025
...tion/doc-Migrating_your_virtual_machines/assemblies/assembly_advanced-migration-options.adoc
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/about-configuring-target-vm-scheduling.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
documentation/modules/configuring-target-vm-scheduling-cli.adoc
Outdated
Show resolved
Hide resolved
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
Pkylas007
reviewed
Oct 29, 2025
Collaborator
Author
RichardHoch
force-pushed
the
MTV-2772_target_vm_scheduling
branch
from
4263af7 to
6015978
Compare
avivtur
reviewed
Oct 30, 2025
RichardHoch
force-pushed
the
MTV-2772_target_vm_scheduling
branch
from
6015978 to
44704b2
Compare
Collaborator
Author
RichardHoch
force-pushed
the
MTV-2772_target_vm_scheduling
branch
from
8c5d2ea to
d15b016
Compare
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MTV 2.10
Resolves https://issues.redhat.com/browse/MTV-2772 by adding a description of scheduling target VMs as well as UI and CLI procedures.
Preview: