About Application Profiles
Application Profiles in CloudCenter are templates or blueprints that can be used to describe how applications should be deployed, configured, and managed on cloud environments. Application Profiles allows you to quickly describe and onboard applications in a cloud-independent manner.
An Application Profile does not require the user to provide any cloud-specific information or hard-wire the profile to any cloud infrastructure.
Once created, the profile enables enterprises to launch their applications on any . CloudCenter supports multiple options for users to accelerate the application onboarding process. These options are organized based on commonly used applications.
- 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)
Application Profiles have the following characteristics:
- Created using CloudCenter supported images or using private customer images. See Application Tasks for additional context.
- Shared between multiple users within each deployment. See Permission Control for additional context.
- Maintained on multiple clouds (cloud-agnostic images and application packages/scripts). See Application Workflow for additional context.
Create Application Profiles
To create application profiles, see
Once you create an Application Profile, the application is ready to be deployed on any target cloud.
Once you create the Application Profile, select any target cloud to deploy the application. CloudCenter automatically filters clouds that do not meet the application requirements.
The running on the target deployment cloud. The orchestrates the deployment tasks:passes the application to the respective
- Provisions and configures cloud infrastructure and services as determined in the Application Profile (compute, storage, networking)
- Launches VMs and mounts them to the storage repository on that cloud so the VMs can access application packages, data, and scripts specified in the profile
- Deploy each application component (different tiers in a multi-tier application)
- Start application services in the right order based on the service dependencies
During each stage of the orchestration, the send status messages to the so you can view and track the application deployment status.
The continues to monitor and meter deployed applications through the CloudCenter Management Agent. Monitoring and metering data is sent to the for reporting purposes. The continues to enforce deployment policies created by the user. For example, a user may have associated a deployment with an auto-scaling policy. The continues to monitor the deployed application and orchestrates scaling as specified by the user in the policy.
Similar to first-time deployment, the orchestrates subsequent lifecycle management functions such as: Start, Stop, Remove, and Upgrade
See Manage for additional context.
Migrate Applications from One Cloud to Another
You can also use CloudCenter to migrate a deployed application from one cloud to another using a downtime-based migration process. For live migrations, the application should support
CloudCenter follows an automated process to migrate application from one cloud to another:
- On the cloud where the application is running, the to shut down the deployment and save a backup to the storage repository on this source cloud. instructs the
- Once the shutdown and backup are complete, the 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 on the target cloud and instructs the to provision the application in restore mode. sends the Application Profile to the
- The target cloud deploys the Application Profile as specified in the Application Profile and restores the application backup during deployment.
Application Workflow States
- No labels