Help Center/ Cloud Application Engine/ User Guide/ System Settings/ Configuring Start/Stop Policies
Updated on 2024-05-25 GMT+08:00

Configuring Start/Stop Policies

  • You can configure up to 20 start/stop policies.
  • Do not start or stop a component when it is being scaled. Disable the AS policy before the operation.
  • When a component is being started, restarted, or stopped, AS policies cannot be added or enabled for the component.

Adding a Start/Stop Policy

  1. Log in to CAE.
  2. Choose System Settings.
  3. Click Edit in the Start/Stop Policy Configuration module.
  4. Click Add Policy. Configure the start/stop policy by referring to the following table.

    Parameter

    Description

    Policy Name

    Enter a policy name.

    The policy name must be unique.

    Effected Components

    • All in the environment: The start/stop policy takes effect for all components in the environment.
    • All in the application: The start/stop policy takes effect for all components in the selected application.
      NOTE:
      • Start/stop policies do not take effect for components in the Not deployed state.
      • For components in the Deploying state, start/stop policies will fail to be executed. For details about the failure cause, see Viewing a Start/Stop Policy.
      • All in the environment and All in the application policies also take effect for newly added components.
    • Some: The start/stop policy takes effect for the selected components.
      NOTE:

      Components in the Not deployed state cannot be selected.

    Status

    • Enable: The start/stop policy is enabled and will be triggered at the specified time.
    • Disabled: The start/stop policy is disabled.

    Policy

    • Start: After the policy is configured, components will be started in batches. Components that have been started are not affected.
    • Stop: After the policy is configured, components will be stopped in batches. Components that have been stopped are not affected.

    Trigger

    • Once: The policy is triggered only once. After the policy is triggered, Status will be disabled.
    • Periodically: The policy is executed periodically. Currently, the policy can be executed by week or day.

    Triggered

    • Select a time when Trigger is set to Once.
    • When Trigger is set to Periodically:

      Every week: Select a date and time for triggering the policy every week. For example, 17:30 on every Monday.

      Every day: Select a time for triggering the policy every day. For example, 01:00 every day.

      NOTE:

      Triggered time must be at least two minutes after the current time.

  5. Click OK.

Editing a Start/Stop Policy

  1. Log in to CAE.
  2. Choose System Settings.
  3. Click Edit in the Start/Stop Policy Configuration module.
  4. Select the target policy and click Edit in the Operation column. Reconfigure the policy by referring the following table.

    Parameter

    Description

    Effected Components

    • All in the environment: The start/stop policy takes effect for all components in the environment.
    • All in the application: The start/stop policy takes effect for all components in the selected application.
      NOTE:
      • Start/stop policies do not take effect for components in the Not deployed state.
      • For components in the Deploying state, start/stop policies will fail to be executed. For details about the failure cause, see Viewing a Start/Stop Policy.
    • Some: The start/stop policy takes effect for the selected components.
      NOTE:

      Components in the Not deployed state cannot be selected.

    Status

    • Enable: The start/stop policy is enabled and will be triggered at the specified time.
    • Disabled: The start/stop policy is disabled.

    Policy

    • Start: After the policy is configured, components will be started in batches.
    • Stop: After the policy is configured, components will be stopped in batches.

    Trigger

    • Once: The policy is triggered only once. After the policy is triggered, Status will be disabled.
    • Periodically: The policy is executed periodically. Currently, the policy can be executed by week or day.

    Triggered

    • Select a time when Trigger is set to Once.
    • When Trigger is set to Periodically:

      Every week: Select a date and time for triggering the policy every week. For example, 17:30 on every Monday.

      Every day: Select a time for triggering the policy every day. For example, 01:00 every day.

      NOTE:

      Triggered time must be at least two minutes after the current time.

  5. Click OK.

Deleting a Start/Stop Policy

  1. Log in to CAE.
  2. Choose System Settings.
  3. Click Edit in the Start/Stop Policy Configuration module.
  4. Select the target policy and click Delete in the Operation column.
  5. If Deleted is displayed, the policy is deleted.

Searching for a Start/Stop Policy

  1. Log in to CAE.
  2. Choose System Settings.
  3. Click Edit in the Start/Stop Policy Configuration module.
  4. In the search box in the upper right corner, enter a policy name (fuzzy search is supported).
  5. Click to filter the start/stop policy.

Viewing a Start/Stop Policy

Policies in the Not executed and Executing states cannot be viewed.

  1. Log in to CAE.
  2. Choose System Settings.
  3. Click Edit in the Start/Stop Policy Configuration module.
  4. Select the target policy and click Execution Details in the Operation column.
  5. View the execution status of the start/stop policy.