O&M tickets

Background information

O&M tickets provide the following O&M features:

• Restart: Restarts specified pods.

• Replace: Deletes a pod directly. CafeDeployment then automatically creates a new pod to replace it.

Create an O&M ticket

1. Log on to the console.

2. In the navigation pane on the left, choose Publishing and O&M > O&M Tickets.

3. On the O&M Tickets page, click Create O&M Ticket.

4. On the Create O&M Ticket page, enter the following information and click Submit.

   • Title: Enter a title for the O&M ticket.

   • O&M Operation Type: For more information, see the following table:

     Parameter	Description
     Restart	Restarts one or more pods of an application service.
     Replace	Replaces one or more pods of an application service.
     Specified Scale-in	Scales in specific pods without being limited by pod numbering. Important The version of the cafeextcontroller cluster component must be 0.7.2 or later. Otherwise, pods are scaled in randomly.
     Specifying Stream Pulling	Removes traffic from a specified pod. Important To select the Specified Traffic Removal type, the following two conditions must be met: The version of the cafeextcontroller cluster component must be 0.7.2 or later. The version of cloud-controller-manager must be 0.8.0 or later.
     Server Load Balancer Traffic Shifting	After you select this option, you can set traffic weights for pods in a deployment unit. Important To select the Server Load Balancer Traffic Shifting type, the following three conditions must be met: The application service must be configured with a custom Server Load Balancer. For information about how to configure it, see Create an application service. The version of the cloud-controller-manager cluster component must be 1.2.1 or later. The cluster network plug-in must be terway-eni.

   • Namespace: Select a namespace from the drop-down list.

   • Application Service List: This parameter is displayed after you set O&M Operation Type to Server Load Balancer Traffic Shifting. Select one or more application services.

   • Deployment Unit Pod Weight Settings: This parameter is displayed after you set O&M Operation Type to Server Load Balancer Traffic Shifting. Configure the traffic weight for pods in the deployment unit.

     Important

     • The weight cannot be 0. If you set the weight of any deployment unit to 0, the application service cannot be published. To publish the service, you must create a new O&M ticket and set a non-zero weight.

     • If deployment units have different numbers of pods, the total traffic weight of a deployment unit is not the same as the pod weight that you set. The total weight is the pod weight multiplied by the number of replicas. For example, if deployment unit GZ00A has a weight of 50 and 1 replica, and deployment unit GZ00B has a weight of 50 and 2 replicas, the weight ratio between the deployment units is (50 × 1) : (50 × 2), which is 1:2.

   • Release Policy: This is disabled by default. If you enable it, you can set a release policy, such as grouping by deployment unit or by deployment unit percentage.

   • Pod List: Click Add, and then select the application service and pods.

5. Click Submit.

   On the O&M Tickets page, click the O&M ticket that you created to go to the O&M Ticket Details page. Click Publish All to start the release.

View O&M ticket details

On the O&M Ticket Details page, you can view the ticket's basic information and execution details.

• Basic Information: Includes the O&M ticket ID, executor, and release type.

• Application Service: Application services are published in groups. The following list describes the possible pod statuses:

  • Not Updated: The pod configuration has not been updated to the latest version.

  • Updating: The pod configuration has been updated to the latest version, but the pod is not yet ready or has been in the ready state for less than 30 seconds.

  • Update Successful: The pod configuration has been updated to the latest version and has been in the ready state for more than 30 seconds.

  • Update Failed: An error occurred when publishing or updating the pod.

Other operations

• To stop the release process for an O&M ticket, go to the O&M Ticket Details page and click Cancel.

• If an O&M ticket fails to initialize, it cannot be published. You can hover over Failure Reason to view the cause or click Re-initialize.