Change CPU/Memory Allocations (Core Granularity)

Language:

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

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

Note - Examples are based on SuperCluster M6-32, however, the same concepts apply to SuperCluster M7 and SuperCluster M8.

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.
Presents viable memory capacities for you to select, based on your core allocations.
Modifies domain resources according to the choices you make.
(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, 6 cores and 512 GB memory are moved from dedicated domain ssccn3-dom1 to another dedicated domain, primary.

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

Domain	Domain Type	Cores Before	Cores After	Memory Before (GB)	Memory After (GB)
`primary`	Dedicated	12	18	1024	1536
`ssccn3-dom1`	Dedicated	36	30	3072	2560
`ssccn3-dom2`	Root	N/A	N/A	N/A	N/A
`ssccn3-dom3`	Root	N/A	N/A	N/A	N/A
Unallocated		45	45	4048	4048
Total resources		93	93	8144	8144

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

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

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                          |    12 |   1024 | Dedicated |     2 |     32 |
 | ssccn3-dom1                      |    36 |   3072 | 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] C

 Step 1 of 2: Core Count

 primary      : specify number of cores [min: 2, max: 46. default: 12] : 18
                you chose [18] cores for primary domain

 ssccn3-dom1  : specify number of cores [min: 2, max: 30. default: 2] : 30
                you chose [30] cores for ssccn3-dom1 domain

Configuration In Progress After Core Count Selection:
 +----------------------------------+-------+--------+-----------+--- MINIMUM ----+
 | DOMAIN                           | CORES | MEM GB |   TYPE    | CORES | MEM GB |
 +---------------------------------+-------+--------+-----------+-------+--------+
 | primary                          |    18 |   1024 | Dedicated |     2 |     96 |
 | ssccn3-dom1                      |    30 |   3072 | Dedicated |     2 |    128 |
 | *ssccn3-dom2                     |     1 |     16 |   Root    |     1 |     16 |
 | *ssccn3-dom3                     |     2 |     32 |   Root    |     2 |     32 |
 +----------------------------------+-------+--------+-----------+-------+--------+
 | unallocated or parked            |    45 |   4048 |    --     |    -- |   --   |
 +---------------------------------+-------+--------+-----------+-------+--------+

 Step 2 of 2: Memory Capacity
        (must be 16 GB aligned)

 primary: specify memory capacity in GB [min: 96, max: 2016. default: 2016]: 1536
                you chose [1536 GB] memory for primary domain

 ssccn3-dom1: specify memory capacity in GB [min: 128, max: 2560. default: 2560]: 2560
                you chose [2560 GB] memory for ssccn3-dom1 domain

Configuration In progress After Memory Capacity Selection:
 +---------------------------------+-------+--------+-----------+--- MINIMUM ----+
 | DOMAIN                           | CORES | MEM GB |   TYPE    | CORES | MEM GB |
 +---------------------------------+-------+--------+-----------+-------+--------+
 | primary                          |    18 |   1536 | Dedicated |     2 |     96 |
 | ssccn3-dom1                      |    30 |   2560 | Dedicated |     2 |    128 |
 | *ssccn3-dom2                     |     1 |     16 |   Root    |     1 |     16 |
 | *ssccn3-dom3                     |     2 |     32 |   Root    |     2 |     32 |
 +---------------------------------+-------+--------+-----------+-------+--------+
 | unallocated or parked            |    45 |   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:59:31.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%
 |-----|-----|-----|-----|-----|-----|-----|-----|-----|-----|
 *=====*=====*=====*=====*=====*=====*=====*=====*=====*=====*

Broadcast Message from root (pts/1) on etc5mdbadm0301 Fri Aug 28 16:03:13...
THE SYSTEM etc5mdbadm0301 IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged

                Task complete with no errors.

Verify the new resource allocation.

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

For example:

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

# ldm list
NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  NORM  UPTIME
primary          active     -n-cv-  UART    144   1572096M 0.1%  0.1%  5m
ssccn3-dom1      active     -n----  5001    240   2620928M 1.3%  1.3%  2m
ssccn3-dom2      active     -n----  5002    8     16G      0.1%  0.1%  3d 16m
ssccn3-dom3      active     -n--v-  5003    16    32G      0.1%  0.1%  3d 16m

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

Oracle^® SuperCluster M8 and SuperCluster M7 Administration Guide

Change CPU/Memory Allocations (Core Granularity)

Related Information