CliQr is now part of Cisco Learn More About Cisco

Configure Image IDs

Overview

Cloud Nuances for Image ID

The Image ID terminology differs between clouds:

  •  VMware Image ID

     <VM name >/<snapshot name>

    If using snapshots, add a folder in vSphere (to store your CloudCenter snapshots), name it CliqrTemplates, and add this snapshot to the CliqrTemplates folder.

    You can alternately use VM template names to configure the cloud image. In this case, specify the name of a VM or VM 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.

    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 example):

  •  Amazon Image ID

     Automatically handled by CloudCenter.

  •  Azure Classic Image ID

    In Azure Classic, the application VM image mapping name is a disk name that you must retrieve by clicking the Virtual instances > Image tab and copying the NAME listed in the vhds section highlighted in the following sample image:

  •  Azure RM Image ID

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

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

  •  Google Image ID

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

    The following procedure allows you retrieve the image details using the source to map the CloudCenter 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 12.04 or 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 CCM UI's Image Mapping page.

Download and Import the Base OS Image and Retrieve Image ID

To retrieve the Image ID for the worker appliance, follow this procedure:

  1. Download the OVA or QCOW2 files file from software.cisco.com to the /tmp folder. See Installation Overview > Installation Download Details for additional context.
  2. Retrieve the Image ID for the worker appliance. You need this Image ID to Map Images in the CCM UI.