Stack Management
If you want to deploy multiple applications at a time, use a stack to implement automatic orchestration.
A stack is a deployment instance composed of applications, services, and resources. The ServiceStage manages these elements by means of stacks.
ServiceStage provides two methods for creating a stack.
- Creating a Stack Using a Template: A development engineer or maintenance engineer designs an application topology and lifecycle management plan, and develops an application template called blueprint. The system automatically creates a stack based on the template.
- Creating a Stack Using the Designer: ServiceStage provides a TOSCA-compliant graphic designer to streamline full-stack graphic orchestration and deployment for applications at the IaaS, ServiceStage, and SaaS. The designer can automatically generate an application template for the system to create a stack.
NOTE: Comply with the following rules when using stacks to co-deploy non-containerized applications: (co-deploy non-containerized applications refer to multiple non-containerized applications deployed on the same server):
- If multiple packages are deployed on one node, the directories and ports of the non-containerized applications cannot conflict.
- If VM clusters are co-deployed by means of stacks, the multiple application instances must be able to run on one VM without conflicts.
- If a declarative port is configured during stack-based VM deployment, the ServiceStage checks conflicts based on the port.
- The system supports soft affinity for stack-based VM deployment. Different instances of an application can be scattered, which is not rigidly required.
Before creating a stack, you are advised to read section Blueprint Development Specifications.
In addition, learn the concepts described in Table 39-4.
Term |
Description |
|---|---|
Orchestration |
Processes elements composed of a stack in a specified order. This process defines the application components, resource requirements, dependent services, and element relationships or topologies, provides description of the applications and their dependent services and resources, and transfers them to the ServiceStage for deployment. |
Stack |
A deployment instance composed of elements such as applications, services, and resources. ServiceStage manages orchestrated elements by means of stacks. |
Template |
Description of stacks, including application model-based stack topology definition, stack lifecycle, running resources, and software components. |
Element |
A building block that forms a template and the instantiation of an element type. An element indicates a node in a topology, which can be an application, service, resource, and child node. |
Application |
The minimum object that can be deployed. It is a logical entity and presents a service function to users. |
Service |
A function provided for users on demand. In ServiceStage, a service must be purchased and then bound to an application before it can be used. In some scenario, a service must be charged by usage. |
Resource |
Physical resources required to keep applications running, including computing, storage, and network resources. |
Relationship |
Dependency of the elements that form a template. In a topology, it is a link between two nodes. Relationships include applications running on resources, applications connecting to services, element deployment sequence, and application composition. |
Lifecycle |
In ServiceStage, it refers to the lifecycle of a stack or an application. It is the process from the stack or application is created until is it deleted, involving installation, startup, stop, deletion, upgrade, scalability, and gated launch. |
Blueprint |
Application packaging format in ServiceStage. It serves as the output of topology design and input of the application orchestration system. |
Software Repository |
Repository for Docker images, VM images, software packages, or templates in ServiceStage. |
Deployment |
The process for instantiating a template to the infrastructure. During deployment, a template instantiated using user inputs becomes a stack running on the ServiceStage. |
Node |
As described in the Topology and Orchestration Specification for Cloud Applications (TOSCA), a node is a building block that forms a service template and the instantiation of a node type, represented as a node in a topology. |
Input |
Input parameter used to instantiate a template. It is optional. |
Output |
Output parameter displayed after template instantiation. It is optional. |
Figure 39-2 shows the relationship between orchestration, blueprint, template, stack, and designer.
Previous
