Deployment, operation and maintenance of cloud application delivery platform appstack

Time:2022-1-17
Cloud application delivery platform appstackIt is a developer friendly cloud native application delivery platform with application as the core. It provides one-stop capabilities such as application orchestration, environment management, deployment and operation and maintenance, resource management and application release, helps enterprises establish an overall solution for continuous application delivery, accelerates the transformation of Enterprise Cloud native and Devops, and improves team R & D efficiency.
After creating a new environment, you can deploy, expand, roll back and other operation and maintenance operations on the environment as needed.
 

1、 Deploy

Deployment is usually used to update environment services when there are changes in application artifacts or configurations.
 
prerequisite
  • 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
Operation steps
 
1. Function entrance
  • 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.
2. Fill in deployment doc parameters
  • 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.
Deployment, operation and maintenance of cloud application delivery platform appstack
 
Add multi environment batch deployment:
 
In addition, you can clickAdd environmentInitiate multi environment batch deployment. Taking multiple sets of production environments in different places as an example, one product version can be deployed to all production environments at one time, which is convenient for subsequent one-time rollback.
 
openThe same product is used in all environmentsThe switch can fill in multiple environmental products at one time to ensure that the same products are used in multiple environments. Specific environment deployment parameters can be modified as needed on each environment option card, which is the same as the above deployment document parameters.
 
Deployment, operation and maintenance of cloud application delivery platform appstack
 
3. Submit deployment
 
clickSubmit, generate the deployment work order and jump to the work order details page.
 
4. Observe the deployment process
 
Observe work order execution
  • 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.

Deployment, operation and maintenance of cloud application delivery platform appstack

Pause / resume
 
The operation area above the intermediate pipeline can manually intervene the deployment progress of the current environment. Can clicksuspendCurrent task, which can be used to pause the task and observe the service status under abnormal conditions. For tasks that have been manually suspended or suspended under the control of suspension policy, clickcontinuePerform the task.
 
termination
 
During deployment, you can manuallyterminationCurrent deployment task, optionalSet as successfulorSet as failed。 It can be used in some special scenarios that do not require further deployment: for example, SRE has deployed application services to the target version through manual operation and maintenance cluster, and there is no need to continue processing the work order.
 
RollBACK
 
During deployment, you can clickRollBACK , roll back the current environment to the last deployment state. clickRollBACK After, the current deployment task will be cancelled and a new rollback task will be generated. The rollback task will be redeployed using the latest deployment baseline of the environment. It can be used in scenarios where the current deployment version does not meet expectations and the environment needs to be quickly restored to the last available state.
 
View resource details
  • 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 informationKey eventsContainer logWait.
  • In addition, you can view the status of each resource through the environment card progress environment details page. For details, see environment management.
 
Deployment, operation and maintenance of cloud application delivery platform appstack
 

2、 Expansion and contraction

 
Environment scaling is usually used to dynamically adjust the number of service instances provided by the environment when the environment workload is too high or too low.
 
prerequisite
  • The environment is deployed at least once. Seedeploy
Operation steps
 
1. Function entrance
  • Application environment, enter the target environment details page, and click in the operation area in the upper right cornerExpansion and contractionButton.
2. Fill in the expansion and contraction sheet parameters
  • 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.
 
Deployment, operation and maintenance of cloud application delivery platform appstack
 
3. Submit expansion and contraction
 
clickSubmit, generate a volume expansion work order and jump to the work order details page.
 
4. Observe the expansion and contraction process
 
Observe work order execution
  • 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.
 
Deployment, operation and maintenance of cloud application delivery platform appstack
 
Pause / resume
 
In the middle pipeline area, you can manually intervene the expansion and contraction progress of the current environment. You can clicksuspendCurrent task, which can be used to pause the task and observe the service status under abnormal conditions. For tasks that have been manually suspended or suspended under the control of suspension policy, clickcontinuePerform the task.
 
termination
 
During work order execution, you can manuallyterminationCurrent task, optionalSet as successfulOr setFor failure。 It can be used in some special scenarios that do not require further deployment: for example, SRE has deployed application services to the target version through manual operation and maintenance cluster, and there is no need to continue processing the work order.
 
View resource details:See the deployment order above.
 

3、 Rollback

 
Rollback can quickly restore multiple environments to the target version at one time. It is applicable to the scenario where the new version does not meet expectations and needs to be rolled back to the latest available version. Rollback is equivalent to a redeployment using the historical version. Please be careful!
 
prerequisite
  • The environment to be rolled back has at least one successful historical deployment version.
Operation steps
 
1. Function entrance
 
Application – version, find the target rollback version in the version list, and clickRollBACK Submit the rollback work order.2. Fill in rollback doc parameters
  • 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,productsDeployment strategyNumber 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.
 
Deployment, operation and maintenance of cloud application delivery platform appstack
 
3. Commit rollback
 
clickSubmit, generate a rollback work order and jump to the work order details page.
 
4. Observe the rollback process
 
Observe work order execution
  • 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.
 
Deployment, operation and maintenance of cloud application delivery platform appstack
 
Pause / resume
 
In the middle pipeline area, you can manually intervene the rollback progress of the current environment. You can clicksuspendCurrent task, which can be used to pause the task and observe the service status under abnormal conditions. For tasks that have been manually suspended or suspended under the control of suspension policy, clickcontinuePerform the task.
 
termination
 
During work order execution, you can manuallyterminationCurrent task, optionalSet as successfulorSet as failed。 It can be used in some special scenarios that do not require further deployment: for example, SRE has deployed application services to the target version through manual operation and maintenance cluster, and there is no need to continue processing the work order.
 
View resource details:See the deployment order above.
 
Cloud application delivery platform appstackIt is a developer friendly cloud native application delivery platform with application as the core. It provides one-stop capabilities such as application orchestration, environment management, deployment and operation and maintenance, resource management and application release, helps enterprises establish an overall solution for continuous application delivery, accelerates the transformation of Enterprise Cloud native and Devops, and improves team R & D efficiency.
After creating a new environment, you can deploy, expand, roll back and other operation and maintenance operations on the environment as needed.
 
 

About us

More about cloud application delivery platform AppStack dry cargo and cloud efficiency trends, WeChat search attention [cloud effect] official account ~

Egg: official account back stage reply [guide], get the Alibaba DevOps Practice Guide & 10 times case study of efficiency enhancement.

After reading it, I think it’s helpful for you. Don’t forget to like, collect and pay attention

Recommended Today

Keyof type operator of typescript

preface The official documents of typescript have long been updated, but the Chinese documents I can find are still in the older version. Therefore, some newly added and revised chapters are translated and sorted out. This article is compiled from “typescript Handbook”Keyof Type Operator“Chapter. This article is not translated strictly according to the original text, […]