Redeploying a Component in Dark Launch Mode

Introduction to Dark Launch

In dark launch mode, a certain proportion of instances are upgraded, and traffic is directed to the new version to verify whether functions of the new version are normal. Then, the remaining instances will be upgraded in rolling mode. Dark launch ensures stability of the entire system. During initial dark launch, problems can be detected and fixed.

Prerequisites

• You have upgraded a component. For details, see Upgrading a Single Component or Upgrading Components in Batches.
• The component is a stateless component deployed based on a container. If the component technology stack is Docker, multi-container deployment must be disabled.
• The component version configuration that has been rolled back by referring to Rolling Back a Component cannot be used as a template to redeploy the component.

Redeploying a Component in Dark Launch Mode

1. Log in to ServiceStage.
2. Use either of the following methods to go to the Deployment Records page.
   • On the Application Management page, click the application to which the component belongs, click the target component in Component List, and choose Deployment Records in the left navigation pane.
   • On the Component Management page, click the target component and choose Deployment Records in the left navigation pane.

3. In the Deployment Records list, select the deployment record of the historical version to be used as the configuration template.
4. Click Redeploy in the upper right corner of the page. The Redeploy dialog box is displayed.
5. Select Dark Launch for Deployment Type and click OK.
6. Configure the component version by referring to the following table. Parameters marked with an asterisk (*) are mandatory.

   Parameter	Description
   Stack	Select a component technology stack and version. For details, see Technology Stack.
   *Software Package/Image	The value is fixed to the component source selected during component creation and deployment. If you select Source code repository, create authorization by referring to Creating Repository Authorization and set the code source. If you select a software package or image package, the option is fixed to the software package type (JAR, WAR, or ZIP) or image package type selected during component creation and deployment. It is determined by the selected technology stack type. For details, see Table 1.
   *Upload Method	If the component source is software package or image package, select an uploaded software package or image package. For details about the upload method, see Component Source. If the component source is software package and Custom file address is selected, perform the following operations: Enter the custom HTTP/HTTPS file download address of the software package. Determine whether to enable authentication. If authentication is disabled, any user can download the software package in the custom file address by default. Click to enable authentication. Only authenticated users can download the software package in the custom file address. Authentication mode can be User name and password authentication or User-defined Header Authentication. The authentication mode and the corresponding authentication parameters are determined by the authentication mode supported by the server where the custom file directory is located. NOTE: If you select an image package: You can customize the container name. The name contains 1 to 63 characters, including lowercase letters, digits, and hyphens (-), and must start with a lowercase letter and end with a lowercase letter or digit. Click in the upper right corner of the selected image package to change the image package source.
   Image Access Credential	This parameter is available for container-deployed components. You can select up to 16 image access credentials. Click Create Secret to create an image access credential. Secret Type must be kubernetes.io/dockerconfigjson. For details, see Creating a Secret.
   *Command	This parameter is mandatory when the component source is Source code repository and the selected technology stack type is Java, Tomcat, Node.js, Python, or PHP. Default command or script: preferentially executes build.sh in the root directory. If build.sh does not exist, the code will be compiled using the common method of the selected language. Example: mvn clean package for Java. Custom command: Commands are customized using the selected language. Alternatively, the default command or script is used after build.sh is modified. NOTICE: If Custom command is selected, exercise caution when inputting sensitive information in the echo, cat, or debug command, or encrypt sensitive information to avoid information leakage. To run the compilation command in the project subdirectory, you need to go to the project subdirectory and then run other script commands. Example: cd ./weather/ mvn clean package
   *Dockerfile Address	This parameter is mandatory when the component source is Source code repository and the selected technology stack type is Java, Tomcat, Node.js, Python, or PHP. Dockerfile Address is the directory where the Dockerfile is located relative to the root directory (./) of the project. The Dockerfile is used to build an image. If Dockerfile Address is not specified, the system searches for the Dockerfile in the root directory of the project by default. If the Dockerfile does not exist in the root directory, the system automatically generates the Dockerfile based on the selected operating environment.
   *Component Version	Component version number, which can be automatically generated or customized. Automatically-generated: Click Generate. By default, the version number is the time when you click Generate. The format is yyyy.mmdd.hhmms, where s is the ones place of the second in the timestamp. For example, if the timestamp is 2022.0803.104321, the version number is 2022.0803.10431. Customized: Enter a value in the format of A.B.C or A.B.C.D. A, B, C, and D are natural numbers. For example, 1.0.0 or 1.0.0.0. NOTICE: The customized version number must be unique and cannot be the same as any historical version number of the component. Otherwise, the current deployment record will overwrite the historical deployment record of the same version.
   *Container Name	This parameter is mandatory when the technology stack is not Docker. The name contains 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.
   Resources	The value is fixed to the configuration of the selected historical version and cannot be changed.
   JVM Parameters	The value is fixed to the configuration of the selected historical version and cannot be changed. This parameter is available when the technology stack type is Java or Tomcat. It configures the memory size during Java code running.
   Tomcat	The value is fixed to the configuration of the selected historical version and cannot be changed. This parameter is available when the technology stack type is Tomcat. It configures parameters such as the request path and port number of Tomcat.
   Container Settings	The value is fixed to the configuration of the selected historical version and cannot be changed.
   Application Settings	The value is fixed to the configuration of the selected historical version and cannot be changed.
   Advanced Settings	The value is fixed to the configuration of the selected historical version and cannot be changed.
   *Deployment Architecture	Click Select and select an instance deployment architecture for dark lunch. Click OK. NOTICE: You must choose the correct architecture. Otherwise, dark launch will fail and services will be affected.
   *Dark Launch Policy	Select a dark lunch policy. Traffic ratio-based: Flexibly and dynamically adjust the traffic ratio of different versions. Content-based: Control the version to which the request is sent according to the request. NOTE: ELB dark launch supports only the Traffic ratio-based policies.
   *Traffic Ratio	When Dark Launch Policy is set to Traffic ratio-based, set the traffic ratio. Traffic Ratio: percentage of traffic directed to the new version. Current Traffic Ratio: percentage of traffic directed to the current version.
   *Takes effect	When Dark Launch Policy is set to Content-based, set the effective mode of the dark launch policy. With single criterion: The dark launch policy takes effect when any matching rule is met. With full criteria: The dark launch policy takes effect when all matching rules are met. NOTE: For ELB dark launch, only With full criteria is supported.
   *Matching Rule	When Dark Launch Policy is set to Content-based, set the matching rule for the dark launch policy to take effect. Click Add Matching Condition. Set Matching Type. Currently, only Request header is supported. Set Parameter Name, that is, the key corresponding to Matching Type. Set Condition Type, that is, the matching rule that Condition Value meets. Equal: The value corresponding to Matching Type is equal to the configured Condition Value. Matching: Condition Value supports PERL-compatible regular expressions. It is supported by only microservice dark launch. Enumerated: Multiple Condition Value are separated by commas (,). Set Condition Value, that is, the value corresponding to Matching Type.
   *Instances Deployed for Dark Launch	Select a mode for adding an instance during dark launch. Blue-green Add new version instances with the same number as the old version instances, and switch traffic to the new version based on dark launch rules. After verification based on the dark launch rules, switch all traffic to the new version and delete the old version. Scenarios: lossless service capacity, fast rollback, and when resources are needed in the cluster. This mode requires one or more component instances. Canary (increase, then decrease) Add new version instances with the specified number, and switch traffic to the new version based on dark launch rules. After verification based on the dark launch rules, delete some old instances, add corresponding new instances, and switch traffic. Repeat this process until all traffic is switched to the new instances and old instances are deleted. Scenarios: lossless service capacity, slow rollback, and when resources are needed in the cluster. This mode requires two or more component instances. Canary (decrease, then increase) Delete some old instances and add corresponding new instances, and switch traffic to the new version based on dark launch rules. After verification based on the dark launch rules, delete some old instances, add corresponding new instances, and switch traffic. Repeat this process until all traffic is switched to the new instances and old instances are deleted. Scenarios: lossy service capacity and slow rollback. This mode requires two or more component instances. NOTE: To change the number of component instances to meet the requirements, see Configuring a Manual Scaling Policy.
   *First Batch of Dark Launch Instances	Set this parameter when Instances Deployed for Dark Launch is set to Canary (increase, then decrease) or Canary (decrease, then increase). The value range is [1, Total number of instances – 1]. Total number of instances refers to the number of running instances of the component. For example, if there are 6 component instances and First Batch of Dark Launch Instances is set to 1, 1 instance will be upgraded in the first batch. The remaining 5 instances will be upgraded according to Deployment Batch with Remaining Instances.
   *Deployment Batch with Remaining Instances	Set this parameter when Instances Deployed for Dark Launch is set to Canary (increase, then decrease) or Canary (decrease, then increase). That is, the number of batches whose remaining instances will be upgraded. For example, if there are 6 component instances, First Batch of Dark Launch Instances is set to 1, and Deployment Batch with Remaining Instances is set to 3, there are 5 instances remaining to be deployed in 3 batches, and these 5 instances will be upgraded in the sequence 2:2:1

7. Click Upgrade.
   • Wait until the component status changes from Upgrading/Rolling back the component to Running, indicating that the component has been redeployed.
   • On the Deployment Records page, view the deployment logs.

     If "Querying the Status of a Workload Instance" is displayed, click View Event to view details.