Cloud Remote 

Overview

The Cloud Remote component is deployed on a per cloud region basis if communication between the CloudCenter Suite cluster and the target cloud region is restricted. More specifically, it is needed when

  • communication between the CloudCenter Suite cluster and the API endpoint of your private cloud region is restricted, or
  • communication between the CloudCenter Suite cluster and worker VMs in your VM-based cloud region is restricted.  

When Cloud Remote is used to support communications with a VM-based cloud region, it is installed as a virtual appliance launched in that region.  When it is used to support communications with a Kubernetes cloud, it is installed as a virtual appliance in a network accessible from that Kubernetes cloud.

Cloud Remote can run as a single appliance or it can scale up to multiple appliances working as a single cluster. 

Cloud Remote includes the following services running as containers:

  • AMQP server for communicating with the CloudCenter Suite cluster and with worker VMs
  • Script execution engine for executing external lifecycle action scripts
  • Proxy server for communicating with the script execution engine and the cloud API endpoint
  • Guacamole server for encapsulating SSH or RDP sessions to worker VMs in a browser window

Some typical network configurations involving Cloud Remote are as follows:

Use CaseNetwork ConnectivityNetwork Diagram
CloudCenter Suite in a private network connecting to a public cloud regionWorker VMs Directly Connect with CloudCenter Suite = No
AND
CloudCenter Suite Directly Accessible from Cloud Remote = No

CloudCenter Suite in a public network connecting to a private VM-based cloud regionCloud Endpoint Directly Accessible = No
AND
Worker VMs Directly Connect with CloudCenter Suite = No
AND
CloudCenter Suite Directly Accessible from Cloud Remote = Yes


CloudCenter Suite in a public network connecting to a private Kubernetes cloud region
Cloud Endpoint Directly Accessible = No
AND
CloudCenter Suite Directly Accessible from Cloud Remote = Yes


The remaining sections describe how to acquire and configure Cloud Remote, and how to scale Cloud Remote.

Obtain, Launch and Configure

The procedure to obtain, launch and configure Cloud Remote depends on

  • which VM-based cloud Cloud Remote will be deployed in, and
  • the overall networking constraints of the CloudCenter Suite cluster and the target cloud region.

Prior to deploying Cloud Remote, make sure you have already added the cloud to CloudCenter Suite, and if a multi-region cloud, you added the first region. Then, use one of the following procedures corresponding to where Cloud Remote will be deployed and whether it will be used to support VM-based workloads in that cloud region or Kubernetes container workloads in a Kubernetes cloud hosted in that region.

 Cloud Remote for vCenter

Configure Cloud Remote in a vCenter region as follows:

  1. Download the Cloud Remote appliance OVA from software.cisco.com.
  2. Launch the Cloud Remote appliance from the OVA you downloaded as follows:
    1. Login to the vCenter console using the vSphere web client with Flash, or with the vSphere Windows client. Do not use the HTML5 web client.
    2. Navigate to the folder or resource pool where you want to deploy the OVA. Right click on that resource pool or folder and select Deploy OVF Template.
    3. From the Deploy OVF Template dialog box, for Source, select Local file and click Browse to find the OVA file you downloaded.
    4. Complete the fields for Name and location, Host / Cluster, Resource Pool, Storage, and Disk Format appropriate for your environment.
    5. For the Network Mapping section, make sure to properly map the Management network (public) and VM Network network (private) to the appropriate network names in your environment.
    6. For the Properties section, make sure to check the box labeled Does the VM need a second interface? if the Cloud Remote appliance needs to be multi-homed on a public network and a private network.
    7. Confirm your settings and click Finish to launch the VM.
  3. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  4. Once the first instance of the appliance has been launched, use the vSphere client to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other appliances you launch.
  5. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    8443TCPLimit to address space of users needing SSH or RDP access to their managed VMsUser to Guacamole
    5671TCPLimit to address space of the managed VMs and the address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)
    7789TCPLimit to address space of the managed VMsWorker VM to Guacamole

    The Cloud Remote web UI, User-to-Guacamole, and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.


  6. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You must update some of the address fields in the dialog box according to the scenarios summarized in the table below.
    Toggle SettingsFieldValue

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster. This address must be accessible to Cloud Remote

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) >
    Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.


    Worker VMs Directly Connect with CloudCenter = NoWorker AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to the worker VMs, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    Worker VMs Directly Connect with CloudCenter = NoGuacamole IP AddressEnter <Cloud_Remote_IP>:<guac_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to CloudCenter Suite users, and
    <guac_port> = 8443 OR the custom Guacamole port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    When done, click OK to save the setting and dismiss the dialog box.

  7. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  8. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote in a vCenter cloud for a Kubernetes cloud

Configure Cloud Remote in a vCenter region to support a Kubernetes target cloud as follows:

  1. Download the Cloud Remote appliance OVA from software.cisco.com.
  2. Launch the Cloud Remote appliance from the OVA you downloaded as follows:
    1. Login to the vCenter console using the vSphere web client with Flash, or with the vSphere Windows client. Do not use the HTML5 web client.
    2. Navigate to the folder or resource pool where you want to deploy the OVA. Right click on that resource pool or folder and select Deploy OVF Template.
    3. From the Deploy OVF Template dialog box, for Source, select Local file and click Browse to find the OVA file you downloaded.
    4. Complete the fields for Name and location, Host / Cluster, Resource Pool, Storage, and Disk Format appropriate for your environment.
    5. For the Network Mapping section, make sure to properly map the Management network (public) and VM Network network (private) to the appropriate network names in your environment.
    6. For the Properties section, make sure to check the box labeled Does the VM need a second interface? if the Cloud Remote appliance needs to be multi-homed on a public network and a private network.
    7. Confirm your settings and click Finish to launch the VM.
  3. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  4. Once the first instance of the appliance has been launched, use the vSphere client to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other appliances you launch.
  5. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    5671TCPLimit to address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)

    The Cloud Remote web UI  and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.

  6. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You may need to update the Local AMQP IP Address or the Remote AMQP IP Address fields per the table below.
    Toggle SettingsFieldValue

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster.

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number
    you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.

    When done, click OK to save the setting and dismiss the dialog box.

  7. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  8. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote for OpenStack

Configure Cloud Remote in an OpenStack region as follows:

  1. Download the Cloud Remote appliance qcow2 file from software.cisco.com.
  2. Through the OpenStack console, import and launch the Cloud Remote appliance. This process is similar to importing and launching the CloudCenter Suite installer appliance for OpenStack.

    Do not add ‘Network Ports’ while launching a Cloud Remote instance in OpenStack.

  3. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured. See Cloud Remote (Conditional) > Scaling for details.
  4. Once the first instance of the appliance has been launched, use the OpenStack console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other appliances you launch.
  5. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    8443TCPLimit to address space of users needing SSH or RDP access to their managed VMsUser to Guacamole
    5671TCPLimit to address space of the managed VMs and the address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)
    7789TCPLimit to address space of the managed VMsWorker VM to Guacamole

    The Cloud Remote web UI, User-to-Guacamole, and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.


  6. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You must update some of the address fields in the dialog box according to the scenarios summarized in the table below.
    Toggle SettingsFieldValue

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster. This address must be accessible to Cloud Remote

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) >
    Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.


    Worker VMs Directly Connect with CloudCenter = NoWorker AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to the worker VMs, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    Worker VMs Directly Connect with CloudCenter = NoGuacamole IP AddressEnter <Cloud_Remote_IP>:<guac_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to CloudCenter Suite users, and
    <guac_port> = 8443 OR the custom Guacamole port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    When done, click OK to save the setting and dismiss the dialog box.

  7. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  8. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote in an OpenStack region for a Kubernetes cloud

Configure Cloud Remote in a OpenStack region to support a Kubernetes target cloud as follows:

  1. Download the Cloud Remote appliance qcow2 file from software.cisco.com.
  2. Through the OpenStack console, import and launch the Cloud Remote appliance. This process is similar to importing and launching the CloudCenter Suite installer appliance for OpenStack.
  3. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  4. Once the first instance of the appliance has been launched, use the OpenStack console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other appliances you launch.
  5. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    5671TCPLimit to address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)

    The Cloud Remote web UI  and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.

  6. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You may need to update the Local AMQP IP Address or the Remote AMQP IP Address fields per the table below.
    Toggle SettingsFieldValue

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster.

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number
    you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.

    When done, click OK to save the setting and dismiss the dialog box.

  7. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  8. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote for AWS

Configure Cloud Remote in an AWS region as follows:

  1. Obtain the Cloud Remote shared AMI form Cisco support and launch it. Follow the same guidance for obtaining and launching the CloudCenter Suite installer appliance for AWS.
  2. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  3. Once the first instance of the appliance has been launched, use your cloud console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other instances you launch.
  4. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    8443TCPLimit to address space of users needing SSH or RDP access to their managed VMsUser to Guacamole
    5671TCPLimit to address space of the managed VMs and the address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)
    7789TCPLimit to address space of the managed VMsWorker VM to Guacamole

    The Cloud Remote web UI, User-to-Guacamole, and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.


  5. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You must update some of the address fields in the dialog box according to the scenarios summarized in the table below.
    Toggle SettingsFieldValue

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster. This address must be accessible to Cloud Remote

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) >
    Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.


    Worker VMs Directly Connect with CloudCenter = NoWorker AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to the worker VMs, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    Worker VMs Directly Connect with CloudCenter = NoGuacamole IP AddressEnter <Cloud_Remote_IP>:<guac_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to CloudCenter Suite users, and
    <guac_port> = 8443 OR the custom Guacamole port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    When done, click OK to save the setting and dismiss the dialog box.

  6. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  7. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote in an AWS region for a Kubernetes cloud

Configure Cloud Remote in an AWS region to support a Kubernetes target cloud as follows:
  1. Obtain the Cloud Remote shared AMI form Cisco support and launch it. Follow the same guidance for obtaining and launching the CloudCenter Suite installer appliance for AWS.
  2. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  3. Once the first instance of the appliance has been launched, use your cloud console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other instances you launch.
  4. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    5671TCPLimit to address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)

    The Cloud Remote web UI  and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.

  5. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You must update some of the address fields in the dialog box according to the scenarios summarized in the table below.
    Toggle SettingsFieldValue

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster. This address must be accessible to Cloud Remote

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) >
    Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.


    Worker VMs Directly Connect with CloudCenter = NoWorker AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to the worker VMs, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    Worker VMs Directly Connect with CloudCenter = NoGuacamole IP AddressEnter <Cloud_Remote_IP>:<guac_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to CloudCenter Suite users, and
    <guac_port> = 8443 OR the custom Guacamole port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    When done, click OK to save the setting and dismiss the dialog box.

  6. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  7. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote for AzureRM

Configure Cloud Remote in an AzureRM region as follows:

  1. Download the Cloud Remote appliance zip file from software.cisco.com and then unzip it to reveal the VHD file.
  2. Upload the Cloud Remote appliance VHD file to AzureRM using the AzureRM CLI, then launch the appliance from the AzureRM console web UI. This process is similar to uploading and launching the CloudCenter Suite installer appliance for AzureRM.

    You must use the AzureRM CLI to perform this upload.

  3. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  4. Once the first instance of the appliance has been launched, use the AzureRM console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other appliances you launch.
  5. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    8443TCPLimit to address space of users needing SSH or RDP access to their managed VMsUser to Guacamole
    5671TCPLimit to address space of the managed VMs and the address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)
    7789TCPLimit to address space of the managed VMsWorker VM to Guacamole

    The Cloud Remote web UI, User-to-Guacamole, and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.


  6. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You must update some of the address fields in the dialog box according to the scenarios summarized in the table below.
    Toggle SettingsFieldValue

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster. This address must be accessible to Cloud Remote

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) >
    Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.


    Worker VMs Directly Connect with CloudCenter = NoWorker AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to the worker VMs, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    Worker VMs Directly Connect with CloudCenter = NoGuacamole IP AddressEnter <Cloud_Remote_IP>:<guac_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to CloudCenter Suite users, and
    <guac_port> = 8443 OR the custom Guacamole port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    When done, click OK to save the setting and dismiss the dialog box.

  7. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  8. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote in an AzureRM region for a Kubernetes cloud

Configure Cloud Remote in an AzureRM region to support a Kubernetes target cloud as follows:
  1. Download the Cloud Remote appliance zip file for AzureRM from software.cisco.com and then unzip it to reveal the VHD file.
  2. Upload the Cloud Remote appliance VHD file to AzureRM using the AzureRM CLI, then launch the appliance from the AzureRM console web UI. This process is similar to uploading and launching the CloudCenter Suite installer appliance for AzureRM.

    You must use the AzureRM CLI to perform this upload.

  3. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.
  4. Once the first instance of the appliance has been launched, use the AzureRM console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also note the IP addresses of any other appliances you launch.
  5. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    8443TCPLimit to address space of users needing SSH or RDP access to their managed VMsUser to Guacamole
    5671TCPLimit to address space of the managed VMs and the address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)
    7789TCPLimit to address space of the managed VMsWorker VM to Guacamole

    The Cloud Remote web UI, User-to-Guacamole, and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.


  6. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You may need to update the Local AMQP IP Address or the Remote AMQP IP Address fields per the table below.
    Toggle SettingsFieldValue

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster.

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number
    you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.

    When done, click OK to save the setting and dismiss the dialog box.

  7. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  8. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote for Google

Configure Cloud Remote in a Google region as follows:

  1. Request the Cloud Remote shared VMI form Cisco support by opening a CloudCenter Support case. In your request, specify the following details:

    1. Your GCP account number

    2. Your GCP project ID number
    3. Your CloudCenter Suite version

    4. Your Customer ID (CID)

    5. Your customer name

    6. Specify if your setup is in production or for a POC

    7. Your Contact Email

  2. After you open a case, your support case is updated with the shared VMI ID. Proceed to the next step only after your support case is updated with the VMI ID.

  3. Navigate to the GCP dashboard and search for the VMI ID name provided in the CloudCenter Support case in the list of images for your project.

  4. Launch an instance using the shared VMI. 

    1. Click on the image name. This takes you to the page for the image


    2. Click on Create Instance to display the Instance properties page

    3. Complete these fields:

      1. Instance name

      2. Region and zone

      3. Machine type: select 2 vCPU, 7.5 GB RAM

      4. Click the checkbox to allow HTTPS access

      5. Click the Security tab (under the Allow HTTPS traffic checkbox). In the SSH key field, add your organization's public ssh key followed by a space and then the username you want to use to login to the Cloud Remote appliance. Click the Add Item button when done.

    4. Click Create to launch the instance.

  5. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.

  6. Once the first instance of the appliance has been launched, use the GCP console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also, note the IP addresses of any other appliances you launch.

  7. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    8443TCPLimit to address space of users needing SSH or RDP access to their managed VMsUser to Guacamole
    5671TCPLimit to address space of the managed VMs and the address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)
    7789TCPLimit to address space of the managed VMsWorker VM to Guacamole

    The Cloud Remote web UI, User-to-Guacamole, and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.


  8. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You must update some of the address fields in the dialog box according to the scenarios summarized in the table below.
    Toggle SettingsFieldValue

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster. This address must be accessible to Cloud Remote

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Worker VMs Directly Connect with CloudCenter = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) >
    Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.


    Worker VMs Directly Connect with CloudCenter = NoWorker AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to the worker VMs, and
    <amqp_port> = 5671 OR the custom AMQP port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    Worker VMs Directly Connect with CloudCenter = NoGuacamole IP AddressEnter <Cloud_Remote_IP>:<guac_port>, where
    <Cloud_Remote_IP> = the Cloud Remote IP address accessible to CloudCenter Suite users, and
    <guac_port> = 8443 OR the custom Guacamole port number you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    When done, click OK to save the setting and dismiss the dialog box.

  9. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  10. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

 Cloud Remote in a Google Cloud region for a Kubernetes cloud

Configure Cloud Remote in a Google region to support a Kubernetes target cloud as follows:
  1. Request the Cloud Remote shared VMI form Cisco support by opening a CloudCenter Support case. In your request, specify the following details:

    1. Your GCP account number

    2. Your GCP project ID number
    3. Your CloudCenter Suite version

    4. Your Customer ID (CID)

    5. Your customer name

    6. Specify if your setup is in production or for a POC

    7. Your Contact Email

  2. After you open a case, your support case is updated with the shared VMI ID. Proceed to the next step only after your support case is updated with the VMI ID.

  3. Navigate to the GCP dashboard and search for the VMI ID name provided in the CloudCenter Support case in the list of images for your project.

  4. Launch an instance using the shared VMI. 

    1. Click on the image name. This takes you to the page for the image


    2. Click on Create Instance to display the Instance properties page

    3. Complete these fields:

      1. Instance name

      2. Region and zone

      3. Machine type: select 2 vCPU, 7.5 GB RAM

      4. Click the checkbox to allow HTTPS access

      5. Click the Security tab (under the Allow HTTPS traffic checkbox). In the SSH key field, add your organization's public ssh key followed by a space and then the username you want to use to login to the Cloud Remote appliance. Click the Add Item button when done.

    4. Click Create to launch the instance.

  5. Optional but recommended for production environments: Deploy two additional instances of the appliance to form a cluster for HA. Cloud Remote includes support for clustering of multiple nodes. You will "add" these two additional instances to the first instance after the first instance is configured.  See Cloud Remote (Conditional) > Scaling for details.

  6. Once the first instance of the appliance has been launched, use the GCP console to note its IP public and private addresses. You will need this information later on in order login to the Cloud Remote web UI and to complete the Region Connectivity settings in the CloudCenter Suite Web UI. Also, note the IP addresses of any other appliances you launch.

  7. Setup the appropriate firewall rules. You will need to open various ports on each instance of the appliance. To do this, use the tools provided by the cloud provider to create a new security group for your Cloud Remote cluster; then, associate each appliance in the cluster with that security group. Use the tables below for guidance on what port rules should be added to that security group.

    Port rules for a single node Cloud Remote deployment:
    PortProtocolSourceUsage
    22TCPLimit to address space of users needing SSH access for debugging and changing default portsSSH
    443TCPLimit to address space of users needing access to the Cloud Remote web UI for setup and scalingHTTPS (Cloud Remote web UI)
    5671TCPLimit to address of the CloudCenter Suite cluster's local AMQP serviceAMQP
    15671TCPLimit to address space of users needing web access for debugging the remote AMQP serviceHTTPS (AMQP Management)

    The Cloud Remote web UI  and AMQP ports listed above are the defaults used by Cloud Remote. You may change these port numbers using the Change Ports shell script (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)) once the appliance is fully configured and communicating with the CloudCenter Suite cluster. If you plan to modify any of these three port numbers, update the firewall rules accordingly.

    For a multi-node Cloud Remote cluster deployment, these additional port rules should be added to the same security group used for the single node configuration:

    PortProtocolSource
    2377TCP<cr_sec_group> *
    25672TCP<cr_sec_group>
    7946UDP<cr_sec_group>
    4369TCP<cr_sec_group>
    9010TCP<cr_sec_group>
    4789UDP<cr_sec_group>

     * <cr_sec_group> represents the security group that all Cloud Remote nodes are joined to.

  8. Switch back to the Workload Manager or Cost Optimizer UI and click Configure Region link in the upper left of the Region Connectivity section to bring up the Configure Region dialog box. The toggle settings should be the same as when you set them in the connectivity page of the Add Cloud dialog box. You may need to update the Local AMQP IP Address or the Remote AMQP IP Address fields per the table below.
    Toggle SettingsFieldValue

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = Yes

    Local AMQP IP Address

    Pre-populated with the address and port number of the "local" AMQP server running in the CloudCenter Suite cluster.

    If Cloud Remote is accessing the CloudCenter Suite cluster through a user-supplied proxy server or NAT firewall, overwrite this field with the corresponding local AMQP IP address and port number provided by the user-supplied proxy server or NAT firewall and accessible to Cloud Remote.

    Cloud Endpoint Directly Accessible = No
    AND
    CloudCenter Directly Accessible from Cloud Remote = No
    Remote AMQP IP Address

    Enter <Cloud_Remote_IP>:<amqp_port>, where
    <Cloud_Remote_IP> = the IP address Cloud Remote which is accessible to the CloudCenter Suite cluster, and
    <amqp_port> = 5671 OR the custom AMQP port number
    you would later set with the Change Ports shell script on the Cloud Remote appliance (see Cloud Remote (Conditional) > Custom Port Numbers (Conditional)).

    If there is no user-supplied NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, the IP address would be the public IP address of Cloud Remote.

    If there is a NAT firewall or proxy server between the CloudCenter Suite cluster and Cloud Remote, instead, enter the corresponding public IP address and port number that the firewall or proxy server presents to the internet on behalf of the "remote" AMQP server running in Cloud Remote.

    When done, click OK to save the setting and dismiss the dialog box.

  9. After saving the Region Configuration settings, the next step is downloading the connectivity configuration file and copying its encryption key. Click the Download Configuration link in the upper right of the Region Connectivity section, as shown in the figure below.

    Clicking Download Configuration causes two things to happen:

    • A file named artifacts.zip will be downloaded by your browser. Make note of the location of this zip file as you will need to upload it to Cloud Remote through the Cloud Remote web UI (see below).
    • The Region Connectivity section header briefly displays the encryption key for the zip file, as shown in figure below. The key is the text after ":- ". You must copy this key within one minute of it being displayed as you will need to enter this key in the Cloud Remote web UI (see below). The key is only displayed for one minute. If you miss the chance to copy it, you must download a new copy of the zip file and copy the new key.


  10. After you have set the region connectivity settings in CloudCenter Suite, and downloaded the zip file and copied the encryption key, login to Cloud Remote web UI.
    1. Open another browser tab and login to https://<Cloud Remote_ip> with the default credentials: admin / cisco. 
    2. You will immediately be required to change your password. Do so. 
    3. You are now brought to the Cloud Remote home page as shown in the figure below.
    4. Click the Apply Configuration button in the page header.
    5. Clicking Apply Configuration cause. This prompts you to select a configuration file and enter the encryption key as shown in the figure below.
    6. Paste the encryption key you saved from the CloudCenter Suite web UI into the Encryption Key field in the dialog box.
    7. Click Select File and browse to the artifacts.zip file that you downloaded through the CloudCenter Suite web UI and select it.
    8. Click Confirm.
    9. Once the zip file is successfully transmitted and accepted, the Cloud Remote appliance attempts to establish communication with the CloudCenter Suite cluster and the Cloud Remote web UI home page is updated to show the name of the region it is connecting to in the upper right (see figure below).
    10. Now, switch your focus back to the Region Connectivity section of the target cloud region in the CloudCenter Suite web UI. The status indicator in the Region Connectivity section header will change from Not Configured to Running once connectivity between  Cloud Remote and the CloudCenter Suite cluster is completely established (see figure below).
      After completing these steps, Workload Manager and Cost Optimizer can both use Cloud Remote for communicating with the target cloud region.

Update Cloud Remote

When updating Workload Manager to Workload Manager 5.0.2 or updating Cost Optimizer to Cost Optimizer 5.0.2, you must also update all instances of Cloud Remote to Cloud Remote 5.0.2. For each instance of Cloud Remote, follow this update procedure.

  1. Locate the Cloud Remote update script at software.cisco.com and copy it to a directory in your Cloud Remote instance.
  2. Establish a terminal session to the Cloud Remote instance and navigate to the directory containing the update script.
  3. Run the following commands from the Cloud Remote command prompt.

    chmod +x UPGRADE_FILE
    sudo ./ UPGRADE_FILE


    When the script completes successfully you will get the following message at the command prompt:

    CloudRemote upgraded successfully!

  4. Occasionally, the update script may time out before sending the success message. If you believe this may be the case, you can confirm the update did complete successfully by executing these two commands from the Cloud Remote command prompt:

    1. Confirm all of the images needing update are at the new revision level: 

      docker images

      The output should be similar to the example below.

      The following images should be updated:

      1. ui

      2. ces_worker

      3. worker

      4. guacamole

      5. remoteproxy

      6. rabbitmq

      7. babl

      8. centos_worker

      9. ces_centos_worker

    2. Confirm all of the images have been launched and running in containers:

      docker ps

      The output should be similar to the example below.

  5. After the update script completes successfully, download the region connectivity settings from the Regions tab in the Workload Manager or Cost Optimizer UI as a zip file, then upload that zip file to Cloud Remote as explained in the Cloud Remote configuration instructions above.

  6. After uploading the configuration file to Cloud Remote, manually restart each managed application VM that is in the region served by the updated Cloud Remote instance.

Scaling

After your initial Cloud Remote instance is launched and configured, it is recommended that you can add two additional nodes to form a cluster. When scaling up or down it is recommended not to run your cluster continuously with only two nodes. Follow this procedure:

  1. Deploy a new instance of the appliance in the same network as the first appliance. Record its IP address. Alternatively, if you have another instance of Cloud Remote that you launched previously but stopped, restart that instance.
  2. At the home page of the Cloud Remote web UI for the initial instance, click the tile with the plus icon. After clicking the plus icon, the tile will change and show an Add IP field as shown in the figure below. Enter the address of your newly launched (or restarted) instance in this field and then click Done.

Your new instance will become part of the cluster. There is no need to login to the new instance to set configuration. The cluster can be managed through the first instance's Web UI. 

You can scale down the cluster in two steps:

  1. From the Cloud Remote web UI home page, take note of the IP address of the node you want to remove from the cluster. Then remove it by hovering over its tile and clicking the trash icon.
  2. Login to the cloud console for your target cloud and find the VM with the IP address of the node you just removed from the cluster. Stop that VM.

Custom Port Numbers (Conditional)

If firewall settings prevent you from using standard port numbers for HTTPS, AMQP, and Guacamole protocols, you can specify custom port numbers for those protocol using a Change Ports shell script that is included in the Cloud Remote appliance. Otherwise, Cloud Remote will use the standard port numbers as shown in the table below.

ServiceDefault Port
HTTPS (web UI)443
AMQP (Rabbit MQ)5671
Guacamole8443

The Guacamole service is only needed for user access to VM-based deployments. Therefore, there is no need to create a custom port number for the Guacamole service if this Cloud Remote cluster is used to support connectivity to a Kubernetes target cloud.

Only run the script after you have downloaded the artifacts.zip file from the region connectivity settings section of the Regions tab in the Workload Manager or Cost Optimizer UI, and then uploaded that file to Cloud Remote through the Cloud Remote web UI. In addition, if you later need to upload a new artifacts.zip file to Cloud Remote, the custom port settings will be erased and you will need to run the Change Ports script again.

Follow these steps to run the script:

  1. Establish an ssh session to master (initial) Cloud Remote instance.
  2. Navigate to the directory: /opt/cisco/pilot/builds/<pilot folder>/bin
  3. Run the shell script: 

    changeports.sh
  4. You are first prompted to see if you want to change the web UI port number. Type "Y" or "N". 

    1. If you enter "Y", you are prompted for:

      1. Current port number. Type any number and then ENTER. 

      2. New port number.  Type the new port number and then ENTER. The script will attempt to change the port number on this node and then on all other nodes in your Cloud Remote cluster. When done, you are prompted whether you want to change the value of the next port.

    2. If you enter "N", you are prompted whether you want to change the value of the next port.
  5. When you are prompted for the Rabbit MQ port number, type "Y" and enter the old and then new port numbers as above, or type "N", whichever is appropriate.
  6. When you are prompted for the Guacamole port number, type "Y" and enter the old and then new port numbers as above, or type "N", whichever is appropriate. If the target cloud is a Kubernetes cloud, the Guacamole server is not used and you would therefore enter "N".


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