Application Lifecycle Management

Overview

The following diagram provides an overview of the Workload Manager 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 your application service. These virtual base images comprise of the underlying operating system and any operations tools that are required or referenced by services. See OOB Base OS Images for a list of supported images.

Every Workload Manager deployment requires a Package Store and a hosting location for all Workload Manager-supported (out-of-box) Services. When you model an application, 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 Workload Manager OOB Application Services 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 Understand Application Tier Properties

Service Scripts

Workload Manager does not have hard requirements for scripts called by a service. If you configure a script, Workload Manager 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.

  • Workload Manager, 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: 

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved