Configure a vCD Cloud

Be aware that these screen captures may change based on the vCD changes. They are provided in this section as a point of reference.

Prerequisites

Before mapping a vCD cloud on the CloudCenter platform, verify the following requirements:

  • A valid vCD cloud account.

  • Launch the CCO in the same cloud region as the vCD cloud.

  • Follow this procedure to enable the vCD cloud provider in the CCO server – If you use the vCD cloud, you must configure the CCO servers.  

    To enable the vCD cloud provider in the CCO server, follow this procedure.

    1. Copy the rest-api-schemas-8.10.0.jar  and vcloud-java-sdk-8.10.0.jar files to the /usr/local/tomcat/webapps/ROOT/WEB-INF/lib directory.

      Customers must use their copy of these libraries as these copies are not redistributable by Cisco. The 8.10.0 version is required

    2. Configure vCD.

      1. Change to the following directory.

        cd /usr/local/osmosix/bin directory


      2. Run vcdconfig.
        If the vcdconfig file does not exist, download the file from software.cisco.com. See Installation Overview for additional context.

      3. At the Please enter cloud type: prompt, provide the cloud name and region name that you determined when you performed the site assessment and press Enter.
        Use the following format to enter this information.
        CloudName-RegionName.

        Make sure to enter this information accurately because it cannot be changed after it is configured.

        For example,

        1. For vCD:
          vCloud-CliQrWest; f

        2. For vCloud Air:
          VCoudAir-CliQrWest

      4. At the Please enter Org VDC shared network (comma separated multiple string supported): prompt, enter the vCloud OrgVdc Shared Network information that you determined when you performed the site assessment, and then press Enter. Separate multiple entries with a comma but no spaces.

        For example, orgnet1,orgnet2.

      5. At the Please enter storage profile (comma separated multiple string supported): prompt, enter the Storage Profile information that you determined when you performed the site assessment, and then press Enter.
        Separate multiple entries with a comma but no spaces.
        For example, tier1,tier2,tier3.

      6. At the Please enter CCM address: prompt, enter the IP address of the CCM server.

      7. At the Please enter CCO private address: prompt, enter the private IP address of the CCO server that you are logged in to, and then press Enter.
        For example, 10.0.2.1.

      8. At the Please enter CCO public address: prompt, enter the public IP address of the CCO server that you are logged in to, and then press Enter.
        The configuration tool displays the information that you entered and generates the required files.

    3. Restart the Tomcat server so the CCO server automatically uses the vcloud-java-sdk and rest-api-schemas jar files.

Configuration Process

To configure the logical mapping for a vCD cloud, follow this procedure.

  1. Access the CCM UI > Admin > Clouds > Add Cloud in the side pane.
     
  2. Select the VMware vCloud Director option, provide a Name and Description for this cloud, and click Save.
  3. Locate the newly-added cloud and click Add Cloud Account to add an account for this cloud family. The Add Cloud Account popup displays.

    1. Assign a new cloud Name.

    2. Select the check box to Track Cloud Costs.
    3. Provide the vCD user details.

      Cloud Account DetailsDescription
      vCloud Organization NameThe vCloud organization to which this account belongs.
      vCenter Username/PasswordThe vCloud user name that you determined when you performed the site assessment.
      vCloud OrgVdcThe vCloud organization vDC that you determined when you performed the site assessment.
      vCloud OrgVdc Shared NetworkThe vCloud organization vDC shared network that you determined when you performed the site assessment.
      vCloud Isolated NetworkThe vCloud isolated network that you determined when you performed the site assessment.

      If vCenter users do not have full administrator rights, verify that each user (using CloudCenter) has the following permissions at a minimum:

      vCenter ObjectRequired PermissionReason
      DatacenterNetwork protocol profile configurationFor NSX security profile configuration
      NetworkAssign NetworkIf the default network in a template/snapshot must be changed
      Datastore

      Allocate space

      For persistent disk operation


      Browse datastore
      Low level file operations
      Remove file
      FolderCreate folderFor user folder creation
      Resource

      Apply recommendation

      For datastore cluster support
      Assign VM to resource poolFor resource pool selection
      Tasks

      Create task

      For VM operation

      Update task
      Virtual MachineAll permissions
    4. Click Save and verify that the newly added cloud is displayed in the Cloud Configurations page.
  4. Click the Regions tab to add a cloud region.

    1. Click Add Region.
    2. Select the required regions for this cloud.
    1. Add the Region Name and an optional Display Name for this cloud region.

      The Region Name must be the same as the Region Name provided in the vcdconfig file (referenced in the Prerequisites section above).

  5. Caution

    If you Edit Cloud Settings, you must save the changes to the CCO to ensure that these changes are also propagated to CCOs inside a firewall configuration.

    If your CCO is already configured, you must re-register the CCO for these Cloud Settings to take effect.

    FieldDescription
    vCloud Endpoint URL

    The base vCD URL.
    For example: https://vcd.example.com/

    The URL for org suffix is automatically added by the CloudCenter platform.

    vCloud RegionNot applicable – Effective CloudCenter 4.7.3.1, this field in no longer available.
    Log LevelNot applicable – Effective CloudCenter 4.7.3.1, this field in no longer available.
    Node Name ConfigSee VM Name Config for additional context
    vCloud Deployment Mode

    Effective CloudCenter 4.7.3.1, this field in no longer available.

    For earlier version, two modes are available: While 2 is the default, you must explicitly enter 2 in this field.
    • 1 = Obsolete and no longer supported by the CloudCenter platform – to address multiple vApp deployments made by the same user.
    • 2 = This is the default mode and the ONLY mode that is currently supported – to address new vApp deployments.
  6. To complete the cloud configuration, you must register the CCO with the CCM.

     Register the CCO with the CCM

    Register the CCO with the CCM


    Cloud Region Nuances

    Once you register a CCO with the CCM, the CCO only works for the registered cloud region.

    CloudCenter

    Once you register a CCO with the CCM, the CloudCenter platform considers this cloud region to be active and you can only delete the cloud region from the CloudCenter platform under specific conditions. See Cloud Region Configuration > Delete Cloud Region for additional details.

    Non-HA Mode

    To register the CCO with the CCM, follow this procedure:

    1. In the Configure Orchestrator popup, provide the CCO's IP address that is accessible by CCM and select the cloud account that is used to host the CCO:
    2. If you are not already at this page, verify that you are in the Admin > Clouds > Configure Regions for the required cloud)
      1. Click Configure Orchestrator in the Regions tab.
      2. Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.
      3. Remote Desktop Gateway DNS or IP: The IP address of the Guacamole server (enables browser-based access to the VMs). If the Guacamole component resides in the AMQP server, provide the IP address of the AMQP server.

      4. Cloud Account: Select the cloud account that you want to use with this CCO.

        Amazon Cloud Nuance

        This setting is important if you have configured an IAM Role. Be sure to select the cloud account that contains this role.

    3. Click Save. The CCM and CCO have now established a mutual trust relationship. The CloudCenter platform now manages the cloud region with the deployed CCO.

    4. Repeat Step 2 and Step 3 to establish a mutual trust between the CCM and other CCOs.

    You have registered the CCO VM and completed your configuration. You have two options at this point:

    HA Mode

    To register the CCO with the CCM, follow this procedure:

    1. Ensure that the Tomcat service is running on the Primary CCO.
    2. Login to the Secondary CCO and Tertiary CCO servers and stop the Tomcat service on both servers.

      /etc/init.d/tomcat stop
    3. Access the CCM UI and register the CCO using the CCO LB IP address.
      1. If you are not already at this page, verify that you are in the Admin > Clouds > Configure Regions for the required cloud)
      2. Click Configure Orchestrator in the Regions tab.
      3. Provide the CCO's IP address that is accessible by CCM and select the cloud account that is used to host the CCO:

        1. Orchestrator IP or DNS: Provide the IP or DNS address for the CCO server.
        2. Remote Desktop Gateway DNS or IP: The IP address of the Guacamole server (enables browser-based access to the VMs). If the Guacamole component resides in the AMQP server, provide the IP address of the AMQP server.

        3. Cloud Account: Select the cloud account that you want to use with this CCO.

          Amazon Cloud Nuance

          This setting is important if you have configured an IAM Role. Be sure to select the cloud account that contains this role.

        4. Click Save. The CCM and CCO have now established a mutual trust relationship. The CloudCenter platform now manages the cloud region with the deployed CCO.
    4. After a successful registration, log into the Primary CCO server.
    5. Copy the gateway_config.properties file from the Primary CCO's /usr/local/osmosix/etc/ folder to the same location on both the Secondary CCO and the Tertiary CCO servers.
    6. Verify that the ownership and permissions for the copied file in all servers is as follows:
      • Owner = cliqruser
      • Group Permission = read and write
    7. Run the following commands to change settings – if required:

      chown 
      cliqruser:cliqruser /usr/local/osmosix/etc/gateway_config.properties
      chmod 644 /usr/local/osmosix/etc/gateway_config.properties
    8. Restart the Tomcat on the Secondary CCO and the Tertiary CCO servers by issuing the following command on each server:

       /etc/init.d/tomcat start
    9. Repeat this procedure for other CCOs in HA mode to establish a mutual trust between the CCM and other CCOs.

    You have registered the CCO VM and completed your configuration. You have two options at this point:

     

  • No labels