Managing Lifecycle Hooks

Application Scenarios

• Instances newly added to an AS group need to be initialized before they are bound to a load balancer listener. Initialization means the software is installed and configured and the instance is fully ready to accept traffic.
• To remove an instance from an AS group, it needs to be first unbound from the load balancer listener, stops accepting new requests, and finishes processing any accepted requests.
• Before instances are removed from an AS group, you may need to back up data or download logs.
• Other scenarios where custom operations need to be performed

How Lifecycle Hooks Work

After you add lifecycle hooks to an AS group, they work as follows:

• Adding an ECS instance to an AS group

  When an instance is initialized and added to an AS group, a lifecycle hook of the Instance adding type is automatically triggered. The instance enters the Wait (Adding to AS group) state, that is, the instance is suspended by the lifecycle hook. If you have configured a notification object, the system sends a message to the object. After receiving the message, you can perform custom operations, for example, installing software on the instance. The instance remains in a wait state until you complete the custom operations and perform a callback action (see Performing a Callback Action) or the timeout duration ends. After the instance moves out of a wait state, the specified default callback action will take place.

  • Continue: The instance will be added to the AS group.
  • Abandon: The instance will be deleted and a new instance will be created.

  If you have configured multiple Instance adding lifecycle hooks, all of them will be triggered when an instance is added to the AS group. If the default callback action of any lifecycle hook is Abandon, the instance will be deleted and a new instance will be created. If the default callback action of all lifecycle hooks is Continue, the instance is added to the AS group after suspension by the last lifecycle hook is complete.

• Removing an instance from an AS group

  When an instance is removed from an AS group, the instance enters the Removing from AS group state. After a lifecycle hook is triggered, the instance enters the Wait (Removing from AS group) state. The system sends messages to the configured notification object. After receiving the message, you can perform custom operations, such as uninstalling software and backing up data. The instance remains in the wait state until you finish the custom operations and perform the default callback operation or the timeout duration ends. After the instance moves out of a wait state, the specified default callback action will take place.

  • Continue: The instance is removed from the AS group.
  • Abandon: The instance is removed from the AS group.

  If you have configured multiple lifecycle hooks, and the default callback action of all lifecycle hooks is Continue, the instance will be removed from the AS group until suspension by the remaining lifecycle hooks time out. If the default callback action of any lifecycle hook is Abandon, the instance will be directly removed from the AS group.

Constraints

• You can add, modify, or delete a lifecycle hook when the AS group does not perform a scaling action.
• Up to five lifecycle hooks can be added to one AS group.

Adding a Lifecycle Hook

1. Log in to the management console.
2. Under Compute, click Auto Scaling. In the navigation pane on the left, choose Instance Scaling. Then click the AS Groups tab.
3. Click the name of the AS group to which the lifecycle hook is to be added. On the AS group details page, click the Lifecycle Hooks tab and then Add Lifecycle Hook.
4. In the displayed Add Lifecycle Hook dialog box, set the parameters listed in Table 1.

   Table 1 Parameter description

   Parameter	Description	Example Value
   Hook Name	Specifies the lifecycle hook name. The name can contain letters, digits, underscores (_), and hyphens (-), and cannot exceed 32 characters.	we12_w
   Hook Type	Specifies the lifecycle hook type. The value can be Instance adding or Instance removal. Instance adding puts an instance that is being added to an AS group to Wait (Adding to AS group) state. Instance removal puts an instance that is being removed from an AS group to Wait (Removing from AS group) state.	Instance adding
   Default Callback Action	Specifies the action that the system takes when an instance moves out of a wait state. The default callback action for an Instance adding lifecycle hook can be Continue or Abandon: Continue: If multiple lifecycle hooks are configured for the AS group, and the default callback action of all the hooks is Continue, the system will continue to add the instance to the AS group until the all lifecycle hooks time out. Abandon: If multiple lifecycle hooks are configured for the AS group, and the default callback action of one lifecycle hook is Abandon, the system will delete the instance and create another one without waiting for the remaining lifecycle hooks to time out. The default callback action for an Instance removal lifecycle hook can be Continue or Abandon: Continue: If only one lifecycle hook is configured for the AS group, the system will remove the instance from the AS group. If multiple lifecycle hooks are configured for the AS group, and the default callback actions of all the hooks are Continue, the system will continue to remove the instance from the AS group until all lifecycle hooks time out. Abandon: If multiple lifecycle hooks are configured for the AS group, and the default callback action of one lifecycle hook is Abandon, the system will continue to remove the instance from the AS group without waiting for the remaining lifecycle hooks to time out.	Continue
   Timeout Duration (s)	Specifies the amount of time for the instances to remain in a wait state. The value ranges from 300s to 86400s. The default value is 3600s. You can extend the timeout duration or perform a Continue or Abandon action before the timeout duration ends. For more information about callback actions, see Performing a Callback Action.	3600
   Notification Topic	Specifies a notification object for a lifecycle hook. For details, see "Creating a Topic" in Simple Message Notification User Guide. When an instance is suspended by the lifecycle hook, the system sends a notification to the object. This notification contains the basic instance information, your custom notification content, and the token for controlling lifecycle actions. An example notification is as follows: { "service": "AutoScaling", "tenant_id": "93075aa73f6a4fc0a3209490cc57181a", "lifecycle_hook_type": "INSTANCE_LAUNCHING", "lifecycle_hook_name": "test02", "lifecycle_action_key": "4c76c562-9688-45c6-b685-7fd732df310a", "notification_metadata": "xxxxxxxxxxxxx", "scaling_instance": { "instance_id": "89b421e4-5fa6-4733-bf40-6b07a8657256", "instance_name": "as-config-kxeg_RM6OCREY", "instance_ip": "192.168.0.202" }, "scaling_group": { "scaling_group_id": "fe376277-50a6-4e36-bdb0-685da85f1a82", "scaling_group_name": "as-group-wyz01", "scaling_config_id": "16ca8027-b6cc-45fc-af2d-5a79996f685d", "scaling_config_name": "as-config-kxeg" } }	N/A
   Notification Message	After a notification object is configured, the system sends your custom notification to the object.	N/A

5. Click OK.

   The added lifecycle hook is displayed on the Lifecycle Hooks page.

Performing a Callback Action

1. On the AS Groups page, click the name of the target AS group.
2. On the displayed page, click the Instances tab.
3. Locate the instance that has been suspended by the lifecycle hook and click Wait (Adding to AS group) or Wait (Removing from AS group) in the Lifecycle Status column.
   Figure 3 Performing a callback action
   
   

   Callback actions can only be performed on instances that have been suspended by a lifecycle hook.

4. In the displayed Added Hook dialog box, view the suspended instance and all the lifecycle hooks, and perform callback actions on lifecycle hooks.
   Figure 4 Added Hook dialog box
   

   Callback actions include:

   • Continue
   • Abandon
   • Extend timeout

   If you have performed custom operations before the timeout duration ends, select Continue or Abandon to complete the lifecycle actions. For details about Continue and Abandon, see Table 1. If you need more time for custom operations, select Extend timeout to extend the timeout duration. Then, the timeout duration will be extended by 3600 seconds each time.

Modifying a Lifecycle Hook

On the Lifecycle Hooks page, locate the target lifecycle hook and click Modify in the Operation column, see Table 1 for parameters. You can modify the parameter except Hook Name, such as Hook Type, Default Callback Action, and Timeout Duration.

Deleting a Lifecycle Hook

On the Lifecycle Hooks page, locate the target lifecycle hook and click Delete in the Operation column.