ServiceStage Usage Process

As shown in Figure 1, you can use ServiceStage to create running environments, create applications, create and deploy components, and manage components.

Figure 1 ServiceStage usage process

1. Create and manage environments.

   An environment is a collection of basic compute (such as cluster 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 creating and deploying components by environment simplify O&M management.

   Before using ServiceStage to create and deploy a component, create an environment and manage resources for the environment. For details, see Environment Management.

2. Create and manage applications.

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

   A component must belong to an application. Before using ServiceStage to create and deploy a component, create an application. For details, see Application Management.

3. Create and deploy components.

   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 in an environment.

   Use ServiceStage to create and deploy a component. For details, see Creating and Deploying a Component.

4. Manage components.

   Manage components after the components are created and deployed.

   • To upgrade a single component, see Upgrading a Single Component.
   • To upgrade components in batches, see Upgrading Components in Batches.
   • To redeploy a component using the historical version configuration as the template, see Redeploying a Component.
   • To roll back a component, see Rolling Back a Component.
   • To manage component running metrics and logs, see Component O&M.
   • To manage component instance scaling, see Configuring a Scaling Policy of a Component Instance.

You can also use other capabilities provided by ServiceStage based on service requirements.

• Configuration Management: By creating a unified configuration, you can fill the system variables (such as the IP address, port number, database address, and application name associated with the environment) of the component environment and application in the configuration to generate a configuration file. When a component is associated with a configuration file for deployment, the system variables are automatically replaced with the actual value. This implements multi-environment use with one-time configuration through file mounting.
• Tech Stack Management: Based on the built-in technology stacks, ServiceStage provides technology stack management to support technology stack version customization and multiple runtime systems.
• 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. 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. 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. You can use repository authorization so that build projects and application components can use the authorization information to access the software repository.
• Microservice Engine: Cloud Service Engine is a one-stop management platform for microservice solutions. After microservice components are connected to CSE, you can use service registry, service governance, and configuration management of CSE. In this way, you can focus on service development and improve product delivery efficiency and quality. You can Binding a Microservice Engine when setting Cloud Service Settings for the component.