Images Page

Overview

The Images page is the main UI screen for managing logical images and their mapping to physical cloud images. It is reached by selecting the Images tab from the main menu. The Images tab is hidden unless your login is associated the WM_ADMIN role or the WM_IMAGE_MANAGER role (see OOB Groups, Roles, and Permissions). 

From the Images page you can:

  • View all logical images and their mappings to physical images
  • Add, edit, or delete image mappings
  • Add, edit, delete, or share logical images

The Images page appears in the figure below.

The page consists of a list of rows with each row representing a logical image. If a logical image has any mappings to physical images, an expand icon appears to the left of the image name and the number of mappings defined for that image is displayed to the right of the image name.

Once you add a public cloud in Workload Manager and add regions to that cloud, for each OOB logical images, Workload Manager automatically creates the image mapping for that logical image to the corresponding physical image in that region. This is done based on data maintained by Cisco and stored in the Workload Manager public package store. No user involvement is needed to create these mappings.

All logical images are tenant owned objects. The OOB logical images are owned by the root tenant and are automatically shared with all subtenants.

Add an Image Mapping

You must manually add an image mapping to a logical image to support either of these two cases:

  • Any physical image on a private cloud.
  • Any custom physical image on a public cloud. This includes all Pre-bootstrapped Images.

    If your custom physical image does not correspond to one of the Workload Manager OOB logical images, you must first create a new logical image corresponding to your custom physical image. To do this, follow the instruction to add a logical image, below. If your custom image is a pre-bootstrapped image that does correspond to one of the OOB logical images, do not create a new logical image; instead, use the existing OOB logical image.

To add an image mapping to an existing logical image listed in the Images page, follow this procedure.

  1. Hover over the row for the logical image. An Add Mapping button will appear on the right side of the row. Click it. This brings up the Add Cloud Mapping dialog box as shown in the figure below.

  2. Select the cloud region from the dropdown. Only cloud regions already defined and not currently having an image mapping for this logical image will be displayed in the dropdown.
  3. Enter the physical cloud image ID. To ensure you are specifying the correct image ID, use the guidance below depending on the cloud provider.

    •  VMware vCenter Image ID

      <VM name >/<snapshot name>

      You have two options to configure the Image ID for VMware:

      • Snapshot: If using snapshots, add a folder in vSphere (to store your Workload Manager snapshots), name it CliqrTemplates, and add this snapshot to the CliqrTemplates folder.

      • Template: You can alternately use template names to configure the cloud image. In this case, specify the name of a VM or template as the image ID on the VMware console and the systems always performs a full clone to either a specified datastore or datastore cluster. Add this Template to the CliqrTemplates folder.

      The full clone is performed on the source VM or VM template, the cloned VM can be on either datastore or datastore cluster that user specifies.

      See VMware Configurations for additional context.

    •  OpenStack Image ID

      • QCOW2 Image ID (sample ID mapping highlighted in the following screenshots):


      • Create, customize, and deploy a VM using the required image.

      • Shut down the VM instance and clone the instance.

    •  Google Image ID

      In Google Cloud, launch a VM for the Workload Manager instance and click REST at the end of the page. You can view the sourceImage value in the REST output.

      {
          "disks": [{
              "type": "PERSISTENT",
              "boot": true,
              "mode": "READ_WRITE",
              "autoDelete": true,
              "deviceName": "instance-1",
              "initializeParams": {
                  "sourceImage": "https://www.googleapis.com/compute/v1/projects/centos-cloud/global/images/centos-7-v20160418",
                  "diskType": "projects/x-signifier-537/zones/us-central1-f/diskTypes/pd-ssd",
                  "diskSizeGb": "10"
              }
          }]
      }

      The following procedure allows you retrieve the image details using the source to map the Workload Manager image as Google Cloud Platform's dynamic bootstrapping feature allows you to temporarily access an earlier version of the image by using the REST source details.To  using this method, follow this procedure.

      1. Access the Google Cloud Platform Compute Engine page and click the Create Instance link.

      2. In the Create an instance page, click Change in the Boot Disk field.
      3. Select one of the following options (dynamic bootstrapping is available for these options) as required for your environment and save your change: CentOS6 or 7, Ubuntu 14:04, Redhat Enterprise Linux 6 or 7, Windows 2008 or 2012

      4. Back in the Create an instance page, click the REST link. The Equivalent REST request is displayed in the resulting popup.

      5. Scroll down to the sourceImage line and select the key displayed in this line.

      6. Copy this key and paste it in the Image ID field in the Workload Manager UI's Image Mapping page.
    •  AzureRM Image ID

      In AzureRM, the following command output (latest version) provides the Image ID required by the Workload Manager. Refer to https://docs.microsoft.com/en-us/azure/virtual-machines/linux/cli-ps-findimage for additional context.

      1. Standard AzureRM Image – The following example queries all CentOS 7.2 images, the Image ID of the latest version is OpenLogic:CentOS:7.2:7.2.20170105.

        $ az vm image list -p OpenLogic --offer CentOS --sku 7.2 --all | more
        [
          {
            "offer": "CentOS",
            "publisher": "OpenLogic",
            "sku": "7.2",
            "urn": "OpenLogic:CentOS:7.2:7.2.20160303",
            "version": "7.2.20160303"
          },
          {
            "offer": "CentOS",
            "publisher": "OpenLogic",
            "sku": "7.2",
            "urn": "OpenLogic:CentOS:7.2:7.2.20160308",
            "version": "7.2.20160308"
          },
          {
            "offer": "CentOS",
            "publisher": "OpenLogic",
            "sku": "7.2",
            "urn": "OpenLogic:CentOS:7.2:7.2.20160620",
            "version": "7.2.20160620"
          },
          {
            "offer": "CentOS",
            "publisher": "OpenLogic",
            "sku": "7.2",
            "urn": "OpenLogic:CentOS:7.2:7.2.20161026",
            "version": "7.2.20161026"
          },
          {
            "offer": "CentOS",
            "publisher": "OpenLogic",
            "sku": "7.2",
            "urn": "OpenLogic:CentOS:7.2:7.2.20170105",
            "version": "7.2.20170105"
          },
          {
            "offer": "CentOS",
            "publisher": "OpenLogic",
            "sku": "7.2n",
            "urn": "OpenLogic:CentOS:7.2n:7.2.20160629",
            "version": "7.2.20160629"
          }
        ]
      2. Custom AzureRM Image:

        Image ID depends on the CloudCenter cersion

        The Image ID differs based on the Workload Manager version – use the Resource ID of the image as Image ID (as it includes the new Azure SDK).

        Managed Store Options

        To launch custom AzureRM images, you must select one of the managed storage options listed (Premium or Standard).

        See Multiple Volumes > AzureRMType Nuances for additional context.


        1. The following screenshot displays the Image ID retrieval screen via the AzureRM UI.
        2. The following screenshot displays the Image ID retrieval via the AzureRM CLI.

    •  AWS Image ID

      In AWS, the Image ID is the exact name displayed in the Machine Image (AMI) page in the AWS cloud portal.


  4. Expand Advanced Instance Type Configuration and add or remove instance types as needed.
  5. Click Save to save the changes and close the dialog box. The new mapping will be displayed in the list of cloud mappings for that logical image.

Edit or Delete an Image Mapping

Once a mapping has been added to a logical image, if the image is owned by your tenant, you can edit it or delete it.

From the row of the logical image of interest, click the expand icon to reveal the list of current cloud image mappings for that logical image. The list of mappings will appear as shown in the figure below.

To delete a mapping, hover over the row for that mapping to cause the trash icon to appear on the right side of the row. Click the trash icon, then acknowledge the confirmation message to delete the mapping.

To edit a mapping, click on the name of the associated cloud region. This causes the Edit Cloud Mapping dialog box to appear. This dialog box is similar to the Add Cloud Mapping dialog box except the cloud region cannot be changed. Adjust the image ID and allowed instance types as needed and click Save. 

Add a Logical Image

If you need to deploy a custom physical cloud image that does not correspond to any of the OOB logical images, you need to add a new logical image and then map that new logical image to the custom physical image on your cloud of choice. To create a new logical image from the Images page, follow this procedure.

  1. Click the Add Image button in the upper right of the page. This causes the Add a New Image dialog box to be displayed as shown in the figure below.

  2. Enter values for image name, number of network interfaces, and OS type. Then set the toggle to enable the image.

  3. Click Save to save the image and close the dialog box. The newly added image is now displayed as the list of logical images.

  4. Add the necessary cloud mappings to the image as explained above in Add an Image Mapping.

Edit or Delete a Logical Image

If a logical image is owned by your tenant, you can edit it or delete it.

To delete a logical image, hover over the row for that image to cause the menu dropdown icon to appear on the right side of the row. Then, click the dropdown icon and select the delete command.  Acknowledge the confirmation message to delete the mapping.

Use caution when deleting logical images. Any services associated with a deleted image will stop working. And any users in subtenants that were depending on those logical images will no longer have access to them. If you are the root tenant administrator you also have the ability to delete the OOB logical images. Use extra caution when deleting an OOB logical image as that would break the OOB services that use that image.

To edit a logical image, hover over the row for that image to cause the menu dropdown icon to appear on the right side of the row. Then, click the dropdown icon and select the edit command.  This dialog box is similar to the Add a New Image dialog box except the image name cannot be changed. Adjust the number of network interfaces, OS type, and the Enable toggle as needed and click Save. 

Share a Logical Image

If a logical image is owned by your tenant, you can share it with users, groups or subtenants, giving them view access. All OOB logical images are automatically shared with view access with all subtenants.

To share a logical image from the Images page, follow this procedure. 

Hover over the row for that image to cause the menu dropdown icon to appear on the right side of the row. Then, click the dropdown icon and select the share command.  This causes the Access Control List dialog box to be displayed.

From the dialog box, select the users, groups, and/or subtenants to share this image with. See Permission Control for additional context.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks