Auto-Scaling Scheduler Function

With this function you can control the execution of scale out by specifying the date and time for execution. You can use the schedule function to automate scaling out for a predictable increase of workload, such as the busy season of your business.

This function provides the method to execute the REST API at the specified time.

Tip: You can realize the operation of an increased number of virtual servers in the busy season by describing the REST API to control the scaling policy in order to increase the number.

Registering a Schedule

Set the following items to register a schedule.

Table 1. List of Settings for a Schedule
Item Description Required
Schedule name

From 1 to 64 alphanumeric characters can be used.

Important: The name must be unique among all projects in the same region.
HTTP methods Specify the HTTP methods for the REST API that is to be executed. Only the POST method can be specified Yes
URL Specify the URL for the signal to be the target of the schedule. Yes
Date and time to execute Specify the date and time at which to execute the REST API Yes
Project ID Specify ID of the project in which the schedule is to be executed Yes

The format for the URL for the signal is as follows:

http://<orchestration API end point>/v1/<project ID>/stacks/<stack name>/<stack ID>/resources/<scaling policy name>/signal

Specify the execution date and time in the five fields of the cron-command-compliant format that is shown below. (Fields are separated by single-byte spaces)

minute hour dom month dow
Table 2. Description of Each Field and Values That Can Be Specified
Field Values That Can Be Specified
Minute From 0 to 59, * specifies every minute
Hour From 0 to 23, * specifies every hour
Day of Month From 1 to 31, * specifies every day
Month From 1 to 12, or from jan to dec, * specifies every month
Day of Week From 0 to 7 (0 and 7 specify Sunday) or from sun to sat, * specifies all days

Confirm that a valid trust token exists, on which the user to whom you delegate the execution of schedules, the trusted user (orchestration user), the project ID, and the role (System Owner role) match. Check the trust token by using the following API, which is explained in the section about IDs and access management in API Reference Manual.

  1. Check the trust token (list)

    Confirm that a trust token that meets the following conditions exists.

    Table 3. Conditions for Confirming Existence of Trust Token
    Item Value
    trustor_user_id uuid of the user to whom you delegate the task
    expires_at null
    trustee_user_id 1f708e1376784e529a7b09eb5ff1a5fc
    project_id uuid of the project where the stack exists
  2. Confirm the role on the trust token

    Table 4. Conditions for Confirming Role on Trust Token
    Item Value
    trust_id uuid of the trust token that meets the conditions above
    role_id 0739580a550d4a0f9c78f45a9f038c05

Deleting a Schedule

You can delete a schedule that is already registered.