Implementing Changes

Procedure Description

Figure 1 Change Process

1. Creating a review configuration: You can preset review processes and reviewers for different types and levels of changes, and specify review rules (such as the review level and conditions for review), laying a foundation for change review.
2. Creating a Change Ticket: You can record the basic information, configuration, plan, and implementation solution (job/guide) of the change, and submit a change application to start the subsequent process.
3. Reviewing a Change Ticket: The reviewer reviews the necessity, feasibility, and risks of the change, and approves or rejects the change to control the change execution threshold.
4. Handling and Closing a Change Ticket: The change is implemented at the planned time based on the approved solution. After the change is completed, the result (success or failure) is recorded and the verification report is uploaded to implement the entire change process.

Prerequisites

• You have created an application by referring to Application Management.
• You have created a reviewer shift by referring to Shift Management.

Precautions

Confirm the content of the change ticket and apply for the change based on the actual change requirement.

Creating a Review Configuration

To create a change ticket, you need to configure the review process and reviewer from the change type and change level dimensions based on service requirements.

1. Log in to COC.
2. In the navigation pane, choose Change Ticket Management > Change Configurations.
3. Click Create Review Configurations.
4. Set parameters for creating a review configuration.

   Table 1 Parameters for creating a review configuration task

   Parameter	Description
   Change Type	The options are Regular and Urgent. Only one change type can be configured each time.
   Level	The options are A, B, C, and D (A > B > C > D). You can select multiple change levels at a time.
   Review Configurations	Select a shift scenario and corresponding roles from the drop-down lists. For details about how to configure a shift, see Shift Schedule Management. A shift role becomes active only after a reviewer is assigned. Without a reviewer, the change ticket cannot be submitted. Review Rule: The options are One-member Approval and All-member Approval. You can add up to five levels of reviews.

5. Click OK.

   After the review configuration is complete, you can view it in the change review configuration list. If the change configuration in Creating a Change Ticket is consistent with the review rule, a change can be implemented and verified only after being approved by the corresponding reviewer.

Creating a Change Ticket

1. Log in to COC.
2. In the navigation pane, choose Change Ticket Management > Change Center.
3. Click Create Change Ticket.
4. Set parameters in the Basic Information area.
   • Title: Specify the title of the change ticket.
   • Description: Describe the change. Enter a maximum of 4,096 characters.

5. Set parameters in the Change Configuration area.

   Table 2 Parameters for change configurations

   Parameter	Description	Example Value
   Change Type	The options are Regular and Urgent. Regular changes are non-emergency changes that can be requested, evaluated, reviewed, sorted, planned, tested, implemented, and backtracked using regular procedures. Urgent changes are unplanned changes that are requested because the production environment is unavailable or the changes cannot be evaluated and approved through the normal process, or to meet urgent service requirements.	Regular
   Level	The options are A, B, C, and D (A > B > C > D). For details, see Change Levels.	A
   Scenario	Select a change scenario.	API change
   Application	Select a change application, a sub-application, a group, and a component from the drop-down lists as required. Multiple sub-applications, groups, and components can be selected.	-
   Region	Select a region. Multiple options can be selected.	CN-Hong Kong
   Selected Change Scope	Configure the change region corresponding to the sub-application, group, and component.	-

6. Configure parameters in the Change Plan area.

   Set the change plan for the selected regions.

   Table 3 Change plan parameters

   Parameter	Description
   Planned Change Time	Select a time range for the plan change.
   Change Implementer	Select a change implementation user. Multiple users can be selected.
   Change Coordinator	(Optional) Select a user as the change cooperation. Multiple users can be selected.

7. Set Task Type. The value can be Jobs or Change guidelines.
   • If Task Type is set to Jobs, configure other parameters by referring to Table 4.

     Table 4 Job parameters

     Parameter	Description
     Task Type	Select the job you want to execute.
     Region	Select a region.
     Target Instance Mode	This parameter is required for some jobs. You can select the execution methods for job steps and target instances. Consistent for all steps: All tasks are executed on the selected instance using the same batch policy. Unique for each step: Tasks in one step are executed on the selected instance. Each step uses a batch policy.
     Job Execution Procedure	This parameter is required for some jobs. You can specify job details. Click a job name. The drawer for modifying parameters is displayed on the right. Set Input, Output, and Troubleshooting.
     Global Parameters	This parameter is required for some jobs. You can set global parameters.
     Target Instance	This parameter is required for some jobs. Click Add Instance and configure parameters on the displayed page. For details about how to set the parameters, see Table 5.
     Batch Policy	This parameter is required for some jobs. You can select Automatic, Manual, or No Batch. Automatic: The selected instances you want to execute 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.

     Table 5 Parameters for selecting an instance

     Parameter	Description	Example Value
     Selection Method	Select an instance selection method. Manual Selection: Manually select one or more instances based on settings of Enterprise Project, View Type, Resource Type, Region, and Target Instance.	Manual Selection
     Enterprise Project	Select an enterprise project. You can select 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	Select ECS or BMS.	ECS
     Region	Select a region.	CN-Hong Kong
     Target Instance	Set filter criteria in the filter box and select the filtered instances.	-

   • If Task Type is set to Change guidelines, set required parameters by referring to Table 6.

     Table 6 Parameter description for the change task that is based on change guidelines

     Parameter	Description
     Add File	Click Add File to upload the files related to the change guidelines. A maximum of 10 files can be uploaded. The supported file types are JPG, PNG, DOCX, TXT, and PDF. The size of a single file cannot exceed 10 MB.

8. Click Submit.
9. In the displayed dialog box, click OK.

   The created change ticket can be viewed on the Change Ticket Management > Change Center > Created by Me page.

Reviewing a Change Ticket

After a change ticket is created, you need to perform the following operations to approve or reject the change ticket.

1. Log in to COC.
2. In the navigation pane, choose Change Ticket Management > Change Center.
3. On the Pending tab page, locate the change ticket you need to review and click Deal in the Operation column.
4. Click Review.
5. Set Review Comment.
   • Approve or Not: The options are Approve and Reject.
   • Review Comment: Enter review comments.

6. Click OK.

   After the review is complete, the change owner can view the change ticket on the Pending tab page of the Change Ticket Management > Change Center page and implement and verify the change on the live network.

Handling and Closing a Change Ticket

After a change ticket is approved, implement the change within the specified time window according to the change solution. After the change is implemented, fill in the change result and the verification report.

1. Log in to COC.
2. In the navigation pane, choose Change Ticket Management > Change Center.
3. On the Pending tab page, locate the change ticket you need to handle and click Deal in the Operation column.
4. Execute changes based on the change solution type.
   • If the change solution type is set to Jobs, click Execute Job.
   • If the change solution type is set to Change guidelines, implement the change according to the steps mentioned in the change guide.

5. Click Start Change and wait until the change is complete.
6. After the change is complete, click End.
7. Enter the change result.

   Table 7 Parameters in the result of a successful change

   Parameter	Description
   Change Result	Select Success.
   Change Verification	The options are Verification within the change time window and The change time window cannot be verified.
   Verification Report or Verification Description	Click Add File to upload the verification report or verification description file. A maximum of 10 files can be uploaded. The supported file types are JPG, PNG, DOCX, TXT, and PDF. The size of a single file cannot exceed 10 MB.
   Description	(Optional) Description of the change result. Enter 0 to 256 characters.

   Table 8 Parameters in the result of a failed change

   Parameter	Description
   Change Result	Select Failed. This parameter covers situations like change rollbacks, service interruptions due to changes, and incidents triggered by changes.
   Whether to monitor discovery	The options are Yes and No.
   Rollback Succeeded	The options are Rollback succeeded and Rollback failed.
   Rollback Time	Set the rollback time.
   Change Failure Type	Select a failure type. Dependent service issues Change quality issues Change tool issues Change implementation issues Change solution issues Other issues
   Failure Cause Description	Describe the change failure cause. Enter 0 to 256 characters.
   Verification Report or Verification Description	Click Add File to upload the verification report or verification description file. A maximum of 10 files can be uploaded. The supported file types are JPG, PNG, DOCX, TXT, and PDF. The size of a single file cannot exceed 10 MB.

8. Click OK to close the change ticket. The change ends.

More Operations

After creating a review configuration, you can perform the following operations:

Helpful Links

• How Do I Distinguish Regular Changes from Emergency Changes?
• On COC, you can call APIs to create or update change tickets, upload or download attachments, and delete change tickets. For details, see Change Ticket Management.