CliQr was first with a cloud-agnostic model. CliQr was the first with a combined infrastructure and application model. Now with another first, CloudCenter 4.4 is here and it’s stretched.
This latest release of CloudCenter has a wide range of improvements that take anther step forward with enhanced ease-of-use and flexibility. The result is that now applications can be deployed with individual tiers in separate datacenter or cloud. And built-in walk-throughs provide step by step guidance that leads users through common tasks, right from the user interface.
Highlight – Stretched Application Profile
Today’s savvy enterprise IT wants the flexibility to mix and match different resources, in different locations to deploy an application based on business requirements. CloudCenter 4.4 delivers the industry’s first cloud agnostic, stretched application profile that deploys tiers in different data centers, private, or public clouds based on cost, security and compliance, or HA/DR requirements.
Rarely are sets of resources the same. An enterprise might have high-IOPS, out-dated, secure, and/or compliant resources within their datacenter in addition to using at least 4 different cloud technologies, all with unique characteristic and capabilities. All of these resources have different costs based on the resources and maintenance. Instead of deploying an entire application to the highest (and thus most expensive and resource constrained) common denominator, it’s more cost effective to break the application tiers up. For example, a database requiring HIPAA or PCI compliance can remain within the datacenter in more expensive infrastructure while the application and web tiers can take advantage of greater scalability and pay-per-use economics of general use public cloud resources.
For more information about the CloudCenter Stretched Application Profile, stay tuned for an upcoming blog or request a demo.
- Feature Walk-throughs: users can walk step-by-step through 25+ product feature walk-throughs directly in the UI to minimize referencing documentation and requiring professional services
- Password Parameter Type: Previously, the password field type had a confirmation field as well as a check against CloudCenter’s password rules. The previous functionality is now called “Password with Confirmation”, and a new field type called “Password” has been added with no confirmation field or checking against CloudCenter’s password rules.
- Dynamic Parameter Lists: Using the “Web Service” parameter type, a drop down list’s values can be dynamically pulled from another system to decrease maintenance and chance of user error.
- Stretched Application profiles: With a single application profile, users can choose where individual tiers are deployed, without making any changes to scripts or orchestration. Users have always had the flexibility to choose where the full application stack is deployed. Now they have even more flexibility to choose were each tier is deployed. This feature supports more savvy IT departments that want to choose where tiers are deployed for cost, security and compliance, or HA/DR architectures.
- Added Support
- Dimension Data MCP 2.0 Support
- CloudStack Advanced Network Support
- External Service Logging and Messages: When using external services, logs will now be taken from the execution container and moved to the host for troubleshooting. Messages can also be posted to the deployment UI screen.
- Removed Azure MDS Requirement
Administration and Governance
- Deployment Environment Enhancements: Administrators are now able to add multiple accounts to one cloud in a deployment environment as well as set defaults for each cloud. This adds more flexibility to deployments along with making it easier for less technical users to deploy applications.
- Optional User Security Groups: For customers that have only a small limit of firewall rules on cloud accounts like AWS, a new tenant level option is available to stop CloudCenter from creating user security groups.
- Images Support vSphere Full and Linked Clones: CloudCenter images can now support vSphere full clones or linked clones. Full clones can be provisioned from VM Templates or VMs without snapshots. Linked clones require a VM with a snapshot.
- MariaDB Support: The CloudCenter Manager now supports MariaDB along with MySQL. New installations will be given a choice of databases during the installation.
- Upgrade to Java 8 and Tomcat 8: The Manager, Orchestrator, and AMQP server have all be updated to use Java 8 and Tomcat 8
- 3rd Party Library Updates: Some of the services in the services library’s have been updated to their latest versions including Spring, Hibernate, AWS Client, and Hazelcast
- Optional Installation of AMQP on CCM: RabbitMQ AMQP server can be installed on the CCM to take advantage of Enterprise Service Buses that a company might use.
The following APIs were introduced in this release:
- Migrate Deployment– while this API was already available in CloudCenter 3.x, CliQr documentation introduces it in this release.
The following APIs were updated in this release:
- Deployment Environment Management: Enhanced to reflect a modified associatedCloudsattribute – seeDeployment Environments for additional context. The associatedClouds attributes now includes the regionId of each associated cloud account and additionally contains new attributes called cloudAssociationDefaults anddefault.
- User Management: Enhanced to support user deletion based on the External ID.
- Job Management: Enhanced to include the mandatory metadata name-value attributes.
- No Updates