CliQr is now part of Cisco Learn More About Cisco

Application Lifecycle Management

Overview

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 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

You must contact CloudCenter Support to obtain either the Installer Packages or Virtual Appliance packages.

Using one of these packages and then following the process specified on the Install CloudCenter page, you can launch the CloudCenter virtual appliances for each component.

Once you have installed the required components (i.e., CCMCCO, and AMQP) and map images, you can begin the application or application profile modeling process.

Every CloudCenter deployment requires a Package Store and a hosting location for all CloudCenter-supported (out-of-box) Services. When you Install CloudCenter, all services are automatically detected by the Package Store and displayed on the Topology Modeler Properties tab.

The Services Framework

A service is one of the building blocks to model an application (or application profile) and is mapped to virtual images. You can create an application using multiple tiers in which you specify each tier to use a different CloudCenter supported service or externally-provided service (i.e., third-party services). See External Service for additional information.

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 Topology Modeler Services tab.   (see Service Administration and Service Lifecycle Actions for additional information)

For tier-specific parameter configuration, see Service Properties

Service Scripts

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 Service Lifecycle Action.

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.

Service Parameters

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?

When modeling applications or application profiles, verify the prerequisites depending on your deployment scenario. See the following pages for additional information: 

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