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

Release Date

Release Date: July 16, 2018

Updated on:

  • July 23, 2018: Added estimatedMonthlyCost to the list of attributes in the Updated APIs section and listed additional pages that were subsequently changed in the Documentation section.

  • July 27, 2018: Added support for VMware vCenter 6.7 as listed in the Clouds section.

  • July 31, 2018: Added procedure to monitor and recover the PostgreSQL database if running in HA mode. 

  • August 7, 2018: Added procedure to update appliances files for UCSD cloud configuration in VMware environments and a Custom Docker Image section.

  • August 14, 2018: Added memory requirement for CCO HA environments and added the CCM on a FIPS System as listed in the Documentation section.

  • August 23, 2018: Added a PostgreSQLcluster monitoring bullet to the Installation section based on an additional feature availability.

  • August 28, 2018: Updated the Upgrade Overview page as listed in the Documentation section.

  • September 6, 2018: Updated multiple pages as listed in the Documentation section.

  • September 12, 2018: Added documentation for the View Action Execution Status API.

  • October 18, 2018: Added a bullet item to High Availability Best Practices General section and updated multiple pages as listed in the Documentation section.

Installation

  • CloudCenter 4.9.1 is available as installer files for ALL components for all supported clouds. 

  • The proxy settings configuration differs for CloudCenter 4.9.1 – If you have a local custom repository, then you must explicitly configure the non-proxy host variables. The default proxy setting is empty – no proxy configuration is set. See Proxy Settings for additional context. This is a change!

  • You can monitor and recover the PostgreSQL database if running in HA mode. This utility runs on the CCM server and monitors the network and operational health of the PostgreSQL. See Monitor and Recover PostgreSQL for additional context.

  • For HA environments the minimum memory requirement is 8GB for CCO servers. See High Availability Best Practices  and CCM HA for additional context.

  • CloudCenter 4.9.1 provides an additional feature to monitor the PostgreSQL VM health and assist with the recovery process – The PostgreSQL Database VMs should not be moved after installation to ensure a safe recovery (in case of environmental factors). This feature detects and monitors cluster health in HA environments. See Monitor and Recover PostgreSQL for additional context.

Architecture

No updates

Clouds

  • Dimension Data:

    • Additional support for the following clouds (see Public Clouds for details):

        • Canada CA2 (Toronto)

        • Europe EU6 (Frankfurt)

        • Asia Pacific AP3 (Singapore)

        • Asia Pacific AP4 (Tokyo)

        • Asia Pacific AP5 (Hong Kong)

        • Australia AU9 (Sydney)

        • Australia AU10 (Melbourne)

        • Australia AU11 (New Zealand)

        • Africa AF3 (Johannesburg)

    • Use VM Naming Callout scripts to automatically generate unique names for VMs launched as part of an application deployment. See Callout Scripts for additional context on VM Naming Callout scripts.

    • Use three new out-of-box storage types, Standard, High Performance, and Economy, are predefined and available for VMs launched in Dimension Data environments. You can additionally Sync Storage Types to update storage cost information for the predefined storage types and any user-defined storage types. See Configure Cloud Storage for additional details.

    • Perform the following advanced platform actions: Attach Volume, Detach Volume, Resize Instance Type, Sync VM Information. See Actions Library > Advance Platform Actions for additional context.

    • View and import unmanaged VMs launched in Dimension Data environments provided the CloudCenter user has been granted access. See VM Management for additional context.

    • Specify multiple NICs in a Dimension Data environment as specified in Environments and Deployment Environment Defaults

    • IPv6 support: Worker VM in dual stack mode are always assigned an IPv6 address.

  • VMware vCenter:

    • Additional support for vCenter 6.7.

    • The Regions tab for a VMware vCenter cloud has two new fields to specify a list of Allowed Root Disk Sizes and Allowed Additional Volume Sizes. See Region-Level Cloud Settings for additional details.

    • When deploying a job to a vCenter cloud region, the Tier Settings > Volumes section via the Deployment Environments page (not the Deployment Environment Defaults page) allows you to specify the Root disk size. 

    • See Manage Instance Types > Root Disk Size > VMware for related details.

  • AzureRM:
    • In earlier CloudCenter releases, the CloudCenter platform only supported client key authentication for AzureRM environments. 

    • Effective CloudCenter 4.9.1, users can select either key-based authentication or the more secure certificate-based authentication. 

    • A new toggle switch is included in the Add or Edit Cloud Account popup for Azure RM clouds called Use Cert Based Auth (disabled by default) and the client key authentication is displayed in this field. 

    • If you enable Use Cert Based Auth, the client key field is hidden and two other fields are displayed: 

      • Certificate– Paste the certificate in PKCS 12 format as Base64 text in this field.

      • Password – Enter the password used to create the certificate in this field. 

    • The certificate used can either be one of the following options – You can create either type using the openssl command from the command prompt of any Linux system:

      • A self-signed certificate

      • A Certificate Authority (CA) signed certificate

    • See Configure an AzureRM Cloud for additional context.
  • Kubernetes:
    • Interoperability with Kubernetes 1.10.

    • See Container Clouds for additional context.

  • Cisco UCSD:

Applications and Services

  • VM-Based Service External Lifecycle Actions:

    • The Pre VM Stop field name was changed to Pre VM Terminate and the Post VM Stop field name was changed to Post VM Terminate in the UI. This is a change! 

    • These actions actually executed when the VM is Terminated and not when the VMs are stopped or suspended. 

    • See External ServiceExternal Script Specification > VM-Based Service External Lifecycle Actions for additional context.

  • Reboot during Deployment:

    • CloudCenter 4.9.1 introduces the #!CliQrReboot: header to the /tmp/.cliqrRebootResumeInit file – Once the agent detects the #!CliQrReboot: header, it resumes after a reboot in the service lifecycle flow depending upon the context set in the header. 

    • You can control the resume flow after reboot by adding the resume context header to the /tmp/.cliqrRebootResumeInit file. 

    • See Deployment Lifecycle Scripts > The #!CliQrReboot: Header for additional context.

CloudCenter Management

  • Suspension Policy Cost Savings: This is a change! 

    • Suspension policies, designed to reduce cloud cost by suspending all tiers in a deployment during certain times, has additional, compute, cost savings displayed in multiple places.

      • New Savings column next to the Schedule column in the Policies > Suspension list page – this column displays the percentage of compute cost savings based on the uptime schedule.

      • New percentage savings field in the upper right corner of the Create/Edit Suspension Policy form – this field is updated whenever the user updates fields that determine the uptime schedule.

      • Two new fields in the second part of the Deploy form that display the percentage savings and per month savings of the associated suspension policy in the upper right corner.

      • Deployments List Page:

        • New Approx Cost column next to the Run time column displaying the hourly compute cost and estimated monthly compute cost based on the uptime schedule.

        • New Savings column next to the Cloud Cost column displaying the estimated monthly compute cost savings based on the uptime schedule of the associated suspension policy. If there is no suspension policy associated with the deployment, this column is populated with a link to Add Policy. If the deployment if terminated, this column is blank.

        • The Cloud Cost column is renamed Accrued Cost and displays the same data as before – the total compute and storage cost since the deployment was launched.

    • See Policies > Suspension Policies for additional context.

  • Instance Costs Column Name:

    • When you navigate to Admin > Clouds > Configure Cloud, the Cloud Accounts page displays a column that was called Last Billing Cycle in CloudCenter 4.9.0. This column name has been changed in CloudCenter 4.9.1 to Estimated Month to Date Cost. Correspondingly, the column row content link has been changed from View Invoice in CloudCenter 4.9.0 to Cost Details in CloudCenter 4.9.1. This is a change! 

    • See Manage Instance Types > Billing Cycle and Summary for additional details.

Administration and Governance

  • Compute Cost and Storage Cost:

    • Various public cloud providers have different billing cycles for their compute instances and the attached storage –the CloudCenter platform addresses these nuances between cloud providers and offers more granular cost reporting customized for the following cloud providers:

      • AWS

      • Google Cloud Platform

      • Microsoft Azure

    • For these public clouds:

      • When a VM or deployment is suspended, compute charges cease to accumulate.

      • Storage charges continue to accumulate until the VM or deployment is terminated.

    • The calculation considers all suspend and resume events for the VM or deployment since the last calculation. These updates occur at the top of the hour, when:

      • A VM or a deployment is manually suspended.

      • A deployment is automatically suspended due to a suspension policy. 

    • For VMs on all other public and private clouds, the one hour billing cycle model is used.

    • See Cloud Costs > Compute Cost and Storage Cost for additional context.

Security

No updates

End of Life Notices

See End of Support Notices for additional details.

Deprecated

  • The CloudCenter platform no longer supports the Sync Image Mapping functionality for Dimension Data environmentsThis is a change! 

CCM UI

  • Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers. 

  • LocalizationSee UI Behavior for additional context.

API

CloudCenter 4.9.1 introduces v2 APIs, where applicable. If a new API is introduced for the first time, it continues to use v1 as it is still the first version of that particular API. The following list differentiates between the New and Updated APIs for CloudCenter 4.9.0.

  • New APIs: The following API was added to the Suspension Policy APIs list.

Integrations

  • IPAM Callout ScriptThis is a change! 

    • The nicCount parameter is no longer a required parameter effective CloudCenter 4.9.1.

    • See Callout Scripts > Supported IPAM Properties for additional context.

Documentation

This section lists the documentation changes implemented in CloudCenter 4.9.1.

CloudCenter 4.9.1 has the following known issues:  

  • Deployment runtime data is sometimes off the mark for application deployment reports – When you create another cloud with the same name after deleting the existing cloud, then the run time number remains doubled for the the job deployed on those clouds.

  • CloudCenter 4.9.1 allows users to specify the service lifecycle actions that need to be run after a VM reboot. This functionality works for application deployments. It is not supported for the Deployment Resume flow.

  • The estimated monthly cost of VMs in the Managed VMs page should get adjusted if the suspension policy is associated with deployments. Currently, this estimated cost does not take suspension policy into account.

  • The Running VM History report does not account for VMs that are in the suspended state.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 4.9.1:

  • CSCvf60486: In case the job is in error state for azure cloud regions, PRE_VM_STOP and POST_VM_STOP scripts are NOT being executed.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that these scripts are successfully executed.

  • CSCvi24437: The Add Storage Type fields in the UI has incorrect names and units.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the right term and corresponding unit is displayed in the UI for these fields.

  • CSCvi28901Unable to deploy external service RDS MySQL in a restricted environment.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the CCM and CCO proxies settings can be configured to access the public network. See Proxy Settings for additional context.

  • CSCvi44711: Sometimes, fonts are not rendered correctly even if the liberation-mono-fonts package is installed on the AMQP server.
    Resolution:
    This was a known issue in CloudCenter 4.9.0. CloudCenter 4.9.1 provides a fix to ensure that these fonts are rendered legibly with the inclusion of dejavu-sans-mono-fonts along with liberation-mono-fonts.

  • CSCvi49062: If the name of the service deployment parameters is greater than 30 characters, a deployment that uses this parameter fails.
    Resolution
    In the CCM UI, the name field is allowed a maximum length of 40 characters and if this name field is assigned more than 30 characters and saved, then the deployment that uses this parameter is successful. 

  • CSCvi49925: Log messages in gateway.log displayed at the wrong level.
    Resolution: The log level was changed to WARN instead of ERROR in CloudCenter 4.9.1.

  • CSCvi49981The Custom Repository field in the CCO wizard is a required field and by default maps to repo.cliqrtech.comSetting up a custom repository on the worker cannot be skipped with an empty or configured value.
    ResolutionCloudCenter 4.9.1 includes an improvement that allows users to enter NULL ( case insensitive) in the CCO wizard menu > Agent Bundle >  Custom Repository field – this setting allows you to skip the custom repository configuration on the worker when using OS services like CentOS, RHEL, Ubuntu. However, you cannot use NULL as the value when using out-of-box (OOB) CloudCenter services as this value causes OOB services installations to fail.

  • CSCvi52040: When CloudCenter sends an email, the body of the email displays %EMAIL_HEADLINE% in the body of the email. In addition, some of the images that the email should display (logo, social media icon, and so forth) does not display even after changing the Desktop Outlook settings to download images when receiving email in HTML format.
    Resolution: CloudCenter 4.9.1 includes a fix to 
    remove the %EMAIL_HEADLINE% token. To view the images, you would need to accept certificates in the mail client, if the CloudCenter setup is using the default self-signed certificate.

  • CSCvi61147: The RDS MySQL out of the box service has a secret parameter of SA_Password that is not defined in the CloudCenter UI or the backend services database. If a clone is made of this service the parameters are not visible for the new service.
    Resolution: This is the current design - some parameters for a service are derived from the parent service (category) and will not be visible at the child service level.

  • CSCvi61499: The agent log issues the following message – Missing destination file operand after '/usr/local/cliqrstage/csagent/osmosix/service/' 
    Resolution: This is a warning message and can be ignored. CloudCenter 4.9.1 includes a fix to check this folder before copying the file and this message will no longer be issued.

  • CSCvi64689: The cco-installer.jar should exit if it does not have root access.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the installer process exits if the user's UID is not 0.

  • CSCvi77046: When system tags in an application profile are shared with another admin user, the shared admin user is not able to save the application without the system tags as they are auto-populated on the shared application profile.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that shared application profile allow shared users to remove the associated system tags.

  • CSCvi82831Custom repository configuration script is called on Windows worker by the agent. Windows agent log has error message about the custom repository configuration.
    Resolution: The custom repository configuration is only applicable to Linux workers. CloudCenter 4.9.1 includes a fix to call the custom repository configuration based on the OS.

  • CSCvi91300:  Using the SSH/RDP buttons on the Virtual Machine page results in a 404 error and SSH/RDP configuration on the deployment page displays a message stating that the user does not have SSH/RDP privileges.
    ResolutionCloudCenter 4.9.1 includes a fix to ensure that this option is not visible to users with only
     View permissions. Users require Manage permission to view this option that is only available on Managed VMs.  See the VM Management > Managed VMs for additional context.

  • CSCvi92428: While deploying an application to Google cloud Platform, with the Public IP disabled, the instance was assigned both a private and public IP address.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the 
    Public IP is not assigned to the network interface if the assign public IP flag is disabled.

  • CSCvi96114: A new Tenant Logo is not updated in the UI due to insufficient permissions on the logo file.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that this logo is updated as designed.

  • CSCvj08358: When upgrading from CloudCenter 4.8.0 to v4.8.2 installation, the config-server service fails to start because of a Git initialization issue.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the config server and all the related services come up even if it encounters this Git initialization issue.

  • CSCvj09379: While launching an MySQL RDS service via CloudCenter, it sets publicly-accessible parameter to true, by default, as the syntax is incorrect in the script. 
    Resolution: CloudCenter 4.9.1 introduces a new deployment parameter, cliqrIsPublicAccessible, for RDS service which can be toggled to true / false to control public accessibility.

  • CSCvj10862: The CCO or REPO components do not accommodate the default Docker image that is obtained via the internet. The proxy setting introduced in CloudCenter 4.9.0 does not modify the Docker file or daemon.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that users can configure the proxy values for these environments by using the CCO config wizard and setting the proxy values for the proxy server. See Proxy Settings for additional context. The 
    proxy values set using the CCO wizard also works for Docker services.

  • CSCvj13372: On the Deployments page of CCM UI when the RDS service is deployed no VPC network can be selected.
    Resolution: This is not a bug. See Services > RDS – the
     selection of a specific dbSubnetGroup in a VPC is completely driven by 2 parameters: vpcId and dbSubnetGroup. You must provide these values during a manual deployment or when you use them as needed. In CloudCenter 4.9.0, these two parameters are also added as deployment variables so you can pass the, as parameters during deployment.

  • CSCvj16103Add a new menu item in repo_config_wizard.sh script which allows users to add a proxy server. This value is required as an environment variable which is used for rsync proxy settings.
    Resolution: The option to set proxy is now available in CloudCenter 4.9.1 as an enhancement. See Repo (Conditional) or REPO Upgrade (Conditional) for additional context. 

  • CSCvj24881: The Invalid Instance Type ELB provided for app tier awselb_1 error message appears when deploying a Virtual Private Cloud with load balancing (ELB, based on cloud provider AWS). 
    Resolution: This issue could not be reproduced and did not appear under the same circumstances during the CloudCenter 4.9.1 testing. It is listed here for completion.

  • CSCvj36010: An error message shown on the job details page does not have enough details about the deployment failure when the error has occurred on the cloud provider side. Error messages are not propagated to the CCM from CCO’s cloudblade service. 
    Resolution: CloudCenter 4.9.1 includes a fix to collect all errors that occurred on the cloud provider side and display a consolidated list in the job details page if the deployment fails.

  • CSCvj36411: The custom repository configuration is not done for Ubuntu16.04 as it is not handled in the custom_repo_util.sh script.
    ResolutionCloudCenter 4.9.1 includes a fix to handle the custom repository configuration for Ubuntu16.04.

  • CSCvj36493When deploying a Linux image (reported with Ubuntu 16.04), the agent creates /root/swapFile1  with permissions at 0644 (rw-r-r). These permissions should be changed to 0600 (-r-----) as any accidental assignments by the root user can make this file world-readable.
    Resolution: CloudCenter 4.9.1 includes a fix to change the permissions for this file to 0600 (-r-----).

  • CSCvj64468: A user was unable to delete a cloud account due to an association with a phantom running Job. The user was able to delete the deployment environment, but not the cloud account.
    ResolutionThis is because some of the jobs in this environment were still in the JobCanceling and JobRejected states. CloudCenter 4.9.1 includes a fix to ensure that the status for these job deletions are verified before the Cloud Account deletion is initiated.

  • CSCvj64693: App profiles using a custom service that are exported from a tenant cannot be imported to a sub-tenant even when the service is shared.
    ResolutionCloudCenter 4.9.1 includes a fix to ensure that application profiles and associated services can be imported by sub-tenants with view permissions on the service.

  • CSCvj71771In the Virtual Machines page, if the user selects x number of VMs and then selects an action from the Action Library, then x number of queries are executed on each VM instead of 1. Therefore, the total number of queries executed will be x^2.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the logic to execute the action for x number of VMs is just 1, instead of x.

  • CSCvj73129: In the CloudCenter agent, the AMQP heartbeat is sent every 30 seconds, and if 2 heartbeats are missed, the agent will fail and a manual restart of the agent is needed.
    Resolution: CloudCenter 4.9.1 includes a connection timeout of 60 seconds with 20 retries and a 15-second interval between each retry.

  • CSCvj73140: Unable to deploy a Windows Server 2012 worker image that is created using cliqr_installer.exe from CloudCenter 4.9.0 in a VMware environment. 
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that this installer works as designed.

  • CSCvj89282: A user installed CloudCenter 4.9.0.1 and configured the proxy settings using the wizard. However, these settings were not visible in the gateway.conf file. 
    Resolution: CloudCenter
     4.9.1 includes a fix to address this issue. See Proxy Settings > 4.9.1 configuration for additional details.

  • CSCvj97648: The Java that is packaged with the worker in CloudCenter 4.8.2 has a Java security vulnerability.

  • Resolution: The CloudCenter 4.8.2 worker appliance has Java version 1.8.152 installed by default in the standard location for Java: /usr/local/c3agent/jre1.8.0_152. New deployments created with CloudCenter 4.9.1 have workers appliances that use the most recent Java version. Core components with older Java versions must be manually updated for the core_upgrade.bin by using the core_upgrade.bin <os> <cloud> java command to ensure that the latest compatible Java version is being used with each CloudCenter release. See Java Version Compatibility for additional context.

  • CSCvk06362: A password used in an External Service is displayed in clear text in the CCM log file.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that the password displayed in the CCM log file is redacted.

  • CSCvk20349: A Windows Server deployment fails if the Hostname Callout is configured as Instance Naming Strategy in an AWS cloud region setup.
    Resolution: CloudCenter 4.9.1 includes a fix to ensure that Windows Server deployments work when the Hostname Callout is configured on AWS environments.


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