Change CPU/Memory Allocations (Socket Granularity)

Language:

Perform this procedure on each compute node to change its CPU and memory resource allocation at the socket granularity level.

Note - To find out if you can perform this procedure, see Supported Domain Configurations.

The tool makes these changes:

Automatically detects Root Domains.
Calculates the minimum and maximum resources for all domains, and only enables you to select valid quantities.
Modifies domain resources according to the choices you make.
Automatically assigns memory capacity in the same proportion to CPU resources.
(If needed) Stops nonprimary domains.
(If needed) Reboots the primary domain with new resources .
(If needed) Brings up nonprimary domains with new resources.

In this example, one socket and 1 TB memory are removed from the primary domain and allocated to ssccn3-dom1.

This table shows the allocation plan (see Plan CPU and Memory Allocations).

Domain	Domain Type	Sockets Before	Sockets After	Memory Before (GB)	Memory After (GB)
`primary`	Dedicated	2	1	2048	1024
`ssccn3-dom1`	Dedicated	2	3	2048	3072
`ssccn3-dom2`	Root	n/a	n/a	n/a	n/a
`ssccn3-dom3`	Root	n/a	n/a	n/a	n/a
Unallocated resources		45	45	4048	4048
Total resources		49	39	4144	4144

Log in as superuser on the compute node's control domain.

Ensure that applications are shut down and that there is no production activity.

Activate any inactive domains using the ldm bind command.
The tool does not continue if any inactive domains are present.

Run osc-setcoremem to reconfigure the resources.

Respond when prompted. Press Enter to select the default value.

# /opt/oracle.supercluster/bin/osc-setcoremem
 
                              osc-setcoremem
                    v2.0  built on Aug 27 2015 23:09:35
 
 
 Current Configuration: SuperCluster Fully-Populated M6-32 Base
 
 +------------------------------+-------+--------+-----------+--- MINIMUM ----+
 | DOMAIN                           | CORES | MEM GB |   TYPE    | CORES | MEM GB |
 +------------------------------+-------+--------+-----------+-------+--------+
 | primary                          |    24 |   2048 | Dedicated |     2 |     32 |
 | ssccn3-dom1                      |    24 |   2048 | Dedicated |     2 |     32 |
 | ssccn3-dom2                      |     1 |     16 |   Root    |     1 |     16 |
 | ssccn3-dom3                      |     2 |     32 |   Root    |     2 |     32 |
 +------------------------------+-------+--------+-----------+-------+--------+
 | unallocated or parked            |    45 |   4048 |    --     |    -- |   --   |
 +------------------------------+-------+--------+-----------+-------+--------+
 
 [Note] Following domains will be skipped in this session.
 
 Root Domains
 ------------
 ssccn3-dom2
 ssccn3-dom3
 
 
 CPU allocation preference:
 
        1. Socket level
        2. Core level
 
 In case of Socket level granularity, proportional memory capacity is
  automatically selected for you.
 
 Choose Socket or Core level [S or C] s
 
 
 Step 1 of 1: Socket Count
 
 primary      : specify socket count [min: 1, max: 3. default: 1] : 1
                you chose [1] socket for primary domain
 
 ssccn3-dom1  : specify socket count [min: 1, max: 3. default: 1] : 3
                you chose [3] sockets for ssccn3-dom1 domain
 
 
 Configuration In Progress After Socket Count Selection:
 
 +----------------------------------+----------+----------+-----------+
 | DOMAIN                           |  SOCKETS |   MEM GB |   TYPE    |
 +----------------------------------+----------+----------+-----------+
 | primary                          |     1    |     1024 | Dedicated |
 | ssccn3-dom1                      |     3    |     3072 | Dedicated |
 | *ssccn3-dom2                     |   0.083  |       16 |   Root    |
 | *ssccn3-dom3                     |   0.167  |       32 |   Root    |
 +----------------------------------+----------+----------+-----------+
 | unallocated or parked            |   3.750  |     4048 |    --     |
 +----------------------------------+----------+----------+-----------+
 
 
 Following domains will be stopped and restarted:
 
        ssccn3-dom1
 
 This configuration requires rebooting the control domain.
 Do you want to proceed? Y/N : Y 
 
 +- IMPORTANT NOTE: -+
 |  After the reboot, osc-setcoremem attempts to complete CPU, memory re-configuration. |
 |  Please check syslog and the state of all domains before using the system.           |
 |  eg.,  dmesg | grep osc-setcoremem ; ldm list | grep -v active ; date |
 +- -+
 
 All activity is being recorded in log file:
        /opt/oracle.supercluster/osc-setcoremem/log/osc-setcoremem_activity_08-28-2015_15:31:27.log
 
 Please wait while osc-setcoremem is setting up the new CPU, memory configuration.
 It may take a while. Be patient and do not interrupt.
 
 0%    10    20    30    40    50    60    70    80    90   100%
 |-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|
 
 [Info] Domain ssccn3-dom1 is taking too long to stop. Waiting ..
 [Info] Domain ssccn3-dom1 is taking too long to stop. Still waiting for the domain to stop ..
 *=====*=====*=====*=====*=====*=====*=====*=====*=====*=====*
 
Broadcast Message from root (pts/1) on etc5mdbadm0301 Fri Aug 28 15:36:45...
THE SYSTEM etc5mdbadm0301 IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged
 
                Task complete with no errors.
 
#

Check the system log and the status of all logical domains to ensure that they are in active state before proceeding with the regular activity.

Example:

# dmesg | grep osc-setcoremem
Aug 28 15:43:46 etc5mdbadm0301 root[2074]: [ID 702911 user.alert] osc-setcoremem: core, memory re-configuration complete. system can be used for regular work.

Verify the new resource allocation.
You can verify the resource allocation and check for possible osc-setcoremem errors in several ways:

Repeat this procedure if you need to change resource allocations on another compute node.

Change CPU/Memory Allocations (Socket Granularity)

Related Information