Adding a Custom Technology Stack Version

A technology stack includes the operating system, framework, and runtime system for component running. It consists of attributes such as the stack name, type, status, and version. For details, see Technology Stack.

Based on the built-in technology stacks, ServiceStage provides technology stack management to support technology stack version customization and multiple runtime systems.

You can add the technology stack type and deployment type of a custom technology stack version to ServiceStage. For details, see Table 1. For details about deployment types, that is, the component deployment modes supported by the component technology stacks, see Component Deployment Modes.

**Table 1** Custom technology stack versions
Type	Deployment Type
Java	VM: A VM, or an ECS or custom server, is a basic computing unit that consists of vCPUs, memory, OS, and EVS disks. After creating a VM, you can use it like using your local computer or physical server to deploy components. Kubernetes: container-based or CCE-based deployment. CCE is a scalable, enterprise-class hosted Kubernetes service. With CCE, you can easily deploy, manage, and scale containerized applications in the cloud.
Tomcat

Prerequisites

The technology stack version software package (in .zip or .tar.gz format) to be added has been uploaded to OBS. For details, see Streaming Upload (PUT).

Adding a Custom Technology Stack Version

Log in to ServiceStage.
Choose System Settings > Tech Stack Management. The Tech Stack Management page is displayed.
Select the target technology stack and click Add Tech Stack Version.

Set the parameters. Parameters marked with an asterisk (*) are mandatory.

Java

Parameter	Description
*Tech Stack	Technology stack version name. Enter 2 to 64 characters. Only use letters, digits, slashes (/), underscores (_), and hyphens (-). Start with a letter and end with a letter or digit.
*Tech Stack Version	Technology stack version. The format is A.B.C, where A, B, and C are natural numbers. Example: 1.0.0.
*OS Image	This parameter is mandatory for technology stacks whose Deployment Type is Kubernetes. Kubernetes is a container orchestration platform that manages containers (usually Docker containers). Each container runs in an isolated environment provided by an OS image. An OS image contains the OS kernel, libraries, tools, and applications required for running a container, ensuring that the container can run consistently in any Docker-enabled environment. Built-in: Select a built-in OS image from the drop-down list. Custom: Click Select Image Package and select the uploaded custom OS image package. My Images (private images), Open Source Images, Shared Images, and Third-Party Images are supported. If you select My Images, upload the image to the image repository in advance. For details, see Uploading an Image. If you select Third-Party Images, ensure that you have obtained the address of the third-party image. The format of the image address is as follows: {IP address of the third-party image repository}:{Port number for accessing the third-party image repository}/{Image storage path}/{Image name}:{Image tag} or {Image name}:{Image tag} If the image tag is not specified, the latest version is used by default.
*JDK Version Path	Path for storing the JDK software package that has been uploaded to OBS. Click Select Software Package. Select the path. Click OK.
Description	Technology stack description. Enter up to 512 characters.

Tomcat

Parameter	Description
*Tech Stack	Technology stack version name. Enter 2 to 64 characters. Only use letters, digits, slashes (/), underscores (_), and hyphens (-). Start with a letter and end with a letter or digit.
*Tech Stack Version	Technology stack version. The format is A.B.C, where A, B, and C are natural numbers. Example: 1.0.0.
*OS Image	This parameter is mandatory for technology stacks whose Deployment Type is Kubernetes. Kubernetes is a container orchestration platform that manages containers (usually Docker containers). Each container runs in an isolated environment provided by an OS image. An OS image contains the OS kernel, libraries, tools, and applications required for running a container, ensuring that the container can run consistently in any Docker-enabled environment. Built-in: Select a built-in OS image from the drop-down list. Custom: Click Select Image Package and select the uploaded custom OS image package. My Images (private images), Open Source Images, Shared Images, and Third-Party Images are supported. If you select My Images, upload the image to the image repository in advance. For details, see Uploading an Image. If you select Third-Party Images, ensure that you have obtained the address of the third-party image. The format of the image address is as follows: {IP address of the third-party image repository}:{Port number for accessing the third-party image repository}/{Image storage path}/{Image name}:{Image tag} or {Image name}:{Image tag} If the image tag is not specified, the latest version is used by default.
*JDK Version Path	Path for storing the JDK software package that has been uploaded to OBS. Click Select Software Package. Select the path. Click OK.
*Tomcat Version Path	Path for storing the Tomcat software package that has been uploaded to OBS. Click Select Software Package. Select the path. Click OK.
Description	Technology stack description. Enter up to 512 characters.

Click OK.

Click before the technology stack for which a custom technology stack version has been added to expand the technology stack list. You can see that the custom technology stack version exists with Type being Custom and Status being Disabled.