About Application Profiles
A cloud-agnostic, ready to deploy JSON and XML description used to deploy an application while retaining its cross-environment portability is referred to as an application profile in the CloudCenter platform -- Application Profiles enable you to quickly describe and onboard applications in any supported cloud.
An Application Profile does not require you to provide any cloud-specific information or hard-wire the profile to any cloud infrastructure.
An out-of-box topology that determines orchestration tasks appropriate for different application types (for example, tiered web applications, job-based, and so forth) or application technologies (for example, Java, Hadoop, and so forth) is referred to as an application profile template – these templates can be used by CloudCenter users to describe how applications should be deployed, configured, and managed in a cloud environment.
Application Profiles have the following characteristics:
Created using CloudCenter supported images or using private customer images (See Application Tasks for additional information)
Shared between multiple users within each deployment (See Permission Control for additional information)
Maintained on multiple clouds (e.g., cloud-agnostic images and application packages or scripts) (See Application Workflow for additional information)
CloudCenter supports many options that enable you to decrease the time it takes to onboard an application profile. These options are organized according to commonly used application categories. For example:
High-Performance Computing (HPC), desktop, parallel, web, batch, or cluster applications
Multi-tier/multi-service complex deployment topology applications or simple application models
Image-based services or end-point services (for example, Windows OS images)
Create Application Profiles
To create application profiles, see
Once you create the Application Profile, you can deploy it to a single cloud, or if a multi-tier application, you can deploy each tier to a different cloud (hybrid deployment).
The CCO running on the target deployment cloud. The CCO orchestrates the following deployment tasks:passes the application to the respective
Provisions and configures cloud infrastructure and services as determined in the Application Profile (e.g., compute, storage, networking)
Launches VMs and mounts them to the storage repository on the target cloud so that the VMs can access the specified application packages, data, and scripts
Deploy each application component (applies to different tiers in a multi-tier application)
Start application services in the correct order based on service dependencies
During orchestration, the CCO sends status messages to the so that you can view and track the application deployment status.
The CCO monitors and meters deployed applications through the CCM Agent. The CCO enforces the deployment policies you created.
For example, you may have associated your deployment with an auto-scaling policy. The CCO monitors the deployed application and orchestrates scaling as specified by your policy.
The CCO orchestrates subsequent lifecycle management functions such as: Start, Stop, Remove, and Upgrade
See Application Tasks for additional information.
Migrate Applications from One Cloud to Another
You can use CloudCenter to migrate a deployed application from one cloud to another using a downtime-based process.
For live migrations, the application should support
CloudCenter uses the following process to migrate an application from one cloud to another:
On the cloud where the application is running, the CCO to shut down the deployment and save a backup to the source cloud storage repository.directs the
After the shutdown and backup are complete, the CCO on the source cloud initiates a file-sync of the backup to the storage repository on the target cloud.
When the backup is complete, the sends the Application Profile to the CCO on the target cloud and directs the CCO to provision the application in restore mode.
The target cloud CCO deploys the specified Application Profile and restores the application backup during the deployment.
For more information about .zip files, see Model Using Application Packages.
Application Workflow States
- No labels