Redeploying a Component Using a Component Template
Redeploy a component created by Creating a Component Using a Component Template.
Prerequisites
- You have upgraded a component. For details, see Upgrading a Component Using a Component Template.
- The component status is Running, Not ready, or Abnormal. For details about how to check the component status, see Viewing Component Details.
- You have compressed the prepared component template files into a ZIP package and uploaded the package to the repository. For details, see Component Template Description.
- Upload the template package to the SWR repository. For details, see Uploading a Software Package.
If PKIToken is disabled, the SWR repository is not supported.
- Select the corresponding template package from OBS. Upload the template package to the OBS bucket in advance. For details, see Streaming Upload (PUT).
- If you need to use JFrog (example) as the repository for storing the component template package, you can use an HTTP/HTTPS custom file address as the component template package download address. Upload the component template package to the custom file address in advance.
- Upload the template package to the SWR repository. For details, see Uploading a Software Package.
Redeploying a Component Using a Component Template
- Log in to ServiceStage.
- Use either of the following methods to go to the View Deployment History 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.
- In the Deployment Records list, select the deployment record of the historical version to be used as the configuration template.
- Click Redeploy in the upper right corner of the page. The Redeploy dialog box is displayed.
- Select a deployment type.
- Single-batch release: During component redeployment in this mode, component services will be interrupted. This is supported only by container-deployed components and is applicable to the test upgrade scenario or the upgrade scenario where services are to be stopped.
- Rolling release: Only one or more instances are deployed at a time and then added to the production environment. This process repeats until all old instances are upgraded. Services will not be interrupted during the deployment.
- Click OK.
- In the Set Template Package area, select the uploaded component template package based on the template package storage mode.
- CodeArts release repository
- If CodeArts release repository is not the component template repository, click Select Software Package, select the uploaded template package from the CodeArts release repository, and click OK.
- Otherwise, click
, select the uploaded template package from the CodeArts release repository, and click OK. Alternatively, click
> Select Software Package, select the uploaded template package from the CodeArts release repository, and click OK.
- OBS
- If OBS is not the component template repository, click Select Software Package, select the uploaded template package from the OBS bucket, and click OK.
- Otherwise, click
, select the uploaded template package from the OBS bucket, and click OK. Alternatively, click
> Select Software Package, select the uploaded template package from the OBS bucket, and click OK.
- SWR repository
- If SWR repository is not the component template repository, click Select Software Package, select the uploaded template package from the SWR repository, and click OK.
- Otherwise, click
, select the uploaded template package from the SWR repository, and click OK. Alternatively, click
> Select Software Package, select the uploaded template package from the SWR repository, and click OK.
- Custom file address: If you need to use JFrog (example) as the repository for storing the template package, perform the following operations to obtain the template package that has been uploaded to the custom file address:
- Enter the HTTP/HTTPS custom file address where the software package is located. The custom file address must be the complete path of the component template package file, for example, https://172.16.0.1:8082/artifactory/template-component.zip.
- 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.
- CodeArts release repository
- Click Next.
- In the Preview Template Package area, you can view the details of the component template file.
- In the Set Parameters area, you can view and modify the component parameters.
- Click Upgrade.
- During component redeployment, if the component configuration is incorrect, you can click Suspend to stop the redeployment. Then, click Upgrade and reconfigure the component by referring to Upgrading a Component Using a Component Template.
- Wait until the component status changes from Upgrading/Rolling back the component to Running, indicating that the component has been upgraded.
- On the Deployment Records page, view the deployment logs.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot