Logging In to ServiceStage

Prerequisites

• You have registered a Huawei account and enabled Huawei Cloud services.
• The login account has the permission to use ServiceStage. For details, see Using IAM to Grant Access to ServiceStage.

Logging In to ServiceStage

1. Log in to the management console.
2. Click and select a region.
3. Click in the upper left corner, and click ServiceStage.
   • If you log in for the first time, click Authorize on the displayed service authorization page to authorize ServiceStage to use the services on which it depends. Then, the ServiceStage console is displayed.
   • If this is not your first login, the ServiceStage console is displayed directly.

   For details, see Table 1.

   Table 1 ServiceStage console

   Module	Description
   Overview	The Overview page provides a dashboard, including ServiceStage edition selection, total number of environments, applications, and components, monitoring information, alarms, and documentation. Edition selection: ServiceStage provides the basic and professional editions in pay-per-use billing mode. You can select an edition as required. For details, see Changing the ServiceStage Product Edition. Environments: displays the number of created environments. You can click Environments to go to the Environment Management page and view environment details. Applications: displays the number of created applications. You can click Applications to go to the Application Management page and view application details. Components: displays the number of deployed components. You can click Components to go to the Component Management page and view component details. Customize Monitoring: Move the cursor to Customize Monitoring in the upper right corner and select the applications and environment to be displayed on the Overview page. A maximum of four monitoring information records can be displayed. Where, Applications: displays the name of each application, number of deployed components (including available and unavailable components), and CPU and memory usage of the application. Environments: displays the name of each environment, CPU and memory usage in the environment, number of components deployed in the environment, resource health, and instance health of deployed components. Click CPU usage or Memory usage on an environment card to enable or disable the information display. Remove the monitoring information that does not need to be displayed: Click in the upper left corner of a card to be removed and click Remove. Move the cursor to Customize Monitoring in the upper right corner and deselect the monitoring information that does not need to be displayed. Alarms: Click Learn More in the Alarms area to go to the AOM console and view ServiceStage alarm details. Documentation: Click Learn More in the Documentation area to view ServiceStage documents.
   Environment Management	An environment is a collection of compute, network, and middleware resources used for deploying and running a component. The Environment Management page allows you to create, edit, and delete environments, and configure resources (manage and remove resources). Created environments are displayed in a list.
   Application Management	An application is a service system with functions and consists of one or more components. The Application Management page allows you to create, edit, and delete applications. Created applications and the number of components created under them are displayed in a list, and entries for creating components under applications are available.
   Component Management	A component is a service feature implementation of an application. It is carried by code or software packages and can be independently deployed and run. The Component Management page displays components of all applications in a list, and provides the component details page as well as the entries for component creation and O&M.
   Configuration Management	In ServiceStage, a configuration is a file. You can fill the environment and application system variables (such as the IP address, port number, database address, and application name associated with the environment) in a configuration file. When the component is associated with the configuration for deployment, the system variables are automatically replaced with the actual values. This implements multi-environment use with one-time configuration through file mounting. The Configuration Management page allows you to create, edit, and delete configurations. Created configurations are displayed in a list.
   Release Management	Release tasks of different types provide functions for releasing applications: single-component release, batch operations (release, upgrade, and clone), and dependency-based orchestration. This feature enables you to flexibly deploy components in batches, improving service efficiency and user experience. This page displays created release tasks and provides entries for creating and managing release tasks.
   System Settings	Provides an entry for customizing technology stack versions to provide multiple runtime systems. It also provides entries for starting, stopping, editing, and deleting technology stack versions. Provides an entry for configuring and managing directories to manage the startup users, running directories, and log directories of VM-deployed components. You can view the default directory rules of the system or customize directory rules.
   Deployment Source Management	Provides functions such as organization management, software repository, and image repository. Organization management is used to isolate images and assign access permissions (read, write, and manage) to different users. Image repositories are used to store and manage Docker images. Software repositories are used to store, manage, and deploy software packages.
   Continuous Delivery	Provides functions such as viewing build projects, releasing build projects, and authorizing repositories. Build The software package or image package can be generated with a few clicks in a build job. In this way, the entire process of source code pull, compilation, packaging, and archiving is automatically implemented. Pipeline One-click deployment can be achieved through pipeline. In this way, the entire process of source code pull, compilation, packaging, archiving, and deployment is automatically implemented. This unifies the integration environment and standardizes the delivery process. Repository Authorization You can create repository authorization so that build projects and application components can use the authorization information to access the software repository.
   Cloud Service Engine	Provides operation entries for instance management, dashboard usage, microservice catalog management, microservice governance, configuration management, and system management of engine instances.