CliQr is now part of Cisco Learn More About Cisco

Cisco CloudCenter 4.7.0 Release Notes

Release Date

January 6, 2017

Architecture

No updates.

Install

  • You now have the following configuration options:
    • Separate appliances are available for CCM (CCM_SA) and Database (MGMTPOSTGRES), so they can be configured on different VMs, if required. These appliances can also be used to configure CCM in HA mode. See Appliance Installation for additional context.

    • CCO HA directly on the CCO_PRIMARY wizard for a 3-node MongoDb cluster setup.
      • CCO HA Setup now requires 3 VMs to support a 3-node MongoDB cluster. In addition to CCO_PRIMARY & CCO_SECONDARY, a new role CCO_TERTIARY has been added. See Component Modes and Roles for additional details.

      • You can configure CCO HA by running the configuration wizard on any one of the 3-nodes.

      • See Per CloudCenter Region Installation (Required) > 4. Install CCO (Required) > CCO HA > CloudCenter 4.7 for additional context.
      • See HA Best Practices > CCO High Availability for additional context.
    • GUAC HA (Connection Broker) is now supported:
  • Port Changes:
    • EXT_Script_Executor:

    • Monitor:

      • 8881- incoming from CCM roles

      • 8882 – incoming from browser clients

      • 4560 – incoming from CCM & CCO roles

      • See Monitor Network Rules for additional context.

Upgrade

  • The core_upgrader.bin file IS REQUIRED to upgrade all components from CloudCenter 4.6.x to CloudCenter 4.7.0.
  • CloudCenter installations of pre-4.6 releases cannot be directly upgraded to 4.7.0. You must first upgrade to CloudCenter 4.6 first before upgrading to 4.7.
  • See Upgrade in Non-HA Mode and Upgrade in HA Mode for additional context.

Clouds

  • New Cloud Regions:

    • AWS: Canada (Central)

    • Dimension Data: US - East 3 - MCP 2.0  NA9
    • IBM SoftLayer: Softlayer-sao-01 (Sao Paulo 01)
    • See Public Clouds for a complete list.
  • Deleting Cloud Regions
    • You can now delete Cloud Regions even after CCO has been registered.

    • Cloud owners can delete regions if there are no running deployments and no association of the region in a Deployment Environment – If there are any, remove them first before trying this operation.

    • Ensure that all the jobs submitted in this region have already been terminated.

    • See Cloud Region Configuration > Delete Cloud Region for additional context.
  • Configuring Clouds:
    • You can configure a VMware vCloud Director (vCD) 8.1 cloud.
    • See Configure Cloud(s) > Configure a vCD Cloud for additional context.

Model, Deploy, and Manage

  • Root Volume Size:

    • The Amazon deployment flow has a new field to specify the Root Disk Size so you can resize the root disk as part of the image.

    • To provide a larger size for root volume for an AWS environment, use the newer generation of CloudCenter instance types. This configuration, by default, uses the AMI's root volume size.

    • The older generation of instance types like the t1, m1 series do not support the resizing of root volume. To use the older generation of instance types, configure the root volume size as 0 (zero). 

    • See Multiple Volumes and the Submit Job (v2) API for additional context.
  • Scaling within Clustered Services:
    • You can now add or reduce the number of nodes within a clustered service.
    • See Service Administration for additional context on Service Clustering.

Administration and Governance

  • Storage Cost:
    • The CloudCenter platform now accounts for the storage cost along with the compute cost when billing jobs.
    • The cloud storage billing includes the amount of storage used, snapshots, and is based on the storage type and associated properties like IOPS.
    • See Configure Cloud Storage and Cloud Storage Management APIs for additional context.
  • Download Logs:

    • Log files can be downloaded for CCM and CCOs.

    • You can search within each downloaded log file based on the Deployment’s JobName or Job ID to retrieve information about a particular deployment.

    • Log files for each component can now be downloaded centrally from the UI by using the Elasticsearch, Logstash, and Kibana (ELK stack) which is installed by default along with the Health Monitor component.

    • You can configure this feature when you configure the CCM Properties and the CCO Properties using the respective wizards.

    • To configure the required ports, see Phase 2: Configure Network Rules > Monitor Network Rules section.

    • You can search within each downloaded log file based on the DeploymentJobName or DeploymentJobID to retrieve information about a particular deployment.
    • See Download Log File for conceptual and UI context and Download Logs for the API context.
  • Running VM History Report:
    • The Running VM History report provides a snapshot and usage pattern for VMs for your tenant hierarchy.

    • See Running VM History Report for the UI context.

Security

The following changes are made at the OS level and not directly visible to CloudCenter users:

  • Enabling OS Firewall (iptables) to Ensure OS-level Protection – Only specific ports required by the respective components are allowed and the remaining incoming ports are blocked.
  • Enabling SELinux:
    • If the base OS has SELinux enabled then the CloudCenter platform also enables SELinux – When using installers, SELinux is enabled or disabled based on their status in base OS image used.
    • Appliance for all components are enabled by default with SELinux

  • Redoing Weak Ciphers – The CloudCenter platform no longer uses weak ciphers to ensure cipher hardening.
  • Hardening IPv4 Networks – The CloudCenter platform uses the sysctl interface to securely harden the IPv4 network.

  • Permission – IPAM scripts run as cliqruser. See Callout Scripts > Permissions for additional context.

Integrations

The following integration capabilities extend the CloudCenter platform capabilities:

  • Resource Placement allows users to define cloud settings based on third-party infrastructure tools or quota management tools using automated scripts instead of manually-selected settings.
  • Resource Validation blocks new deployments, if users reach a configured threshold limit when using Cloud Resources (for example, restricting VMs being launched only if cloud resources consume < 75% of your maximum capacity).
  • See Resource Placement and Validation for additional context.

Deprecated

No updates.

CCM UI

See the links provided in this page for additional context on UI changes for this release.

API

CLI

No updates.

Documentation

Known Issues

CloudCenter 4.7.0 has the following known issues:

  • If the value of a custom parameter or a global parameter contains the $ character, then you cannot use this parameter in macros.
  • Storage-as-a-Service (NFS/CephFS) deployments cannot be used to mount other application deployments.

  • Tenants other than Root admin cannot sync instance types or images even if they are the cloud owners.

  • Security profiles cannot be deleted, if any region is down.

  • When using callout scripts, the re-inject setting in the callout.conf file is ignored.

Resolved Issues

The following issues were resolved/addressed in CloudCenter 4.7.0:

  • Issue: The CCO server fails with a Command not found message when you launch a VM on VCD as the vcdconfig file is not available.
    Resolution: CloudCenter 4.7.0 provides a fix to address this issue. The vcdconfig file is now available in the /usr/local/osmosix/bin/ folder.

  • Issue: If a job contains an external service, the Suspend action is not listed in the responses for the List Jobs (v1) and the Get Job Details (v2) APIs.
    Resolution: CloudCenter 4.7.0 includes a fix to ensure that suspend/resume actions are available for external services using these two APIs. Additionally, a warning message is displayed when you try to suspend deployments with external services. The external services are terminated on suspend and recreated on resume.
  • Issue: Using the $ character in a custom parameter for the Password Type does not allow the password value to pass through.
    Resolution: Parameters with a value that contains the ‘$’ symbol work but the parameter cannot be used as a macro in the application profile.
  • Issue: The cliqrIgnoreAppFailure parameter is not honored when a deployment is scaled.
    Resolution: CloudCenter 4.7.0 provides a fix to ensure that VMs that were added during scaling are not terminated if they go to an error state, when cliqrIgnoreAppFailure = true is specified.
  • Issue: If the CCM and CCO lack connectivity neither the CCM nor the CCO API calls reach their respective destinations. This disconnect prevents the UI from being updated with the current deployment status and the CCO from receiving actions. 
    Resolution: Effective CloudCenter 4.7.0, the communication between the CCO and CCM is persisted, ensuring that API calls reach their respective destinations once the connectivity is restored.
  • Issue: When users are deleted from the CloudCenter platform, it removes them from the system but the data associated with their account is not purged from the database.
    Resolution: CloudCenter 4.7.0 include a flag that allows you to purge or retain user data by editing the vendor.properties file's purge.useraccount flag. This file is located at /usr/local/tomcat/ROOT/WEB-INF/vendor/tenantId/vendor.properties.
  • Issue: The Node Resume workflow fails when a service script is defined in the application profile for Windows 2012.
    Resolution: Effective CloudCenter 4.7.0 the Node Resume workflow completes successfully even if a service script is used.
  • Issue: Error when deploying an external service with an ACI environment.
    Resolution: CloudCenter 4.7.0 includes a fix to ensure that empty ACI fields no longer prevent the external service deployment from completing as these field settings are now optional.
  • Issue: When a SSO user access CCC the first time and the user has not been activated, the user receives the Account validation failed message that contain multiple spelling errors.
    Resolution: CloudCenter 4.7.0 includes a fix to correct these errors.
  • Issue: The CCM UI > Deployments screen displays unreasonable VM Hours.
    Resolution: CloudCenter 4.7.0 includes a fix to calculate the VM Hours for external services accurately.
  • Issue: The Restful JSON output displays hidden parameters.
    Resolution: CloudCenter 4.7.0 includes a fix to ensure that hidden parameters are not displayed in the Restful JSON output but are received as designed by the CloudCenter platform.
  • Issue: When a multiple service parameters of type textarea and text are added to a service definition, then the service was not saved when using the CCM UI.
    Resolution: CloudCenter 4.7.0 includes a fix to save a service definition when multiple service parameters of type textarea and text were added and this feature now works as designed.
  • Issue: A user is able to terminate an application despite one node is powered-off.
    Resolution: Effective CloudCenter 4.7.0, if any of the VMs are in a powered off state and you try to terminate a deployed application, you receive a warning message: One or more nodes associated with this deployment are suspended or not reachable. Any cleanup scripts specified in the application profile may not be executed for these nodes. Please power on the nodes before termination to ensure proper cleanup.
  • Issue: When users request a Jetty product and remotely connect to the server with Jetty installed, they have no indication that the jetty daemon is for CliQr and that the jetty2 daemon is the Jetty service. It would be much simpler if the jetty daemon was renamed to cliqr.
    Resolution: CloudCenter 4.7.0 includes a fix to ensure that the jetty daemon points to the C3AgentServer.
  • Issue: When a script (for example, the node-init script) tries to modify a file in an application package (for example, to replace macros) or another script (such as a database setup script) that is downloaded by the agent, then the script fails with a permission denied error.
    Resolution: Effective CloudCenter 4.7.1, permissions on worker script files and application packages downloaded at the base location /opt/remoteFiles are owned by the cliqruser.

 

 

 

 

  • No labels