Billing when changing a running On/Off Capacity on Demand request

Ensure that you understand the implications to billing before you decide to change a running On/Off Capacity on Demand (CoD) request.

When you issue a change request, the days in the running request are not preserved; however, the time in the current resource day is carried forward from the running request. It is important to understand that the resource days that remain in a request are decremented at the start of each day. Therefore, the number of resource days billed is incremented at the start of each day.

If the change request decreases the amount of resources in the running request, the remainder of the current resource day is forfeited for each of the resources that are being canceled. No credit is given for any partial resource days that are forfeited. If the change request increases the amount of resources in the running request, a charge for the additional resources for the time that remains in the current resource day is immediately applied. That charge is calculated as additional resources multiplied by the quantity (time that remains in the current resource day rounded up to the whole hour and divided by 24). The result is rounded up to whole resource days. The usual charge for any requested days in the change request applies.

The number of resource days in the On/Off CoD enablement is calculated separately from the number of resource days that are billed. When an On/Off CoD request is started, the number of enabled resource days is reduced by the number of requested resource days (number of requested resources multiplied by the number of requested days). When a running On/Off CoD request is changed, the number of enabled resource days is increased by the number of remaining resource days in the running request, then reduced by the number of requested resource days in the change request. If the change request increases the number of resources, the number of enabled resource days is also reduced by the number of resource days that are charged for the additional resources for the time in the current resource day.

If you decide, within the same day, to again activate the On/Off CoD processors, such as during a test period, the implications to billing are slightly different. The 24-hour test period starts when the first On/Off CoD request is made. During the 24-hour test period that your server is powered on, a record is kept of the maximum number of On/Off CoD processors or memory requested when you make On/Off CoD activation or change requests. Therefore, as the testing reactivation occurs, you can start and stop, or change, On/Off CoD requests repeatedly. Any subsequent requests during the same 24-hour period for the same or fewer resources are not charged. Requests that are made for more resources result in a pro-rated charge for the excess resources. This new, higher level of resources becomes the maximum resource amount for the 24-hour period, and subsequent requests during the same 24-hour period are not charged for resources up to this new maximum amount. For information about testing your On/Off CoD activations, see Testing your On/Off Capacity on demand activations.