Cisco CloudCenter 4.10.0.10 Release Notes

Release Date

First Published: August 27, 2020

Updated:

  • September 4, 2020: Updated the Upgrading Non-CentOS CloudCenter Components (RHEL) row in the table below.

  • September 14, 2020: Added dependencies about Imported VMs to the Upgrade Path section.

  • October 13, 2020: Added a bullet to the Deprecated section to provide notification for select clouds.

Installation

CloudCenter 4.10.0.10 is only available as an upgrade for existing customers from CloudCenter 4.10.0.3, CloudCenter 4.10.0.4, CloudCenter 4.10.0.5,  CloudCenter 4.10.0.6, CloudCenter 4.10.0.7, CloudCenter 4.10.0.8, or CloudCenter 4.10.0.9. Contact the CloudCenter Support team for additional details.

Enable RPM Packages

You must run the following commands to enable the following RPM Package Manager (RPM) packages when running the core_installer.bin file to successfully install CloudCenter components on RHEL7 devices. 

subscription-manager repos --enable "rhel-*-optional-rpms" --enable "rhel-*-extras-rpms"  --enable "rhel-ha-for-rhel*-server-rpms"

yum clean all

Upgrade Path

You must be at a minimum version of CloudCenter 4.10.0.3 to upgrade to CloudCenter 4.10.0.10.

Effective CloudCenter 4.10.0.7 and later, the CloudCenter upgrade process downloads packages from a CentOS base and the extras repository via the internet. If you do not have internet connectivity, they must setup a local CentOS mirror and configure the CloudCenter components (CCM, CCO etc) to use the local mirror.

See the Upgrade Overview page and the following table for additional details. 

Upgrading CentOS CloudCenter Components to CloudCenter 4.10.0.10
From

core_upgrade

Appliance Jar Files?Notes
 os_upgrade1?

MongoDB?

Component?
4.10.0.5 or earlierYesYes (for CCO only)YesYes
4.10.0.6NoYes (for CCO only)YesYesYou should have already run os_upgrade when you upgraded to 4.10.0.6
4.10.0.7 or laterNoNoNoYesApplicable to CloudCenter 4.10.0.7 or later
Upgrading Non-CentOS CloudCenter Components (RHEL) to CloudCenter 4.10.0.10
4.10.0.9 or earlierNoYesYesYes

1 The os_upgrade command is not required when upgrading the REPO or Bundle store.

Rabbit HA Configuration Scenarios

If you run the jar files for CloudCenter 4.10.0.10, the rabbit_ha_info file is not created. The rabbit_config_wizard.sh command does not create rabbit_ha_info file in the /usr/local/cliqr/etc location – even if you cancel the Rabbit HA wizard. 

If you upgrade from a previous version, the rabbit_ha_info file may be present in the system based on your previous configuration changes. If present, you must remove the file.

After deleting the rabbit_ha_info file in a SA setup, the core_upgrade.bin executes successfully. See AMQP_PRIMARY - Configure High Availability Properties for additional details.

Editing AzureRM Settings

After upgrading to CloudCenter 4.10.0.10, perform the following procedure to ensure that deployments work on existing AzureRM cloud regions.  

  1. Click the Edit Cloud Settings link and set the extension versions identified in the following table to the new values in each field.

    FieldOld ValueNew Value
    Linux Custom Script Extension Version1.42.1
    Windows Custom Script Extension Version1.41.10
  2. Run the Configure Orchestrator for the new values to be consumed. Any new AzureRM cloud regions added will inherit the new values by default.

Upgrade to Python Version 2.7.5 or Later

A bootstrap timeout error can occur for deployments on AWS/Google/Azure RM/OpenStack clouds when the following set of conditions coincide: 

  • Linux Images used for deployment have Python installed with a version < 2.7.5. Usually CentOS 6 and RHEL 6 flavors have this lower version.

  • HTTPS Bundle URL is configured for the region.

To work around the issue, you have one of the following options:

Imported VMs

If you are upgrading from CloudCenter 4.9.1.1 and if your environment contains one of the following types of VMs:

  • A VM that is not deployed through WM

  • A VM that is imported into WM

You must first upgrade to CloudCenter 4.10.0.9 and upgrade the management agent on these VMs before upgrading the CloudCenter 4.10.0.10.

To upgrade the management agent on a VM that is imported into the CloudCenter platform, see VM Management > Upgrade Agent.

Architecture

When you launched worker instances with the Java agent, a 2 GB RAM swap space was automatically created when you initially booted or later on rebooted the agent. This swap space was used by the Java and GO-based agents to ensure that they continued running in case they encountered out-of-memory events.

Effective CloudCenter Platform 4.10.0.10, Cisco does not create the 2 GB swap space. Instead, the onus is on you to ensure that the worker instance has 128 MB of free space for the GO based agent to function as designed. This is a change from earlier releases. 

See Management Agent (Worker) Installation for additional details.

Applications and Services

The /etc/hosts file was modified by the %wm in certain scenarios:

  • Adding the following line to the /etc/hosts file to Linux VMs/deployments.
    127.0.0.1 hostname

    cat /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
     ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
     127.0.0.1 cqjw-681bc0be3
  • Appending the hostname to the following line:
    127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4 hostname

    cat /etc/hosts127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 cqjw-681bc0be3
     ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6

Effective CloudCenter 4.10.0.10, the code that used to modify the /etc/hosts file has been removed and these file will remain intact for VMs/deployments.

CloudCenter Management

The CloudCenter platform removes the authorized keys from the root and Ubuntu folders on various OS flavors and injects the keys on one of two ways:

  • If specified in the deployment environment

  • The CloudCenter platform automatically generates a key for each user per region and account, and injects the public key into the VM.

If you prefer to use your own key on a Linux based OS image for a Worker VM in CloudCenter 4.10.0.10 or later, then use the /etc/opt/.do_not_delete_authorized_keys flag to ensure that your private key is not overwritten during deployment by running the following commands:

touch /etc/opt/.do_not_delete_authorized_keys
chmod 444 /etc/opt/.do_not_delete_authorized_ke

The authorized_keys file locations are as follows:

  • Centos and RHEL workers - /root/.ssh

  • Ubuntu workers - /home/ubuntu/.ssh

See SSH Options for additional details. 

Administration and Governance

If you want to push the management agent on a VM that is imported into WM, you must enable the SMB2 protocol on the Windows server. See http://docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3 for details on how to enable the SMB2 protocol. See VM Management > Install AgentLite Manually > Install AgentLite on a Windows VM for additional details. 

SMBv2 is only required only when installing CloudCenter Agent from UI – it is not required if we installing the agent manually on a VM.

CloudCenter platform 4.10.0.10 no longer requires or uses SMB Version 1 on Windows VMs. Instead, verify that SMB Version 2 is installed. SMB Version 2 is installed by default on the latest Windows servers. See Virtual Machine Management > Install the Management Agent on a Windows VM for additional details on when SMB Version 2 is used by the Workload Manager.

End of Life Notices

See End of Support Notices for additional details.

Deprecated

  • CSCvu66141: Previous versions of the CloudCenter Platform supported integration with Arcus. However, this announcement is to provide notification that Arcus is deprecated, and that CloudCenter Platform 4.10.0.10 is the last release with integration support.

  • The vcdcli utility is not used or distributed by the CloudCenter platform or CloudCenter Suite of products and is now removed from the scripts/src/vasetup repository. 

  • The CloudCenter Platform will be deprecating support for the following clouds in an upcoming release: Dimension Data, Alibaba and vCloud Director.

Documentation

The following documentation changes were implemented in CloudCenter 4.10.0.10:

Known Issues

The following issues were identified in CloudCenter 4.10.0.10:

  • In CloudCenter 4.9.x, some API requests took more than 300 seconds to return a 404 error to the client. Effective CloudCenter 4.10.x, these requests have returned a 200 (successful response) even after 300 seconds. 

  • When using the GET v2/tenants/1/reports?reportType=USAGE_SUMMARY_REPORT API call, the Usage Summary Report's response time increases in cases where customers have setup a large number of VMs and deployments. 

Resolved Issues

The following issue was resolved/addressed in CloudCenter 4.10.0.10:

  • CSCvu92734: When adding a VMware Region and deploying with a root disk, if you try to add 15 or more additional disks, the %wm adds volumes up to 15 and issues an error message (Unit Number(s) are not available to create hard disk on controllerKey : 1000) beyond 15 additional volumes. A customer requested a feature enhancement to allow more than 15 volumes. 
    ResolutionPrior to CloudCenter 4.10.0.10, you could only add a maximum of 15 disks to a VM. Effective CloudCenter 4.10.0.10, the CloudCenter platform adds additional controllers automatically as needed (with matching sub-type and bus type as controller-0) and adds additional disks as requested by the user up to a total of 60 disks per VM.





  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks