VMware vSphere Installation


Trial User Installation Procedure and Settings

In some cases, you may merely want to try out the installation to check if it works. In these cases, try the installation with the following settings, regardless of your environment:

  1. Upload the tenant image manually to the root folder and prefix the file with CCS (all upper case) before you begin the installation.

  2. Do not convert the tenant image to be a template.

  3. If you are new to Cloud Center Suite, installing CloudCenter Suite for the first time in a VMware environment or if you not sure of your vSphere capacity, then select the following settings in the Placement properties page as follows to ensure a successful installation:

    Placement Properties FieldSettings and Description
    VM TemplateSelect the image uploaded in as mentioned in Step 1 above.
    Resource PoolCreate a new resource pool in your VMware environment and select this new resource pool.
    CIDR Network

    Placement properties has 2 types of networks: vSphere Network and Kubernetes POD CIDR.

    The values for both these networks must be different.

    If you select the same network for both settings, the installation will not succeed as the IP that is being assigned will be the same for both networks and thus cause a conflict.

    Master VIPMake sure it is available and not allocated to any other environment before entering the information in this field.
    Static IPMake sure all values are correct and the range is wide enough and available. The number of primary servers, workers, and load balancers must be included in this count.
    Number of worker nodes

    Reduce the Worker count to 2 (even if this field defaults to 5) for an environment that uses 8 CPU 32 GB memory. At a later point ( after your installation/registration is complete), you can increase this count by using the scale up procedure.

    DatastoreThe updated tenant image and the destination CCS_ image folder MUST have the same Datastore value – to verify this, note the datastore value when you upload the image and then use the same value to enter in this field.

The following Advanced sections are intended for users who would like to perform the installation using their environment-specific VMware settings.

Advanced Prerequisites

If you are using a proxy requirement, be sure to verify that the proxy does not have a username or password restriction.

If you have credentials in place, you will see a field validation error below each Proxy field.


The installation process assumes internet connectivity to certain domains.  When installing CloudCenter Suite into environments residing behind a proxy, please ensure the following domains are entirely accessible.  Remember the proxy information - this will be used during the installation of CloudCenter Suite.

Note: The Installer VM supports HTTP and HTTPS proxies, with or without username and password.  The proxy must support TLS 1.2.

Warning: Several of the following links might perform redirects.  Please ensure your proxy and firewall are configured to allow redirects of the following URLs. 

Proxy URLDescription

https://devhub.cisco.com

http://devhub.cisco.com

https://devhub-docker.cisco.com

http://devhub-docker.cisco.com

Repository for Cisco CloudCenter Suite Docker Charts

https://gcr.io

http://gcr.io

Repository for Cisco CloudCenter Suite Helm Charts

https://storage.googleapis.com

http://storage.googleapis.com

Repository for Cisco CloudCenter Suite Tiller Image
OtherThe Suite Installer may require additional connections to the installation environment (for example, vCenter, Hyperflex Data Platform, AWS Console, and so forth)  Please ensure your cloud target is reachable via the proxy!


A Note on Offline Clusters

In CloudCenter Suite 5.1 and earlier, if your environment has strict URL rules that redirects (for example, using a shorter URL that redirects to https://storage.googleapis.com) the configured URL, you may not be able to complete the installation as these kind of redirects may not be allowed if you have installed the repository in an offline cluster. As the offline solution is not completely air gapped in CloudCenter Suite 5.0 and 5.1, you must added these URLs to your allowed lists behind the firewall so you can access these sites.


Advanced VMware Nuances

Verify the following VMware nuances:

  • Ensure to use Version 6.0 and higher.

  • Verify that you have sufficient shared storage between hosts.

  • You must have privileges to launch a VM and access the selected DC/Datastore.

  • The datastore clusters are not supported

  • The vSphere datastore must reside outside the datastore cluster.

  • If vSphere is slow:

    • Upload the VM template manually – in the same datastore where you are going to install CloudCenter Suite.

    • Initially select fewer number of workers than suggested – for example, if 5 workers are recommended, just enter 2 instead of 5. This helps prevent a timeout issue when the workers are being created.

    • After the installation completes, login to CloudCenter Suite as the root tenant (admin) user, click on the Cloud Management icon, and scale up the worker node.

    • Static IP Consideration – Verify that you have sufficient IPs available in the Static IP range provided during installation for scale up.

  • If vSphere has more than one datacenter, be sure to:

    • Create and select one resource pool, do not leave this resource pool selection blank.

    • Upload the tenant image manually to vSphere, under root folder as provided in the following procedure.

      • Download the tenant image tar.gz file from software.cisco.com.

      • Extract the tenant image. The extracted folder contains the tenant image, rename it by including a CCS prefix. For example: ccp-tenant-image-1.13.5-ubuntu18-4.1.1.ova, rename it to CCS-tenant-image-1.13.5-ubuntu18-4.1.1.ova

      • Next, upload this renamed image to your root folder, make sure to select the same data store where you will be installing CloudCenter Suite.

      • The image will be displayed in the VM Template dropdown of the Placement Properties page.

      • Be sure to verify that the image is not converted to the template after uploading to vSphere.

  • If vSphere has only one datacenter, then it is not mandatory to select a resource pool.

  • Your datacenter must exist at the root level.

    Be aware that CloudCenter Suite does not support folders at the root level.


  • Network Time Protocol (NTP) must be configured – this is important as the CloudCenter Suite installation can fail, if NTP is not configured or if it is wrongly configured.

    If you setup CloudCenter Suite in offline mode, you must provide valid NTP server details before you save your configuration.

  • For CloudCenter Suite to use a particular user account in VMware, that account must have the permissions identified in the following table.

    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 folder

    For user folder creation

    Create this folder under the root folder and be sure to select this path at installation time.

    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

    Add the following roles and permissions so the tenant image can be uploaded to vSphere under Datacenter during the installation for the given user:

    • Create a role by providing below privileges to this role.

    • Datastore.Allocate space

    • Datastore.Browse datastore

    • Datastore.Low level file operations

    • Datastore.Remove file

    • Folder. Create folder

    • Global.Manage Custom Attributes

    • Global.Set custom attribute

    • Network.Assign network

    • Resource.Apply recommendation

    • Resource.Apply vApp to resource pool

    • Resource.Apply virtual machine to resource pool

    • Storage views. View

    • Tasks.Create task

    • Tasks.Update task

    • Virtual machine (Check all the permissions under this Privilege).

    • vApp.Import

    • vApp.Power off

    • vApp.Power on

    • vApp.Suspend

    • vApp.vApp application configuration

    • vApp.vApp instance configuration

    • vApp.vApp managedBy configuration

    • vApp.vApp resource configuration

    Global RoleSet Custom AttributesTo add custom attributes on virtual machines
    Manage Custom Attributes

Module Details

Additionally, refer to your module documentation for module-specific dependencies identified in the following table.

ModuleDocumentation
Workload ManagerCloud Overview
Action OrchestratorAdd Cloud Account
Cost OptimizerCloud Overview

Advanced Installation Process

To install the CloudCenter Suite on a new vSphere cluster, perform the following procedure. 

  1. Verify that you have prepared your environment as listed in the VMware Nuances section above.

  2. Navigate to the Suite Installer Dashboard.

  3. Click Get Started in the New Kubernetes Cluster tile to create a new cluster and install the Suite Admin on it.

  4. Click vSphere and enter your vSphere credentials identified in the following table and click Connect.

    vCenter DetailsDescription
    vCenter ServerThe DNS address or IP address of the vCenter server.
    vCenter PortThe egress endpoint for the vCenter server. For example, Port 443.
    vCenter UsernameThe username to be used for the vCenter setup
    vCenter PasswordThe password to be used for the vCenter setup
  5. Once the connection is validated, click Next.

    To specify the placement properties, enter the vCenter details identified in the following table.

    vCenter DetailsDescription
    DatacenterThe name of the vSphere datacenter from where this cluster will be launched
    ClusterThe cluster to deploy the node in the above datacenter.
    Resource PoolThe resource pool used to deploy the node.
    DatastoreThe datastore cluster to associate with the node.
    NetworkThe network cluster to associate with the node.
    VM Template

    Different images will be used for the installer and the cluster launched by the installer. The installer includes a default Kubernetes cluster image (called, CCS-version-Base-Image) with a configurable option to override the use of this default image. The CCS-version-Base-Image  image included in the installer is selected if you do not override the setting.

    To override the CCS-version-Base-Image image used by the Suite installer, be sure to add the applicable image in the vSphere console and selected the applicable OVA from the dropdown list in this field.

    If you use the OVA installer to launch the cluster in an OpenStack environment, be sure to override this field and select the applicable QCOW2 CS-version-Base-Image.

    If you install the CloudCenter Suite using any image other than CCS-version-Base-Image, the installation will fail.


    Cluster FolderThe folder which contains the Kubernetes cluster nodes.
    Kubernetes Cluster Configuration
    Worker Instance TypeThe memory and CPU usage that is required for the workers in your environment. See Prepare Infrastructure > Resource Requirements for CloudCenter Suite Modules for additional context. Based on your selection, the recommendation for the number of nodes in the cluster is also updated (right below this field).
    Kubernetes Worker Count

    The recommendation from the Worker Instance Type field should be the number that you enter in this field.
    If you opt to reduce or increase the workers, see Prepare Infrastructure > Resource Requirements for CloudCenter Suite Modules for additional context.

    The Number of Worker VMs depends on the selected instance type. For example:

    • If the instance type is large (8 CPU, 32GB memory), then 5 workers are created and the total static IPs required for this environment are 7 IPs (4 worker VMs, and 3 primary servers).

    • If the instance type is large (8 CPU, 24GB memory), then 5 workers are created and the total static IPs required for this environment are 8 IPs (5 worker VMs, and 3 primary server).

    • If the instance type is large (8 CPU, 16GB memory), then 7 workers are created and the total static IPs required for this environment are 9 IPs (6 worker VMs, and 3 primary server).

    • If the instance type is smaller (4 CPU, 16GB memory), then 9 workers are created, so the static IPs required for this environment are 11 IPs (8 worker VMs, and 3 primary server).

    Accordingly, select the IP range by taking into consideration the Number of Worker VMs that will be created based on instance type.

    This is just an example, be aware that different datacenters will have different instance types configurations and dependencies for each release.

    To determine the number of workers select the instance type in the CloudCenter Suite installer, the Number of Worker VMs are calculated and displayed at the bottom of the instance field as displayed in the following screenshot.

    Kubernetes Pod CIDR

    The IP address of the pod's Classless Inter-Domain Routing (CIDR) block.

    Verify that this IP does not conflict with the node/VM IP address.

    Cluster PrefixThe name of each node in the cluster is prefixed with the information identified in this field to let users know that this node is part of the cluster. This prefix is defined by the user.
    IP Allocation Mode

    This switch allows you to select the mode:

    • DHCP: This strategy allows the IP to be allocated by the DHCP server to the instance on server boot up.

      • Master VIP: The IP address for the Take Me to Suite Admin link – Users can determine the IP address that should have the primary server role for the Take Me to Suite Admin link.

        This should be a unique IP and should not be assigned to any other resource.

        This should be a unique IP that is not assigned to any other resource. Also, make sure the IP is not in the same range of IPs generated by any DHCP server in your vSphere environment – this will ensure that those IPs are not assigned by the DHCP server to any other node at installation time.


    • Static IP: This strategy allows the customer to provide the IP address. As this IP address may or may not be available to the server (based on the availability), you must perform adequate checks to ensure IP availability before using this strategy.

      All IPs should be unique and should not be assigned to any other resource.


      • Static IP Pool Start IP: The first IP address of the static IP range. If you need to scale up nodes after setting up the Suite Admin, then you must ensure a wider range. The total number of IPs = the total number of nodes required in the cluster (with the scale requirements factored into this number) + 3 IPs for ingress controllers.
      • Static IP Pool End IPThe last IP address for the static IP range.
      • Subnet Mask: The netmask corresponding the the specified IP range.
      • DNS Server List: The comma separated list of DNS server IP addresses.
      • Gateway List: The comma separated list of Gateway server IP addresses.


    SSH Configuration
    SSH Username

    This is a user-assigned field to identify the user for SSH access into worker(s)/primary server(s).

    Do not use root as a username in this field, any other valid name is acceptable.

    SSH Public Key
    This field only accepts one of the following keys:
    • ecdsa

    • ed25519

    For either key, you must use the following format:

    #ssh-ed25519 
    ssh-ed25519 <public key> KEY-BODY <username>@<hostname>
    
    #for example
    ssh-ed25519 AAA*$...vI48 user@checkmachine 
    
    
    
    #The UI does not accept keys without <username>@<hostname> -- this is applicable for both ecdca and ssh-ed25519 keys
    ssh-ed25519 <public key> KEY-BODY <username>@<hostname>
    
    #Example for ed25519 user@checkmachine 
    ssh-ed25519 AAA...vI48 
    #Example for ecdsa user@checkmachine 
    ssh-ecdsa AAA*$...vI48
    
    
    
    #ecdsa 
    ssh-ecdsa <public key> KEY-BODY <username>@<hostname>
    
    #for example
    ssh-ecdsa AAA*$...vI48 diffuser@checkmachine
  6. Specify the NTP Configuration details identified in the following table:

    If you setup CloudCenter Suite in offline mode, you must provide valid NTP server details before you save your configuration.

    When you enter values for the NTP Servers or NTP Pools fields, make sure to enter the NTP value that was assigned to the ESX Host where the CloudCenter Suite installer was created. This NTP value is available in the Placement Properties page at the time of installation, see VMware vSphere Appliance Setup > Step 1 for details.

    Identical NTP values are required to ensure that the NTP communication between the installer and CloudCenter Suite primary server/worker VMs are in sync so the certificates generated by the installer for CloudCenter Suite are also in sync.

    NTP DetailsDescription
    NTP ServersThe list of IP addresses or FQDNs of your NTP server(s) – to be used to sync VM clocks.
    NTP Pools

    The list of IP addresses or FQDNs of your NTP pools.

  7. If you are in an environment that uses Proxy connections to access the internet, you need to configure the settings identified in the following table.

    If you use proxy values for both HTTP and HTTPs, enter any one of the two values, not both. If you enter both the HTTP and HTTP values, then the UI dashboard may not display modules.

    Proxy detailsDescription
    HTTP ProxyThe IP addresses and port of the HTTP proxy server.
    HTTPS ProxyThe IP addresses and port of the HTTPS proxy server.
  8. Click Install. The installation progress is visible on screen. 

  9. Once successful, you see the following message.

    CloudCenter Suite installation successful!
  10. You have the following options at this point:

    1. Click Take Me To Suite Admin to launch and set up the Suite Admin.
    2. Click Install Another Cluster to start another installation and go back to the homepage (Installer Dashboard).

    3. Download KubeConfig file to connect to the launched cluster using the kubectl tool.

    4. After the installation is complete, use the following command to SSH (using the SSH credentials configured during installation.) into the workers/primary servers as cloud-user and use the private SSH key or the public key (provided when you configured the Properties details above).

      #Sample command to SSH into a worker/primary server
      
      • ssh -I <private key> cloud-user@<Installer IP>
      
      #or
      
      • ssh -I <private key> ssh-user@<worker/primary server IP> 
  11. Be sure to switch off the installer VM. You can reuse this VM for any other purpose, for example, as an Offline Repository or to upgrade the Kubernetes cluster or to upgrade the tenant image on the nodes.



Terms & Conditions Privacy Statement Cookies Trademarks