Map Images

Terminology

TermDefinition
ImageA snapshot of a base OS or an application running on a cloud instance or server.
Base OS imageCloud-agnostic logical images provided by the Workload Manager to model applications as listed in OOB Base OS Images.
Logical imageThe part of an application profile that describes artifacts needed to natively deploy the application. Refers to physical images that are stored in repositories.
Physical imageApplication files, packages, and scripts that are used to natively deploy the application. Referenced by logical images in application profile.
Custom imageAny customer created image.
Worker imageApplication VM images are also referred to as Worker images. Both terms refer to the Linux and Windows machine images. See Pre-bootstrapped Images (Conditional) for additional context

Methodology

The method of mapping logical images to physical images depends on the cloud provider and whether the logical image is an OOB image or a custom logical image specified by you.

  • There is rarely a need to manually map OOB Base OS Images to physical images in public cloud regions. Workload Manager does this automatically when you create the region in the CloudCenter Suite suite. A use case where you might want to override the default mapping and create a different mapping, is if you know of a more recent minor release of an OS that is currently available in the region.

    OOB Base OS image mapping is not automatically performed for AWS Govcloud regions. FOr all AWS Govcloud regions you must manually map the Workload Manager OOB base images to the corresponding physical images in the AWS Govcloud region.

  • For private VM-based clouds, you must manually map the OOB Base OS Images to physical images that you import into the private cloud.
  • For custom logical images, regardless of whether the physical image resides in a public or private cloud, you must manually map the custom logical image to the physical images. For public clouds, the physical image could be one you imported yourself or one that was shared with your account from someone else. For private clouds the physical image is always imported.

All VM-based Services are based on a logical images. If a service's logical image is not properly mapped to the correct physical cloud image for a particular cloud region, that service will not be available for deployment in that cloud region.

To manually map Workload Manager logical images to physical images, you can use the Regions tab method (see below) or the Images tab method.

Regions Tab Method

To map Workload Manager VA base image IDs to the Workload Manager platform's logical image name, follow this procedure:

  1. Click the Admin link displayed in the Workload Manager UI main menu.

  2. Click the Cloud tab in the side panel to display the Cloud Configurations page.

  3. On the right side of the Cloud Configuration page, look for the name of the region where you want to map images and click on the link with the name of the region. This takes you to the Regions tab.

  4. Scroll down to the Configure Image Mappings section and click Add Mapping for the required Workload Manager base OS images. For example:

    • CentOS 7

    • RHEL 7

    • Ubuntu12.04

  5. Clicking Add Mapping brings up the Add Cloud Mapping dialog box. 


    Enter the Cloud Image ID provided by your cloud provider, then click on the ">" symbol to expand the Advanced Instance Type Configuration menu.

  6. Deselect any instance types you do not want to allow and click save.

Images Tab Method

See Cloud Mapping for Images.

Service Mapping Changes

By default, all services in the Services tab are mapped to CentOS 6 or RHEL 6 images.

Note

If you use any other image in your Workload Manager deployment, you need to explicitly identify the applicable image in the Workload Manager UI.

To map the service changes, follow this procedure:

  1. Click the Admin link in the Workload Manager UI main menu.

  2. Click the Services link

  3. Edit the service applicable to your deployment.

  4. In the Edit Service page, verify the Supporting Images field setting.

  5. Change the selection to the image used in your environment.

  6. Click Save.

Sync Image Mappings

To perform this procedure, you must have access to the Cisco hosted package store or have a Local Package Store (Conditional).

To sync image mappings, follow this process:

  1. Configure a cloud as specified in Configure a Cloud End-to-End

  2. When the Region Connectivity section of the Regions tab displays the Running status, click Sync Image Mappings.

  3. The Regions tab updates to display the synced status.


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