Flexible implementation of automated deployments of various environments using TPM software components

By flexibly using the Software Stack in the TPM, Software Product, and the SRT defined on it, you can combine different types of environmental deployment, such as creating only virtual machines, installing software only, creating virtual machines, and installing software. This article will detail how to use TPM software components to flexibly implement automated deployments of various environments by defining different SRT parameters.

The TPM full name is http://www.aliyun.com/zixun/aggregation/13966.html ">tivoli provisioning Manager, IBM's core automated deployment engine, Can automate the deployment of multiple complex software environments. Support for virtual machine deployment on a variety of virtualization platforms, support for multiple software distributed installations on different platforms, high scalability, and support for custom TPM workflows (workflow) for automated installation of customized software. In the cloud service era, the TPM can easily provide an entity environment or a virtual environment without a supervised deployment service.

As a stand-alone software, the TPM can be configured and managed by an administrator on the TPM interface to automate the installation of virtual machines and software, while the TPM provides a program interface, and external applications can invoke the TPM to automate the deployment of the virtual environment. This article will introduce the external application call TPM interface to implement virtual machine deployment and software installation, not simply by passing in the required parameters of workflow to invoke a specific workflow, but with an extensible flexible framework to implement.

DCM and critical software components of the TPM

The TPM data exists in the database, but it also defines a set of its own data model, DCM (data Center model). DCM is represented in XML format and has its own query language (similar to XQuery), which makes it easy to identify the data attributes and other data associated with it. In DCM, the concept of software definition is mainly as follows:

The following two sections describe the three software components in two representations.

Software components on the TPM console

On the TPM console, we open a Software Stack, as shown in Figure 1:

Figure 1. Software Stack on TPM console

Figure 1 shows a software stack (Software stack) that includes a name, the software products it contains (Software Modules) and SRT (revisit Templates). SRT is a tree structure, the parent SRT contains two child SRT, the figure shows the child Srt--mw_tds details, the main is the installation parameters of the name value pairs. This software stack contains only one software PRODUCT Mw_tds, and the definition of entering this SOFTWARE PRODUCT is shown in Figure 2.

Figure 2. Software Product on the TPM console

The SOFTWARE PRODUCT (MW_TDS) shown in Figure 2 defines the installation file directory and name of the software, the file server where it resides, and the installation Workflow script (workflow) used. This tells the TPM how to install the software.