// removed jquery ui css and js

Cloud-Specific Nuances to Install Infrastructure

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
      VIP
      {    
          "Version": "2012-10-17",
              "Statement": [{        
              "Action": [            
                  "ec2:AssignPrivateIpAddresses",             
                  "ec2:UnassignPrivateIpAddresses",             
                  "ec2:DescribeInstances",             
                  "ec2:DescribeNetworkInterfaces"
              ],
                      "Effect": "Allow",
                      "Resource": "*"    
          }]
      }
      EIP
      {    
          "Version": "2012-10-17",
              "Statement": [        {            
              "Action": [                
                  "ec2:DescribeInstances",                 
                  "ec2:DescribeNetworkInterfaces",                 
                  "ec2:AssociateAddress",                 
                  "ec2:DisassociateAddress",                 
                  "ec2:DescribeAddresses" 
              ],
                          "Effect": "Allow",
                          "Resource": "*"        
          }    ]
      }

Azure Nuances

  •  Azure RM
    1. Launch a CentOS VM in Azure RM 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.
  •  Azure Classic
    1. Launch a CentOS VM in Azure Classic 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. Register the CCO with the metadata server.

      curl-XPOST-d"info={\"userData\":\"Azure,<CCM_IP>\",\"image\":\"ccm\",\"machineType\":\"large\",\"osName\":\"Linux\",\"tenant\":\"admin\"}"-k
       https://mds.cliqrtech.com/0.1/meta-data/Azure/<CCO_HOST_NAME>
    5. Verify the registration by issuing the following command – it should return the data from the step above:

      curl http://mds.cliqrtech.com/0.1/meta-data/Azure/<CCO_HOST_NAME>
    6. See Configure Cloud(s) > Configure an Azure Classic Cloud for additional context.

  •  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. Use the core installer package to setup CCO as listed in Per Cloud Region (Required) > CCO (Required).
    4. Register the CCO with the metadata server.

      curl-XPOST-d"info={\"userData\":\"AzurePack,<CCM_IP>\",\"image\":\"ccm\",\"machineType\":\"large\",\"osName\":\"Linux\",\"tenant\":\"admin\"}"-k
       https://mds.cliqrtech.com/0.1/meta-data/AzurePack/<CCO_HOST_NAME>
    5. Verify the registration by issuing the following command – it should return the data from the step above:

      curl http://mds.cliqrtech.com/0.1/meta-data/AzurePack/<CCO_HOST_NAME>
    6. See Configure Cloud(s) > Configure an Azure Pack Cloud for additional context.

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.

Dimension Data Nuance

 Configuration Requirements
 Be sure to address the following requirements:

Google Nuances

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

    • If using the XPN network feature, you also required XPN Admin permissions (see https://cloud.google.com/compute/docs/xpn/provisioning-xpn 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

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.
    2. Launch the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE VMs
  •  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>`
    3. Get the Port IDs of the MGMTPOSTGRES_MASTER and MGMTPOSTGRES_SLAVE VMs:

      `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, CCM_SA_PRIMARY.mydomain.com.

    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> 127.0.0.1

  •  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 ccm.example.com and it’s behind a NAT, and the internal private IP address is 12.16.0.5 and its external public IP address is 54.1.2.5, then enter the following line in the local /etc/hosts file

    12.16.0.5 ccm.example.com

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

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.

VMware Nuances

 vCenter

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
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

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

  • No labels
© 2017 Cisco Systems