- 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
Copied.
Creating a Change Ticket
Scenarios
Create a change ticket in Cloud Operations Center.
Prerequisites
1. You have created an application by referring to Application Management.
2. You have created a reviewer shift by referring to Overview.
Precautions
Confirm the content of change ticket and apply for the change based on the actual change requirement.
Procedure
- Log in to COC.
- In the navigation pane on the left, choose Change Ticket Management > Change Center. Click the Pending tab, and click Create Change Ticket.
Figure 1 Creating a change ticket
- Enter the basic information and change configuration of the change request.
Figure 2 Entering basic information about the change request
- Set the change task type. You can select Jobs and Change Guide. For details about job execution, see Automated O&M.
Figure 3 Setting the change task type
1. Change Type
Regular changes are non-emergency changes that can be requested, evaluated, approved, sorted, planned, tested, implemented, and reviewed using normal procedures.
Emergency changes are unplanned changes that are proposed because the production environment is unavailable or the changes cannot be evaluated and approved in time through the normal process, or to meet urgent service requirements.
2. Class: A > B > C > D
3. Scenario: Customize configurations based on service requirements.
4. Application: Select an application first and then the specific application resources.
5. Region: The change scope is defined by the change area and change application.
6. Change Plan: Generated by region.
The operator and coordinator need to be configured by region.
The planned change time window needs to be configured by region. (Note: The allowed change time window is restricted by the change level and change type.)
7. Task Type: Select Jobs or Change Guide.
After the configuration, click Submit.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot