Application Profile Export/Import
An application file that was exported by the CloudCenter platform can be imported into the same or different CloudCenter platform if the cloud environment is one of the clouds identified in the Restrictions section below:
The export deployment feature allows you to export applications from a deployed CloudCenter environment to a storage system.
The import deployment feature allows you to import applications from a storage system to another CloudCenter environment.
The following figure illustrates application profile export and import.
The deployment export/import feature includes the following details:
- Deployment details:
- The running deployment details.
- Underlying OS (ability to select specific instances supporting this application).
- Configuration profile details (network architecture, specific host and instance configuration, application configuration, information to support the application migration to another supported cloud).
- Storage system details:
- Refers to a networked cloud or a separate storage device specified by the user.
- The exported application is stored as a single archive.
- Export details:
- Exported as a set of files to the target folder or repository specified in the CCM UI or API.
- Once exported, you can manually copy the files to the target environment and import the application deployment within that environment.
- The CloudCenter platform handles each image based on the associated cloud provider:
- AWS = Grants image permission to store in the repo. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sharingamis-explicit.html for additional context.
- VMware = Downloads the cloud images and stores them in the repo.
- OpenStack = Downloads the cloud images and stores them in the repo.
Only available for AWS, VMware, and OpenStack clouds.
Transient CPU and memory states are not preserved.
VM Snapshot migration is only supported within the same cloud family.
The base image or VM snapshot can only be imported to the SAME cloud family. For example, an Amazon image might be exported to and imported from an Amazon Gov Cloud, but not a VMware cloud.
The VM snapshot should only be applied to non-clustered tiers or clustered tiers with VMs having homogeneous configurations.
The license handling is different for each OS. You may need to reapply licenses on the target cloud, and this task must be done manually.
The Windows image requires the same AD and user SSID to exist in the target environment.
The data on attached volumes is not exported.
Even a minor difference on the base OS can result in an image boot failure.
Configuration Properties: Verify that the following properties are set in the /usr/local/cliqr/.config-repo/cloudcenter-cis.properties file:
You must manually grant image permissions to the target account when importing Amazon images.
Granting image permission requires ownership of the Amazon Machine Image (AMI).
You can use one of two approaches when you export applications:
Component-Based Export – The implications of using this approach are:
Uses the base image with the OS.
The underlying OS on which the service runs can sometimes vary between the source and target environment.
Suitable for multi-tier applications and cross-cloud environments (requires knowledge of the CloudCenter application configuration procedures and processes).
If the same service is available on the target cloud, the application package and data can be exported from the source environment and imported to the target environment.
VM Snapshot Export – The implications of using this approach are:
Uses the endpoint service (pre-existing service that does not require provisioning).
Only possible if the application is tightly coupled with the underlying OS.
The application image of VM snapshot is exported from the source cloud and imported into the target cloud.
Application Tier Options
The application may have multiple application tiers. Each tier may be one of the following types:
Component-Based Tiers or VM Snapshot Tiers (one or the other, not both): In this case, the exported file can include:
The service definition.
(Optional) The pre-migration script to backup data from the source and restore to the target environment.
Component-Based Tiers and VM Snapshot Tiers (mixed tiers): A multi-tier application can have application tiers with mixed tier types. Depending on each application tier type, you must use different export options.
You can only use the export and import functionality if your user role was assigned the required permissions by your tenant admin for the following resources
Permission Control > Deployment Permissions for the application to be exported/imported.
Permission Control > Tenant Owner Permission Nuances for additional context. The following screenshot shows the Edit User Role options.Export/Import Permissions – As an admin, you can configure permissions for any user to export/import applications by navigating to CCM UI > Admin > Roles and clicking Edit for the required user role. Be sure to select the check box to Import Deployment and/or Export Deployment depending on the permission required for this user role. See
To export an application deployment from one CloudCenter environment to another, follow this process.
Ensure that you have the permission required to export this application deployment as identified in the Permissions section above.
Log into the CCM UI and navigate to the Deployments > Applications Deployments tab. The following screenshot shows this tab.
Select Export to Repository from the Actions dropdown for this application deployment. The Export Deployment Name popup displays, as shown in the following screenshot.
In the Export Deployment Name popup, provide the following information:
From the Export Data Location dropdown, select the FTP or S3 repo location (a writable repo with a relative path to which the exported file (archive) must be downloaded.
For the selected repo location:
Provide a path and/or folder or the username for the selected repo location.
(Optional) The exported application file can be encrypted and password protected. If so, provide and confirm the password in the Encryption Password field.
Select Component Based (default) or VM Snapshot.
(If you select Component Based) Identify the information to be included in the Application Export:
Identify the metadata attributes for each tier attribute.
Base Image — If checked, the images that the services depend on are also exported.
Service Definition — If checked, CloudCenter service definition is exported. If you additionally select the Base Image option, the corresponding image is also exported.
Application data backup — If checked, the data backup script is run and the backup data is persisted in the repository for future restoration.
Be aware that the application VM may be suspended when the VM snapshot is being retrieved and resumes running as soon as this task is completed.
If the communication between the CCM and CCO has a problem, the job/deployment status may be stuck at the Exporting level. In this case, navigate to the Deployments > Applications Deployments tab and select Refresh Status from the Actions dropdown for this application deployment. This action restores the status to Deployed if the export task is in the Finished/Canceled/Error state.
Once you export the image, you can view the status as follows:
Click the View Status button that appears with the success message to view the status for all export tasks, as shown in the following screenshot.
Click the info icon to view the progress of all Export requests, as shown in the following screenshot.
Either way the Export (or Import) information is displayed as shown in the following screenshot.
Application Export Package Format and Contents
The application export package is a collection of files that are compressed, and optionally encrypted by a user specified password. A sample format for this compressed file is displayed in the following example.
The following table describes the export package files and folders.
This file contains the metadata information for the application deployment:
The JSON file containing the original deployment parameters.
The JSON file containing entries of image file names.
The JSON file containing logical images and their image mapping information.
The JSON file containing service definition information.
|instance_types.json||The JSON file containing cloud instance type definition information.|
The ZIP file containing the application profile details. It captures the application stack, topology, settings, and reference to application specific artifacts such as package, setup and configuration scripts, and so forth.
The folder containing the service logo files.
The folder containing the service bundle files.
The folder containing the application artifacts such as application packages.
The folder containing the application backup data files.
The folder containing the exported physical cloud image files.
The JSON_Schema for the manifest.json file is displayed in the following example:
The events that the following table describes are logged for the export/import activities.
An application profile is imported successfully
An application profile import failed: <reason>
An application profile is exported successfully
Application profile export error: <reason>
Image mapping information is imported
Image mapping import failed: <reason>
Image mapping information is exported
Image mapping export failed: <reason>
Service definition is imported
Service definition import error: <reason>
Service definition is exported
Service definition export error: <reason>
Service bundle is imported to repository <repo_name>
Service bundle import error: <reason>
Service bundle is exported to repository <repo_name>
Service bundle export error: <reason>
Package is imported to repository <repo_name>
Package import to repository <repo_name> error: <reason>
Package is exported from repository <repo_name>
Package export from repository <repo_name> error: <reason>
Deployment information is exported
Deployment export error: <reason>
Deployment is migrated to cloud <target_cloud>
Deployment migrate error: <reason>
See Locate Log Files for additional context on log files.
To import an application deployment from one CloudCenter environment to another, follow this process.
Ensure that you have the permission required to import this application deployment as identified in the Permissions section above.
Log into the CCM UI and navigate to Applications > Applications Profiles. The following screenshot shows the Application Profiles page.
Click Import and select the Repository (Migrated Bundle) option. The Import Application popup displays, as shown in the following screenshot.
If you select the Profile Package option (importing a saved Actions Library > Lifecycle Action Mapping.), you have the option to map lifecycle actions as specified in
Enter the repository location from which to import the file and provide the user credentials for this repository.
Be aware that you must provide the corresponding exportId in the path/folder. For example, if your exported ID is 39, and your folder location is NOV/30/CC1, then you must provide the path/folder as NOV/30/CC1/39 as displayed in the following screenshot.
Click Next. The Import Application Name popup displays, as shown in the following screenshot.
Update the information for the file to be imported and add specify the path for the scripts or the jar files in the Artifact Repository folder field.
Click Import. The Applications Profiles page refreshes to display the status of the import.
You can only import an application if it meets the following requirements:
The application is deployed successfully
The application has been exported successfully
Be aware of the following nuances when you import applications:
An imported application can be deployed with or without the parameters that were configured when this application was exported.
To deploy this application using the imported parameters, access the CCM UI > Applications tab and select Deploy with Import Parameters from the dropdown list. The Deploy Application Name page displays. The following screenshot shows selecting Deploy with Import Parameters.
If you deploy and application, using the imported parameters, the Terminate Protection checkbox in the Deploy page is enabled by default. See Termination for additional context. The following screenshot shows the Terminate Protection checkbox.
When you import applications, you have multiple options:
Import Service: By checking this box, you instruct the CloudCenter platform to import the application along with the service(s) defined when the application was exported. The following screenshot shows the Import Service checkbox.
Remap Service: By checking this box, you instruct the CloudCenter platform to import the application along with the service(s) defined when the application was exported – however, you choose to remap the tier using your own OS and not the OS with which this application was exported. The following screenshot shows the Remap Service checkbox.
Import Service with the exported base image: If you are importing the base image(s) and the service(s) when the application was exported, then you see the additional Import Application - Image Options popup where you can select Remap Image or the Import Image for each tier in this application. The following screenshot shows the Remap Service checkbox.
If you select the Import Image checkbox, you must provide the Image Name as displayed in the example above.
Application Data Backup: Check this box if you want to use the running data (for example, the database records, configuration backup, and so forth) to export the deployment with the intention to restore it at some point.
Abort and Delete Export/Import Operations
After you export/import an application, you have the opportunity to abort the operation.
To abort an export/import that is in progress, follow this procedure.
- Click the View Status button in the green status bar at the top of the CloudCenter page, as shown in the following screenshot.
- In the Exports (or Imports) pop up, click the X next to the required task, as shown in the following screenshot.
- In the Cancel Export (or Import) popup, click OK, as shown in the following screenshot.
The Exports (or Imports) popup refreshes to display the aborted export (or import) operation, as shown in the following screenshot.
Click the Delete icon to delete this export (or import) operation.
- No labels