Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Overview of subpolicies
Subpolicies allow you to group LPARs and manage them together within a policy. You can manage like LPARs in a subpolicy (for example, LPARs running a certain subsystem), and set an MSU limit for the subpolicy. Subpolicies can include LPARs and capacity group members. However, they cannot include capacity groups. Subpolicies can also manage LPARs that reside on multiple CPCs.
You might use a subpolicy in the following situation:
The main policy's MSU limit is 1000.
The policy contains five LPARs.
Two of the LPARs in the policy run high-cost workloads, and you must limit their collective MSU usage to 300.
You can create a subpolicy containing the LPARs running high-cost workloads, and set the subpolicy's MSU limit to 300. Therefore, the subpolicy LPARs will not exceed 300 MSUs, and the remaining 700 MSUs can be distributed to the LPARs in the main policy.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*
