Changing a running Elastic Capacity on Demand request

In a running ElasticCapacity on Demand (CoD) request, you can change the number of resources, number of days, or both the number of resources and number of days. You do not need to stop the current request to start a new request or wait until the current request expires.

Before you change a running Elastic CoD request, ensure that you understand the implications to billing. For more information, see Billing when changing a running Elastic Capacity on Demand request.

To successfully change a running Elastic CoD request:

  1. If you are decreasing the amount of resources in the running request, return the Elastic CoD resources to be deactivated. See Returning Elastic Capacity on Demand resources for details about how to return Elastic CoD resources.
  2. by using the Hardware Management Console (HMC), choose one of the following navigation options depending on the interface type of the HMC:
    • If you are using the HMC Classic or HMC Enhanced interface, use the HMC Capacity on Demand > Processor or Memory > Elastic CoD > Manage task.
    • If you are using the HMC Enhanced+ interface, use the Capacity on Demand > CoD functions > Manage task.

Any newly activated processor cores are now available for use by uncapped logical partitions. If there are no uncapped logical partitions, you must assign the processor cores to one or more logical partitions in order to begin using the processor cores. Any newly activated memory must be assigned to one or more logical partitions to begin using the newly activated memory.

You can dynamically assign the newly activated processor cores or memory to the default partition. Alternatively, if your server is in the manufacturing default configuration, the server can start to use the newly activated processor cores or memory immediately after restarting your server operating system

Parent topic: Using Elastic Capacity on Demand


Last updated: Wed, September 27, 2017