Deployment, operation and maintenance of cloud application delivery platform appstack

1、 Deploy

• The application layout has been completed. SeeApplication Layout。
• There is at least one environment, and the environment has been associated with resources. See for detailsEnvironmental management。

• Application environment, find the target environment card in the environment list and clickDeploy now； You can also enter the target environment details page and click in the operation area in the upper right cornerdeployButton.
• Application environment, click above the environment listNew deploymentMultiple environments can be deployed simultaneously to realize batch deployment.

• Work order name: list name, filled in by default: ${second timestamp} – deployment, which can be modified as needed.
• Version number: deployment version number, automatically generated: ${second timestamp} – ${three digit milliseconds}, which cannot be modified.
• Environment optionsClick: to display the deployment components defined in the application orchestration of this environmentView yamlYou can view the specific content of each component. The workload type component can adjust the deployment parameters as needed:
• products: Mirror address.
• CPU specification: container CPU request and limit, unit “core”, support input floating point number.
• Memory specification: container memory request core limit, in MB. Floating point numbers are supported.
• Deployment strategy: environment deployment strategy, which supports batch release and rolling upgrade.
• Number of target instances: the number of workload replicas. Positive integers are supported.
• Batch number: when selecting the batch publishing deployment policy, you need to specify the number of batches and the number of releases per batch.
• Pause strategy: when selecting the batch publish deployment policy, you need to specify a pause policy. Three strategies are supported: no pause, first pause and each batch pause.
• explain: job description.

Special instructions:The “product”, “CPU specification”, “memory specification” and “target instance number” in the deployment document parameters are controlled by the application orchestration. The control principle is: if the corresponding preset placeholder is used in the application orchestration and the preset placeholder turns on the “modify during deployment” switch, the form items corresponding to the deployment phase can be dynamically modified as needed within the scope of the orchestration verification rules. See applying orchestration – using placeholders and variables for more information.

• The environment list area on the left displays the environment of this work order deployment. Click the card to switch the environment.
• The middle pipeline area displays the deployment pipeline of the current environment, and the pipeline node is determined by the current deployment content.
• The node details area on the left displays the basic information and deployment progress of the current node resources.

• In the work order details page – node area on the right, you can view the basic information and deployment progress of each resource. Specifically for resources of workload type, clickDeployment progressYou can view the details of an instance by using the instance block under:essential information、Key events、Container logWait.
• In addition, you can view the status of each resource through the environment card progress environment details page. For details, see environment management.

2、 Expansion and contraction

• The environment is deployed at least once. Seedeploy。

• Application environment, enter the target environment details page, and click in the operation area in the upper right cornerExpansion and contractionButton.

• Work order name: default population: ${second timestamp} – deployment, which can be modified as needed.
• Expansion and contraction options: to display the deployment information of the workload components of the environment to be expanded, fill in the following parameters:
• Deployment strategy: automatically select the last deployment policy.
• Number of target instances: enter the number of target instances to provide services according to the actual scenario.
• Batch number: according to the instance data to be expanded / reduced, enter the appropriate batch number and the expansion / reduction quantity of each batch.
• Pause strategy: automatically selects the last pause policy.
• explain: enter the expansion description.

• The environment list area on the left shows the environment of this work order expansion and contraction.
• The middle pipeline area shows the expansion and contraction pipeline of the current environment workload.
• The node details area on the left displays the basic information and expansion progress of the current node.

3、 Rollback

• The environment to be rolled back has at least one successful historical deployment version.

• Work order Name: default filling: ${second timestamp} – rollback, which can be modified as needed.
• Rollback version: automatically populates the selected deployment version.
• Environment Option: displays the environment under the target rollback version,products、Deployment strategy、Number of target instancesBoth use the parameters of rollback version. You can specify the batch number of rollback and pause policy according to the actual situation.
• Description: enter a rollback description.

• The environment list area on the left shows the environment of this work order rollback. Click the card to switch the environment.
• The middle pipeline area shows the rollback pipeline of the current environment.
• The node details area on the left displays the basic information and rollback progress of the current node.