CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Cloud-Specific Nuances to Install Infrastructure


Public Clouds

Alibaba Nuances

  •  What Instance Types are available for each Alibaba region??

    The instances supported for each region differs from region to region. The Alibaba SDK and the Alibaba Web Interface differs in the instances listed for each zone. You can add new instances using the CCM UI – see Manage Instance Types for additional context. 

  •  What Storage Types are Supported?

    The CloudCenter platform supports two storage types for Alibaba clouds:

    • SSD Cloud Disks

    • Ultra Cloud Disks

  •  Can I SSH into Alibaba Cloud Environments?

    As SSH key access is not allowed into Alibaba cloud environments, you must provide the instance password as follows:

    • Linux: Provide the root password.

    • Windows: Provide the administrative password.

    See Deployment Environment Defaults Alibaba - Cloud and Network Settings for additional context.

AWS Nuances

  • For CCO, CCO_PRIMARY, CCO_SECONDARY, and CCO_TERTIARY, launch the CCO VMs using IAM Roles if you intend to use IAM role-based accounts for your provisioning.
    •  Choose Virtual IP or Elastic IP

      Guidelines to use VIP or EIP for the IAM Role for database HA:

      • Use VIP:
        • If you launch both the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE from the same VPC.
        • If using VIP, choose an unused IP from one of the subnets within the VPC
      • Use EIP:
        • If you launch both the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE from different VPCs.
        • If using EIP, allocate a new IP from the AWS cloud console with scope as VPC.
        • See VPC peering for additional context.
    •  Create an IAM Role Specific to a VIP or EIP Policy
      PolicyIAM Role
          "Version": "2012-10-17",
              "Statement": [{        
              "Action": [            
                      "Effect": "Allow",
                      "Resource": "*"    
          "Version": "2012-10-17",
              "Statement": [        {            
              "Action": [                
                          "Effect": "Allow",
                          "Resource": "*"        
          }    ]

AzureRM Nuances

  •  AzureRM
    1. Launch a CentOS VM in AzureRM mode.

    2. Add the required endpoints to configure your CCO as listed in Phase 2: Configure Firewall Rules.

    3. Use the core installer package to setup CCO as listed in Per Cloud Region (Required) > CCO (Required).

    4. See Configure Cloud(s) > Configure an Azure Resource Manager Cloud for additional context.

Dimension Data Nuance

  •  Configuration Requirements

    Be sure to address the following requirements:

Google Cloud Nuances

  •  Configuration Requirements
    • A valid Google Cloud Platform account with Project Owner permissions

    • If using the Shared VPC network feature, you also required Shared VPC Admin permissions (see for additional context).

    • The CloudCenter platform appends the network name with an unique ID to form the firewall rule name, the network name can be a maximum of 24 (network name) + 39 (unique ID) = 63 total characters. For example: abcdefghijklmnopqrstuvwx-c3f-462828f37a06acd3ee194716bfe10de0

    • Enable the following APIs for each Google cloud account where you will be adding to CloudCenter platform:

      • Google Compute Engine API

      • Google Cloud Resource Manager API

IBM Bluemix/SoftLayer Nuances

  •  Before You Launch the CCO Instance...

    You MUST launch the CCO in the same cloud region as the SoftLayer device – you cannot select different regions for the CCO and this device.

    See Configure Cloud(s) > Configure a SoftLayer Cloud for additional context.

Private Clouds and Datacenters

Azure Pack Nuances

  •  Azure Pack
    1. Launch a CentOS VM in Azure Pack mode.

    2. Add the required endpoints to configure your CCO as listed in Phase 2: Configure Firewall Rules.

    3. See Configure Cloud(s) > Configure an Azure Pack Cloud for additional context.

Azure Stack Nuances

  •  Azure Stack (Effective CloudCenter 4.9.0)
    • CloudCenter does not support the following features for Azure Stack deployments.

      • Multiple NICs

      • Managed disks

      • VM Extensions

    • The CloudCenter platform supports both Azure Stack Development Kit and Azure Stack Integrated Setup models.

    • When configuring the CCM:

    • When configuring the CCO:

      • This setup requires self-signed certificates for each endpoint to connect to the CCO and must be saved o the CCO sever.

      • If you cannot directly access the endpoint, your setup must be able to access NATted IPs in the /etc/hosts file. To do this, access the etc folder and the edit hosts file. Add a line to the file for each website and save the hosts file. Here are some sample lines:


        If you set up your DNS server accurately, you may not need these lines added to the hosts file.

      • You  may also need to add your <yourDiskName>.blob.local.azurestack.external website to the hosts file:

      • You may need to change the bootstrap timeout properties in the CCO server to address the time required to complete this configuration.

  • See Sample Azure Stack Appliance Setup if you prefer to convert an existing CCO to an Azure Stack-specific CCO.

Cisco UCSD Nuances

  •  Cisco UCSD Release Compatibility

    See Datacenters and Private Clouds for the UCSD releases supported by the CloudCenter platform

  •  Configuration Requirements
    • If you intend to integrate UCSD in your enterprise, the CloudCenter platform requires access to the UCSD environment to provide end-to-end deployment.

    • One CloudCenter platform supports one UCSD instance.

    • Each CloudCenter UCSD implementation requires an associated physical image entry in the CloudCenter platform (this is a dummy placeholder – even if a logical Image is not used).

    • See Configure Cloud(s) > Configure a Cisco UCSD Cloud for additional context.

OpenStack Nuances

Launch VMs for the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE (see Installation Overview) with a Virtual IP (VIP) for the Master-Slave setup.

  •  Access to Openstack Neutron client installed on VM with access to OpenStack server
    1. Install the OpenStack Command Line Client.


  •  Update Ports
    1. Identify an unused IP for the VIP master-slave setup.

    2. Create a new port with this IP using the following command;

      `neutron port-create --fixed-ip ip_address=<VIP> <network-name>`

      `neutron port-list`
    4. Note the id from the list corresponding to the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE IP in fixed_ips.

    5. Update ports associated to MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE with the VIP by running the following command for each Port ID that you noted in the previous step.

      `neutron port-update <port-id> --allowed-address-pairs type=dict list=true ip_address=<VIP>`
  •  Setup Hostname

    For all launched VMs, update the hostname to the desired hostname. Select a hostname that matches the role. For example,

    The hostname cannot contain underscore for the database servers as it causes the PCS authentication to fail.

    Changing the hostnames after you install and configure the VMs may cause unknown issues.

  •  Setup hostname resolution

    Once you update the hostname,  ensure that the VM hostname is resolvable by running the following command:

    hostname -i

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

  •  Network routing loopback

    Network Routing Loopback refers to CCM(s) that are are behind the NAT for a given deployment and have a restriction that servers from an internal network cannot use External IPs to access the CCM.

    In this scenario, you must add a line to the registered CCO and AMQP server's /etc/hosts file to provide the internal private IP of the CCM.

    For example:

    If the CCM DNS name is and it’s behind a NAT, and the internal private IP address is and its external public IP address is, then enter the following line in the local /etc/hosts file

    The hostname used above ( must match what is configured as Public DNS while configuring CCM in Phase 4.

VMware vCenter Nuances

  •  vCenter

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

    vCenter ObjectRequired PermissionReason
    NetworkAssign NetworkIf the default network in a template/snapshot must be changed

    Allocate space

    For persistent disk operation

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

    Apply recommendation

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

    Create task

    For VM operation

    Update task
    Virtual MachineAll permissions

    See Configure Cloud(s) > Configure a VMware Cloud for additional context.

Container Clouds

Kubernetes Nuances

  •  Kubernetes (Effective CloudCenter 4.9.0)

    CloudCenter does not support the following features for Kubernetes deployments.

    • Multiple regions

    • Storage types

    • IPAM and VM naming callout

    • Logical image mapping in region

    • Deployment suspend/resume

    • Container power on/off/reboot

    • Node initialization

    • Override of instance type cost-based on image

    • Aging and Suspension Policies

    • Reporting

    • Billing

    The following Kubernetes-specific configurations are required BEFORE you launch the CCO instance:

    • A separate service account with the default namespace.

      #kubectl create serviceaccount myacc
      #kubectl create clusterrolebinding <name> --clusterrole=cluster-admin --serviceaccount=default:<myacc>
    • An existing ClusterRoleBinding on the API server – this role is not the same as the token used for authentication (see the Kubernetes Documentation for additional details) and is required by the CloudCenter platform to make API calls to Kubernetes if ClusterRoleBinding is present in the default namespace for the Kubernetes service account:

      kubectl create clusterrolebinding <name> --clusterrole=cluster-admin --serviceaccount=default:default
  • See Convert to a Kubernetes-Specific CCO if you prefer to convert an existing CCO to a Kubernetes-specific CCO.

Terms & Conditions Privacy Statement Cookies Trademarks