Application O&M provides application-centric operations for managing both applications and servers. You can perform five main operations: Restart, Online, Offline, Static resource deployment, and Initialize server.
Prerequisites
The server must be attached to the application and have a valid status.
For technology stacks provided by SOFAStack, such as SOFA Lite Web, SOFA Lite Core, and Spring, only the Linux operating system is supported. You must use the CentOS 7.x image provided by SOFAStack.
Create and execute an Application O&M ticket
On the App operations page, click Create. Configure the O&M ticket as described in the following table, and then click Create.
Configuration Item |
Description |
Title |
Enter a title for the O&M operation. It can contain 1 to 50 Chinese or English characters. |
Type |
The following O&M operations are supported:
|
Use Flow Template |
Disabled by default. If you enable this option, you must select from existing flow templates. Selecting a template replaces the current fixed publishing and deployment flow. |
Group policy |
Supports Quick group, Group all servers, Group by each server, Group by unit. |
Group by beta |
Disabled by default. If enabled, one server from each data center is selected as a member of the Beta group for the application. During publishing, this group is deployed first. You must manually confirm its completion before subsequent groups can be published. |
Ops dimension |
It supports App service and Server.
|
Deployment unit |
This is required when Ops dimension is set to App service. Check the required deployment units. |
App service list |
This is required when Ops dimension is set to App service. In the Selectable App service list, select the services you need and click the > icon to add them to the Selected App service List list. |
Server List |
This is required when Ops dimension is set to Server. You can perform O&M operations on selected servers, or on all valid servers in a specific data center under an application service. In the Select one or more machines list, select the servers you need and click the > icon to add them to the Selected machines list. |
Resource Address |
This is required when Type is set to Static resource deployment. Enter the download URL for the static resource.
Note
Currently, only the tar.gz package format is supported. |
Storage location |
This is required when Type is set to Static resource deployment. Enter the storage location for the static resource, such as
Important
The path must start and end with a |
System user |
This is required when Type is set to Static resource deployment. The default user is root. Click Modify to change it. |