Updated on 2024-11-20 GMT+08:00

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

  1. Log in to COC.
  2. 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

  3. Enter the basic information and change configuration of the change request.

    Figure 2 Entering basic information about the change request

  4. 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.