Resource Pools for Solaris Containers Managed in Resource Orchestrator
In Resource Orchestrator, resource management is performed with one resource pool for Solaris Containers being managed in each global zone.
The target resource pool can be changed.
For details, refer to "C.7.1 Creating Definition Files".
Operations when uuids Change in Solaris Containers
In Resource Orchestrator, manage the non-global zone using uuids.
In Solaris Containers, as a uuid is configured for each OS, the uuid for a non-global zone changes when the OS in the non-global zone is re-installed, or the global zone in which the non-global zone starts is changed.
When a uuid changes, it is necessary to relate it to the L-Server and import it to the L-Platform, as Resource Orchestrator recognizes the non-global zone being a new one.
Release the L-Server from the L-Platform and delete the L-Server, next, relate the server to the L-Server and import L-Server to the L-Platform.
Refer to "7.2.3.3 Releasing L-Servers" of "Operation Guide CE" about releasing the L-Server from the L-Platform.
Refer to "17.4 Deleting an L-Server" of "User's Guide CE" about deleting the L-Server.
Refer to "7.2.3 Importing to L-Platform" of "Operation Guide CE" about importing the L-Server to the L-Platform.
Non-global Zone Charges
The following settings need to be made when creating the non-global zone if the non-global zone's CPU or memory will be using the metering and usage fee functions.
However, these settings are not necessary if metering and usage fee functions are not used, or if the CPU or memory are not made the subject of charges.
Subject of charges | Required settings |
|---|---|
CPU | Perform CPU sharing settings |
Memory | Perform memory capping settings |
Refer to the documentation that that comes with the Operating System for information on CPU sharing and memory capping.
