Functions

Permissions Management

This section describes how to use Identity and Access Management (IAM) to implement fine-grained permissions control for your ServiceStage resources. With IAM, you can:

• Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to ServiceStage resources.
• Grant only the permissions required for users to perform a specific task.
• Entrust a Huawei Cloud account or cloud service to perform professional and efficient O&M on your ServiceStage resources.

Environment Management

An environment is a collection of basic compute (such as CCE and ECS), network (such as ELB and EIP), and middleware (such as DCS and RDS) resources, used for component deployment and running. ServiceStage combines multiple basic resources into an environment, including development, test, pre-production, and production environments. Managing resources and deploying components by environment simplifies O&M management.

A maximum of 2,000 environments can be created in a project. For details, see Creating an Environment.

Application Management

An application is a service system with functions and consists of one or more components.

ServiceStage allows a single user to create a maximum of 7,500 applications under the same project. For details, see Creating an Application.

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.

After creating an application on ServiceStage, you can add components to the application. A maximum of 15,000 components can be created for an application.

You can set the component technology stack and component source based on service requirements to create and deploy components. For details, see Creating and Deploying a Component.

Configuration Management

The configuration file can be used to manage parameters required for component running. System variables related to the environment, application, and component are referenced in a configuration file. When configurations are used for component deployment, these system variables are replaced with the actual values. This feature enables you to use one configuration file to flexibly deploy components in environments, improving service efficiency and user experience.

A maximum of 1,000 configuration files can be created in a project. For details, see Creating a Configuration File.

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. Specifically, you can:

• Create a batch deployment release task to deploy components of different technology stacks in different deployment environments of different applications.
• Create a batch upgrade release task to upgrade components of different applications in batches and specify the component upgrade sequence to ensure that services are not affected during the upgrade.

• Create a batch clone release task to clone components of different applications and quickly configure and deploy components in batches.

Technology Stack Management

A technology stack includes the operating system, framework, and runtime system for component running. Its attributes include the stack name, type, status, and version.

Based on the built-in technology stacks, ServiceStage provides technology stack management to support technology stack version customization and multiple runtime systems. For details, see Adding a Custom Technology Stack Version.

Deployment Source Management

Functions such as organization management, software repository, and image repository are provided.

• 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

Continuous delivery provides functions such as project build and release. For details, see Creating a Source Code Job.

Microservice Management

The microservice engine of ServiceStage supports access and governance of mainstream microservice frameworks. You can select a suitable microservice technology to quickly develop cloud applications to achieve complex and ever-changing service requirements.

• Native ServiceComb microservice framework: Microservices developed by using ServiceComb can be seamlessly connected to microservice engines. The microservice engine uses Apache ServiceComb Service Center, which is a RESTful-style, high-availability, and stateless service registry and discovery center and provides microservice discovery and management. Service providers can register their instance information with the registry and discovery center for users to discover and use.
• Compatible with mainstream microservice open-source frameworks: A simple access mode for microservices developed by using Spring Cloud is provided. You only need to modify the dependencies and configurations to access microservice engines and use the unified governance policies.

• Microservice governance: After an application developed using the microservice framework is managed on ServiceStage, the microservice will be registered with the service center after the application instance starts. You can govern microservices.