CliQr is now part of Cisco Learn More About Cisco

VM (Node) Name Configuration

Instance Naming Strategy

Icon

If you make changes to the callouts or attributes for a Cloud Region, you must restart the CCO for the changes to take effect.

If you make changes to the macro replacements for a Cloud Region, you must re-register the CCO with the CCM for the changes to take effect.

You can configure the Instance Naming Strategy to identify callouts using a standard strategy for some clouds:

You can use one of the following options:

OptionsDescriptionSupported Clouds
DefaultThe default value provided by Cisco. A predefined token prefixed with cqjw-
CliQr Macro Replacement

Marcos specified in the Node Name Config field are set as the instance name. If you choose this strategy, you must also configure the Node Name Config field to rename a VM (node) using this macro.Your must first define the macros before specifying them.

Icon

You must restart the CCO for the Node Name Config macro to take effect.

Predefined Macros Requirements for the Node Name Config Field

Hostname Callout

Predefined Macros Requirements for the Node Name Config Field

The VM name should meet the following requirements for a job submission to succeed

  • Only contain the following characters:
    • a to z (lowercase only)  
    • 0 to 9
    •  The - (hyphen)
  • Start with an alphabet
  • Cannot end with - (hyphen)

The predefined macros that you can use for the CliQr Macro Replacement Option are listed in the following table:

NameValue
%os1%First character of OS type string in lower case
%os2%First two character of os type string in lower case
%OS1%First character of os type string in upper case
%OS2%First two character of os type string in upper case
%RND<number>%

Fixed length random string, e.g., %RND10%, 10 character long random string

Icon

This is a mandatory field, only values in the range : %RND6% to %RND11% or just %RND% which defaults to %RND6%"

%UID%User ID
%VID%Vendor ID
%VM_PREFIX%

VM name prefix must be added as a global parameter in the app profile

Icon

Only macro whose value can be user customized

Instance IPAM Strategy

Icon

If you make changes to the callouts or attributes for a Cloud Region, you must restart the CCO for the changes to take effect.

Administrators can configure IPAM callouts at the cloud region level for VMware, AWS, and OpenStack clouds using one of two options:

OptionsDescription
No IPAMThis instance does not use IPAM callouts.
IPAM CalloutIf you select this option,
  • You must ensure that the IPAM callout is configured on the CCO (see Callout Scripts or InfoBlox for additional context).
  • The VMs will launch with IPs as configured by the IPAM callout.

VMware Customization Spec

VMware's  OS customization Spec feature allows you to configure network settings in vSphere (the VMware console). The CloudCenter platform allows you to specify the name of the Customization Spec (already created on the VMware vShpere console), in the IPAM callout script. To specify this spec, select IPAM Callout in the Instance IPAM Strategy field.

If you set the VMware IPAM strategy as IPAM Callout, you have multiple options.

  • Use it to indicate the IPAM Callout in the table above and the CloudCenter platform completes the Static or Dynamic IP configuration.
  • Specify the Name of the Customization Spec in the Callout script.
    • If the CloudCenter platform detects the value in the custSpec key, then it ignores all other settings.
    • To specify the Name of the Customization Spec in the Callout script, ensure that the IPAM Callout script contains the following key-value pair:
      custSpec=CustSpec101

See Callout Scripts for additional details on the IPAM callout script.