Identifying Cloud Image IDs


In order to map the OOB Base OS Images to private cloud physical images, or to map your custom logical images to physical images in any cloud provider, you must identify the corresponding physical image's 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 > AzureRM Type 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.




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