Cloud Operations Center
Cloud Operations Center
- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Application and Resource Management
- Resource Management
-
Application Management
- Creating an Application
- Modifying an Application
- Deleting an Application
- Editing an Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating Resources with a Group
- Intelligently Associating Resources with a Group
- Transferring Resources
- Disassociating a Resource from an Application Group
- Viewing Resource Details
- Viewing Capacity Rankings
- Multi-cloud Configurations
- Cross-Account Resources
- Resource O&M
- Automated O&M
- Faults
- Change Management
- Resilience Center
- Task Management
- Basic Configurations
- Viewing Logs
- Best Practices
- API Reference
-
FAQs
- Product Consulting
- Resource Management FAQs
-
FAQs About Resource O&M
-
Patch Management FAQs
- What Can I Do If the Patch Baselines Do Not Take Effect?
- What Are the Differences Between the Installation Rule Baselines And User-defined Baselines?
- What Can I Do If Exception all mirrors were tried Is Recorded in the Patch Service Ticket Log?
- Why Can't I Select a Node?
- What Can I Do If the Compliance Report Still Reports Non-compliance for a Patch After the Patch Has Been Repaired?
- What Can I Do If the lsb_release not found Error Occurs During Patch Operations?
- Automation FAQs
- Batch Operation FAQs
- FAQs About Parameter Management
- Resource O&M Permissions and Supported Actions
-
Patch Management FAQs
- FAQs About Fault Management
- FAQs About Change Ticket Management
- Resilience Center FAQs
- Change History
- General Reference
On this page
Show all
Help Center/
Cloud Operations Center/
User Guide/
Resource O&M/
Batch Operations on Flexus L Instances/
Batch Restarting Flexus L Instances
Copied.
Batch Restarting Flexus L Instances
Scenarios
Restart Flexus L instances in batches on COC.
Precautions
Stopped instances cannot be selected.
Procedure
- Log in to COC.
- In the navigation pane on the left, choose Resource O&M > Resource Batch Operations, and click Restart FlexusL in Batch FlexusL Operations.
- On the Restart FlexusL page, click Add.
Figure 1 Selecting instances
- Select Batch Policy.
- Automatic: The selected hosts 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 target instances are in the same batch.
- Set Suspension Policy.
NOTE:
- You can set the execution success rate. When the number of failed hosts reaches the pre-set suspension threshold figure, the service ticket status becomes abnormal and the service ticket stops being executed.
- The value range is from 0 to 100 and can be set to one decimal place.
- Click Submit.
Figure 2 Restarting instances
- In the Confirm Execution dialog box, click OK.
Figure 3 Confirming the execution
- View the execution result.
Figure 4 Viewing the result
- If the execution result is abnormal, you can click the Retry button in the Operation column or the Batch Retry button above the list to re-execute the failed one or more tasks. You can also click the Cancel button in the Operation column or Batch Cancel button above the list to skip one or more abnormal tasks.
Figure 5 Canceling or retrying batch tasks
Parent topic: Batch Operations on Flexus L Instances
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot