Go to main content
Oracle® SuperCluster M7 Series Administration Guide

Exit Print View

Updated: March 2017
 
 

Change CPU/Memory Allocations Non-Interactively

By default, osc-setcoremem runs in interactive mode, prompting you for input as it runs. As of SuperCluster version 2.3, you can provide all of the required input using a combination options on a single command line.

You can use this procedure to change resource allocations at the core or socket granularity level.


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

Non-Interactive syntax:

osc-setcoremem -type socket|core -res [min|max|x_sockets|x_cores/x_memgb]:[...]:[min|max|x_sockets|x_cores/x_memgb] [-y|-n] [-h|-help]

Option
Arguments
Description
-type
Specifies the type of granularity used for resource allocations. The choices are:
socket
Specifies socket granularity.
core
Specifies core granularity.
-res
Is the resource option that Is followed by the resource assignments for each of the eligible domains with each resource assignment separated by a : (colon).
The order of resource assignments matches the order shown in the output from osc-setcoremem -list (see Display the Current Domain Configuration (osc-setcoremem)).
You can specify symbolic values like min or max, and the tool automatically calculates the resource allocation values, or specify an explicit integer. You can mix the symbolic values and integer values.
The choices are:
min or MIN
Specifies the minimum possible resource assignment.
max or MAX
Specifies the maximum possible resource assignment.
current or CURRENT
Accepts the current value as is. If it is not possible to retain the current value, the tool will use a value that is as close as possible to the current value.
x_sockets
or
x_cores/x_memgb
Specify integer values for the resource assignments. Use one of these values:
  • x_sockets – For socket granularity, an integer that specifies the number of sockets. The tool automatically assigns proportional memory.

  • x_cores/x_memgb – For core granularity, The first integer specifies the number of cores, the second integer specifies the amount of memory in gigabytes (in multiples of 16 GB). For example: 12/256 indicates 12 cores and 256 GB of memory.

Note -  For x_sockets, x_cores, and x_memgb, you can specify min and max instead of a specific integer.

-y or -n
An optional option, that determines if you are prompted to confirm changes or not. The choices are:
  • -n – The tool displays the new resource allocations and you are prompted to confirm the changes. You can use this option to conduct a dry run without making actual changes by cancelling at the confirmation.

  • -y – As soon as you press Return, the tool immediately proceeds to make the resource allocations. You are not prompted for confirmation.

If omitted, -n is assumed.
-h or -help
Lists all of the non-interactive options and arguments that are listed in this table.

These examples show the variety of arguments you can specify for the -res option:

# osc-setcoremem -type socket -res min:max:min
# osc-setcoremem -type socket -res 2:max:min -y
# osc-setcoremem -type socket -res 1:2:1:2 -n
# osc-setcoremem -type socket -res 2:current:min -y
# osc-setcoremem -type socket -res 1:min:2:max -y
# osc-setcoremem -type core -res min/min:min/max:min/min
# osc-setcoremem -type core -res 12/512:6/64:18/128 -y
# osc-setcoremem -type core -res min/current:max/32:current/current
# osc-setcoremem -type core -res 4/96:min/32:16/max -n
# osc-setcoremem -type core -res min/min:min/32:max/512:8/48 -y
  1. Log in as superuser on the compute node's control domain.
  2. For any domains that might require restarting after the reconfiguration, ensure that all applications are shut down and that there is no production activity running.
  3. Activate any inactive domains using the ldm bind command.

    The tool does not continue if any inactive domains are present.

  4. List the current resource allocations.

    Example:

    # /opt/oracle.supercluster/bin/osc-setcoremem -l
    
                            osc-setcoremem (batch mode)
                        v2.3  built on Sep 26 2016 15:15:32
    
     Current Configuration: SuperCluster Half-Populated M7 Extended
    
     +-----+----------------------------------+---- CURRENT ---+-----------+--- MIN REQD ---+
     |  ID | DOMAIN                           | CORES | MEM GB |   TYPE    | CORES | MEM GB |
     +-----+----------------------------------+-------+--------+-----------+-------+--------+
     |   1 | primary                          |    32 |    240 | Dedicated |     2 |     32 |
     |   2 | ssccn1-dom1                      |    32 |    240 | Dedicated |     2 |     32 |
     |   3 | ssccn1-dom2                      |    32 |    240 | Dedicated |     2 |     32 |
     +-----+----------------------------------+-------+--------+-----------+-------+--------+
    
  5. Run osc-setcoremem non-interactively to reconfigure the resources.

    Example:

    # /opt/oracle.supercluster/bin/osc-setcoremem -type core -res 16/128:min/min:max/max
    
                            osc-setcoremem (batch mode)
                        v2.3  built on Sep 26 2016 15:15:32
    
     Current Configuration: SuperCluster Half-Populated M7 Extended
    
     +----------------------------------+-------+--------+-----------+--- MINIMUM ----+
     | DOMAIN                           | CORES | MEM GB |   TYPE    | CORES | MEM GB |
     +----------------------------------+-------+--------+-----------+-------+--------+
     | primary                          |    32 |    240 | Dedicated |     2 |     32 |
     | ssccn1-dom1                      |    32 |    240 | Dedicated |     2 |     32 |
     | ssccn1-dom2                      |    32 |    240 | Dedicated |     2 |     32 |
     | ssccn1-dom3                      |     2 |     32 |   Root    |     2 |     32 |
     | *ssccn1-io-etc4m7-ioappadm0101   |     2 |     32 |    IO     |     1 |     16 |
     | *ssccn1-io-etc4m7zioadm0101      |     4 |  62.50 |    IO     |     1 |     16 |
     +----------------------------------+-------+--------+-----------+-------+--------+
     | Not in Use (Parked)              |    24 |    114 |    --     |    -- |   --   |
     +----------------------------------+-------+--------+-----------+-------+--------+
    
     [ INFO ] following domains will be ignored in this session.
    
     Root Domains              IO Domains
     ------------              ----------
     ssccn1-dom3               ssccn1-io-etc4m7-ioappadm0101
                               ssccn1-io-etc4m7zioadm0101
    
     Configuration In Progress After Memory Capacity Selection:
    
     +----------------------------------+-------+--------+-----------+--- MINIMUM ----+
     | DOMAIN                           | CORES | MEM GB |   TYPE    | CORES | MEM GB |
     +----------------------------------+-------+--------+-----------+-------+--------+
     | primary                          |    16 |    128 | Dedicated |     2 |     64 |
     | ssccn1-dom1                      |     2 |     32 | Dedicated |     2 |     32 |
     | ssccn1-dom2                      |    78 |    560 | Dedicated |     2 |    320 |
     | *ssccn1-dom3                     |     2 |     32 |   Root    |     2 |     32 |
     | *ssccn1-io-etc4m7-ioappadm0101   |     2 |     32 |    IO     |     1 |     16 |
     | *ssccn1-io-etc4m7zioadm0101      |     4 |  62.50 |    IO     |     1 |     16 |
     +----------------------------------+-------+--------+-----------+-------+--------+
     | Not in Use (Parked)              |    24 |    114 |    --     |    -- |   --   |
     +----------------------------------+-------+--------+-----------+-------+--------+
    
     Following domains will be restarted:
    
            ssccn1-dom2
            ssccn1-dom1
    
     This configuration change requires rebooting the Control Domain.
     Do you want to proceed? Y/N : y
    
    
  6. Verify the new resource allocation.

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

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

Related Information