Host applications

Parameter

Description

Version

Specify a version for the application. You can select a history version to roll back to during a rollback operation.

Application Group

Select an existing application group or click Create Application Group to create a new one. For more information about creating application groups, see "Create an application group."

Software Package

Select a software package type. Options include Container Image, Jar Package, War Package, and Helm Package, Legacy Package, and Front-end Resources Package.

• The image repository stores container images, and the application repository stores Jar, War, Helm, legacy, and front-end resources packages.

• You can select any of the options except the legacy package for a host application.

Resource Type

Select the type of the resource where the application will be deployed.

Configure Instance

Cloud Hosts: Virtual hosts managed by cloud services/cloud host services in this system.

To configure a cloud host instance:

3.     Click Configure Instance.

4.     Enter filter criteria and click Filter to display matching cloud host instances. Filter criteria include AZ, network type, network, IP address, instance name, and deployed applications. You can also create a cloud host instance by clicking Create Instance.

5.     Select one or more cloud host instances and enter the root user password of each cloud host instance. A cloud host instance uses the x86 or ARM architecture. If you select multiple cloud host instances, make sure they use the same architecture.

6.     Click OK.

Application Port

Enter the port of a JAR package, WAR package, or front-end resources package. This port must be the one that is actually used by the application.

Access Mode

Not Configure

Use the host IP address and application port to access applications.

Application Domain Name

Use the domain name to access an application.

• Domain Name: Configure a domain name, for example, example.com.

• Load Balancing Policy:

• Round Robin: Assigns requests to endpoints according to their weights.

• Least Connections: Assigns requests to the endpoint with the least number of connections.

• IP Hash: Assigns requests to endpoints based on the hash of source IP addresses.

• Enable Secure Routes: Select this option to enable HTTPS access mode.

• Enable Sticky Sessions: Select this option to enable a cloud host to respond to all requests from the same client.

IaaS Load Balancing

Use the virtual IP address of a load balancer and the listening port of a listener to access an application.

• Load Balancer: Select an existing load balancer or click Create to create a load balancer. If you select an existing load balancer and an existing listener, the system automatically adds the selected cloud hosts to the server farm of the listener. Therefore, the real servers in the server farm have been deployed with the same applications.

• Listener: Select a listener.

• LB Algorithm:

• Weighted Round Robin: Assigns new connections to real servers based on their weight values. A real server with a greater weight value is assigned more connections.

• Weighted Least Connections: Always assigns user requests to the real server with the fewest number of weighted active connections (the total number of active connections divided by weight).

• Source Address: Distributes user requests to different real servers according to the source IP address. User requests with the same source IP address can be distributed to the same real server.

• Sticky Sessions: Enable this option to distribute all requests from the same user to the same real server.

• APP_COOKIE: Use APP cookies to discriminate clients. Requests with the same APP cookie are sent to the same real server.

• HTTP_COOKIE: Use HTTP cookies to discriminate clients. The system adds a cookie to the HTTP response of the first request sent by a client, Subsequent requests with the same HTTP cookie are sent to the same real server.

• SOURCE_IP: Distribute user requests to different real servers according to the source IP address. User requests with the same source IP address can be distributed to the same real server.

Cookie Name

Enter a cookie name, a string of 1 to 32 characters. The name cannot start or end with a dot (.) and cannot contain full-width characters (except Chinese words) or the following special characters: \ /*?"<>|

App Access Path

After an application is deployed, it can be accessed through IP (domain name):port number/path.

Parameter

Description

Application Installation Package

Select an installation package from the private or public repository, or upload an installation package as described in "About application repository service."

Environment Variables

Configure user-defined environment variables for cloud hosts. You can use the environment variables to edit the configuration of cloud hosts after application deployment. User-defined environment variables cannot be the same as system-defined environment variables as shown in Table-3. You can configure user-defined environment variables by using the following methods:

• Manually Specify: Enter a variable name and value.

• To add more variable name and values, click Add.

• To add multiple variable name and values in bulk, click Quick Add to open a text box, enter variable names and values, and click OK.

JDK Version

Select an JDK version for the JAR package. Options include 1.8 and 1.11.

JVM Parameter

Configure JVM parameters for the JAR or WAR package.

Tomcat Version

Select a Tomcat version for the JAR package. Options include 8.5 and 9.0.

Tomcat Configuration

The system provides a default configuration file named server.xml. You can click Change Configuration to upload your file to replace the default configuration.

Nginx Version

Specify a Nginx version. Only version 1.20 is supported in the current software version. This parameter appears only when you deploy a front-end resources package.

Enable HTTPS

Choose to whether to enable HTTPS. If you enable HTTPS, you must upload a pair of public key certificate and private key certificate. This parameter appears only when you deploy a front-end resources package.

Public Key Certificate/Private Key Certificate

Upload a public key certificate or private key certificate:

7.     Click upload.

8.     Drag a certificate to the window or click click to upload to upload a certificate.

Nginx Configuration

Upload a configuration file:

9.     Click upload.

10.   Drag a configuration file to the window or click click to upload to upload a configuration file.

Software package type

Environment variables

WAR package

• TOMCAT_URL

• PKG_URL

• CONF_URL

• RELEASE_ID

• JAR_PARM

• PARM_LIST

• H3CLOUD_APM_TRIGGER

• H3CLOUD_SW_AGENT_NAMESPACE

• H3CLOUD_SW_AGENT_NAME

• H3CLOUD_SW_AGENT_COLLECTOR_BACKEND_SERVICES

• SW_AGENT_VERSION

• TOMCAT_UPGRADE

• SW_AGENT_CONFIG

• BASE_JDK_VERSION

• LOGROTATE_CRON

• NAMESPACE

• SERVICE_NAME

• JAEGER_AGENT_COMPACT

• JAEGER_AGENT_BINARY

• JAEGER_AGENT_ZIPKIN

• EUREKA_URL

• CONFIG_URL

• GRAY_VERSION

• REGISTRY_TYPE

JAR package

• JDK_URL

• PKG_URL

• JAR_PARM

• RELEASE_ID

• PARM_LIST

• H3CLOUD_APM_TRIGGER

• H3CLOUD_SW_AGENT_NAMESPACE

• H3CLOUD_SW_AGENT_NAME

• H3CLOUD_SW_AGENT_COLLECTOR_BACKEND_SERVICES

• SW_AGENT_VERSION

• SW_AGENT_CONFIG

• LOGROTATE_CRON

• NAMESPACE

• SERVICE_NAME

• JAEGER_AGENT_COMPACT

• JAEGER_AGENT_BINARY

• JAEGER_AGENT_ZIPKIN

• EUREKA_URL

• CONFIG_URL

• GRAY_VERSION

• REGISTRY_TYPE

Parameter

Description

Probe Enabling State

Choose whether to enable probing. Probing can be enabled only if you have installed application diagnostics cloud services.

Log rotation

Configure a log rotation policy, If you do not configure a log rotation policy, the system performs a log rotation operation at 4:30 a.m. every day.

A log rotation policy defines a rotation period through a CRON expression