Application Lifecycle Management
The following diagram provides an overview of the CloudCenter application lifecycle:
Further lifecycle details are described in the following sections.
Base OS Images
Base OS images refer to Linux and Microsoft Windows cloud images on which you install CloudCenter components. These virtual base images comprise of the underlying operating system and any operations tools that are required or referenced by services. See Base OS images for a list of supported images.
Each version of CloudCenter contains the installers and scripts necessary for creating component appliances.
To create CloudCenter components, you have two options:
- Manual Install - no appliances necessary
- Appliance Install – appliances available for some cloud deployments
Once you have installed the required components (i.e., map images, you can begin the application or application profile modeling process., , and and
Every CloudCenter deployment requires a Topology Modeler Properties tab.a hosting location for all CloudCenter-supported Services. When you , all services are automatically detected by the Package Store and displayed on the
The Services Framework
When defining a new service, you can use global parameters, tier/step-specific system parameters, or user-defined parameters and add values at deployment time. See Custom Service Definition for additional information.
The Services Framework enables enterprises to create and add enterprise-specific, private services and make these additional services available via the
The CloudCenter platform does not have hard requirements for scripts called by a service. If you configure a script, the CloudCenter platform executes the configuration specified for each.
The script requirements are:
- The script must be in a folder with the same name as the service identifier.
- CloudCenter, as root, executes the scripts relative to the extracted folder in the zip file
Scripts are called up at various points during your deployment. See Deployment Lifecycle Scripts for additional information.
- When modeling applications you may need to call application-specific scripts for functions such as install, start, restart, and so forth. The called upon scripts may have hard-wired values for configuration parameters which may need to be changed at deployment time. See Configuration Files for additional information.
Configuration parameters represent settings that must be reconfigured when your application is deployed on the target cloud. See Using Parameters for more information.
How Does an Application Profile Work?
- Model a New Application Profile
- Model an Application
- Model Application Using Custom VM Image
- Model an Application by Importing the Profile
- Model Using Application Packages
- Model Applications Using Puppet and Chef
How Does Governance Work?
A system tag is a label that consists of a name and an optional description. You can associate system tags with application profiles and application deployments, either at the tier level or globally. You also can use system tags to add system tag matching rules to aging or scaling policies, security profiles, and deployment environments. See the following pages for additional information:
- No labels