Sample VMware Appliance Setup

To prepare infrastructure using CloudCenter appliances for VMware clouds, follow this process.

  1. In the VMware Console, create a folder named CliqrTemplates and import the OVA file for each CloudCenter component. See Virtual Appliances > VMware for a list of available OVA files.

  2. Prepare to launch the image for each component:

  3. Launch the instance for each component using the imported images.
  4. After you launch the instance for each image:

    1. Power on the image.

    2. Log into the image as the root user:

      Username: root
      Password: welcome2cliqr
      sudo -i


      Before you proceed

      This authentication uses generic credentials – be sure to change the email address and password for the admin account after your first login.

  5. Setup hostname – For all launched VMs, update the hostname. Choose a hostname that matches the Virtual Appliance Overview > Role. For example:

    1. hostname – For all launched VMs, update the hostname.

      Don't change the hostname after you install and configure a component as it may cause unknown issues.

      Choose a hostname that matches the Role. For example:

      Example
      CCM.mydomain.com
    2. Setup the hostname resolution – Once you update the hostname, ensure that the VM host name is resolvable by running the following command

      1. hostname -i

      2. If the VM name is not resolvable, edit the file /etc/hosts and add your VM’s hostname.
        For example:

        Example
        <hostname> 127.0.0.1
    3. Network routing loopback:

      1. Refers to deployed CCMs that are running behind the Network Address Translation (NAT).

      2. This setup places a restriction on machines from internal networks to ensure that they do not use an external IP to access the CCM.

      3. To address this restriction, you must add a line to the CCO and AMQP server's /etc/hosts file and include the internal private IP of the CCM. For example: If the CCM DNS name is ccm.example.com and it is behind a NAT, and the internal private IP address is 192.168.20.5 and its external public IP address is 54.16.20.5, then enter the following line in the local /etc/hosts file:

        Example
        192.168.20.5 ccm.example.com

        When configuring the CCM, the hostname used above (ccm.example.com) must match what you configure as the Public DNS.

    4. Create the CloudCenter-Specific Checker JSON file:
      After you setup the infrastructure for all the CloudCenter components, create a CloudCenter Checker JSON file that lists all the CloudCenter components with their modes and the IP address that correspond to infrastructure elements for each mode and role. This Checker JSON file will be used for network compliance check (see Phase 3 in the CloudCenter Installation process).

      The overall file structure will depend on factors like modes of various components, number of cloud regions, use of conditional/optional components and repos etc. Also, the region names used in the file should be unique, but do not need to match up with any cloud or datacenter names. These strings are merely used to perform network compliance checks and report results.

Back to: Virtual Appliance Process

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