Resource Template Service (RTS) makes it easier for you to simplify your cloud computing resource management and automatic O&M. Based on the template specifications defined in the RTS service, you can compile a template file and define a collection of cloud computing resources, dependencies between resources, and resource configurations. Then you can automatically create and configure all resources in the template by using the orchestration engine so as to implement automatic deployment and simplify O&M. The RTS service supports most native OpenStack Heat APIs and templates in the Heat Orchestration Template (HOT) format.
You can use RTS by calling RTS Application Programming Interface (API) or using the RTS console. The RTS console is a visualized user interface provided for RTS. With the RTS console, you can use templates to automatically deploy resources.
A template is a user-readable, easy-to-compile file that describes how to assemble a set of resources and install required software. This template specifies resources to be used, attributes to be set, and parameters indispensible to the success of automation for a specific application deployment.
A resource is a template that specifies the component of your desired architecture, including Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Cloud Eye, Elastic Load Balancing (ELB), Object Storage Service (OBS), Relational Database Service (RDS), Scalable File Service (SFS), Auto Scaling (AS), and Virtual Private Cloud (VPC) .
A stack is a collection of useful resources, including servers, ELBs, and databases. With a template, Heat orchestration engine helps create an instantiated set of resources, that is, a stack, to accommodate the specified application framework or component (contained in a template). A stack is actually a running instance of a template. Creating a stack is the deployment of an application framework or component.
A region is a geographic area where resources used by your RTSs are located.
An availability zone (AZ) is a physical location where resources use independent power supply and networks within a region. An AZ is insulated from failures in other AZs and provides inexpensive, low-latency network connectivity to other AZs in the same region. A region can have more than one AZ. AZs are physically isolated but interconnected through an internal network.