Batch Restarting FlexusL Instances

Scenarios

Cloud Operations Center (COC) provides unified operations on FlexusL instances. You can restart FlexusL instances one by one or in batches.

Precautions

• This operation can be performed only when the selected instance is running or restarted.
• If any service ticket (for example, restart service ticket) is being executed on the selected instance, the current operation cannot be performed. Wait until the existing service ticket is complete and try again.

Batch Restarting FlexusL Instances

1. Log in to COC.
2. In the navigation pane on the left, choose Resource O&M > Batch Resource Operations.
3. On the displayed page, choose the FlexusL tab and click Restart FlexusL Instances.
4. Click Add and configure the parameters on the Select Instance dialog box.

   Table 1 Parameters for selecting an instance

   Parameter	Description	Example Value
   Selection Method	Select an instance selection method. Manual Selection: Manually select an instance based on Enterprise Project, View Type, Resource Type, Region, and Target Instance.	Manual Selection
   Enterprise Project	Select an enterprise project from the drop-down list. You can choose All.	All
   View Type	Select a view type. CloudCMDB resources: Select an instance from the resource list. CloudCMDB application groups: Select an instance from the application group list.	CloudCMDB resources
   Resource Type	The default value is used and cannot be changed.	FlexusL
   Region	Select a region from the drop-down list.	CN-Hong Kong
   Target Instance	Set filter criteria in the filter box and select the filtered instances.	-

5. Configure Batch Policy and Suspension Policy.
   • Batch Policy: Select Automatic, Manual, or No Batch.
     • Automatic: The selected instances to be executed are automatically divided into multiple batches based on the preset rule.
     • Manual: You can manually create multiple batches and add instances to each batch as required.
     • No Batch: All instances to be executed are in the same batch.
   • Suspension Policy:
     • You can set the execution success rate. When the number of failed hosts reaches the number failed ones that are calculated based on the execution success rate, the service ticket status becomes abnormal and the service ticket stops being executed.
     • The success rate ranges from 0 to 100 and supports accuracy up to one decimal place.

6. Set Timeout Interval. The value ranges from 1 to 1,800 seconds.
7. Set Forcible restart. The value can be Yes or No.
8. Click OK to go to the Confirm Execution page. Click OK to start the execution.
9. Perform the following operations to check whether a service ticket execution is complete.
   • For the service tickets that are being executed:
     • If you want to pause the next batch when the current batch is executed, click Pause in the upper right corner.
     • If you want to continue the paused batch, click Continue in the upper right corner.
     • If you want to stop the service ticket that is about to be executed or is abnormal, click Forcibly End.
   • For the service tickets that are executed:
     • If some or all instance tasks in the service tickets are executed abnormally:
       • Click the Abnormal tab in the Execution Information area. Locate an abnormal batch and click Retry in the Operation column.
       • Select an abnormal batch and click Batch Retry above the instance to re-execute all abnormal tasks in the current batch.
       • Click the Abnormal tab in the Execution Information area. Locate an abnormal batch and click Cancel in the Operation column.
       • Select an abnormal batch and click Batch Cancel above the instance to cancel all abnormal tasks in the current batch.
     • If all instance tasks in the service tickets are executed successfully, no more operation is needed.