The CliQr team is proud to announce the general availability of CloudCenter 4.2 with a new devops and CI/CD automation feature, support for more clouds, and extended modeling functionality.
The CloudCenter 4.2 release puts a broad range of powerful new capabilities in the hands of customers. We have packed this release with great functionality like the new CICD Project Board, support for more clouds, ability to federate management appliances, integrated support for Chef and Puppet, improved integration with Jenkins, and extensible services to name a few.
Highlight – CICD Project Board
CloudCenter now includes a CI/CD Project Board which is the industries 1st end-to-end project management tool integrated with underlying cloud management platform. If you have implemented DevOps processes, or are contemplating Continuous Integration or Continuous Deployment, you can now build on CloudCenter’s powerful cross-cloud deployment and management capabilities, and now visualize and manage each project’s deployments at any phase in any combination of datacenter, private and public clouds.
When a developer makes a code change, Jenkins automates the build, and calls CliQr to deploy environment and the latest build. That deployment then appears in CloudCenter in the Project Board.
The Project Board helps DevOps teams automate and standardize the deployment of infrastructure AND application stacks into any datacenter or cloud environment, as well as visualize and manage each project’s end-to-end process.
- Puppet and Chef Services: CloudCenter now has improved integration with configuration management tools. These configuration management tools can deploy one or more nodes in a multi-tier Application Profile. From the topology modeler, users can drag and drop fully functional Puppet and Chef services into an application profile, allowing users to set properties that include Chef organizations, recipes, and environments or Puppet roles and environments.
- New Repository Support: To make utilizing to pre-built content even easier, CloudCenter now supports Amazon S3, Artifactory, Puppet, and Chef as repository connections. Any of these writable repositories, like S3, can also be used as a central repository for information while migrating applications from one deployment environment to another.
- New Service Definitions: When creating services, users now have the ability to choose from 3 new types of services:
- Virtual Machine with CliQr agent: This would be any service that comes as an appliance or install that you also want to manage with CliQr. This option was the only option in previous releases.
- Virtual Machine without CliQr agent: Services sometimes come in an appliance that should not be managed by CliQr or there is no way of installing the CliQr agent onto it. Examples of this might be an F5 load balancer appliance.
- External service: This opens up the doors to an endless amount of services. When this service is called, a script can run to call out to somewhere else and provision a service or connect to an existing resource. Examples for using this type of service would be if you want to use an AWS service that we don’t support out of the box or if you want to connect to a central database server. In both instances, CliQr would make the call out to the external system to complete the action of deploying the service as part of an Application Profile.
- Federated Managers: CloudCenter deployments now support multiple Managers. This is a great functionality for geographically dispersed companies that want to have centralized management, but want local-to-user manager servers to decrease latency to the user and deployment environment. Administrators can now install CliQr with a main Manager instance, and then federate other Manager instances into it. The solution will survive even if they momentarily lose connection from each other.
- Expanded OS support: Now, the Orchestrator and Manager appliances can be on CentOS 7 and RHEL 6/7
- Guacamole moving to AMQP server: In previous releases, the Guacamole service (necessary for providing SSH and VNC connections to deployed machines) lived on the Orchestrator appliance. Going forward from 4.2 it will now live on the AMQP server to make the configuration of firewall rules easier. If you’re running a previous release, you don’t need to make the change immediately, but we do recommend updating to this architecture. If you’re installing 4.2 or after as a fresh installation, this will be automatically taken care of for you.
Clouds and Integrations
- New Cloud Support: CloudCenter supports four additional clouds.
- Azure Pack
- SoftLayer Bare Metal
- Bracket Computing
- vCenter 6.0/6.0U1 Support
Administration and Governance
- Cross Tenant Sharing: Parent tenants will be able to share application profiles, services, tags, and security profiles with their sub-tenants.
- AWS STS and IAM role support: Amazon Security Tokens can now be used in order to allow an Orchestrator to use Amazon’s IAM service for authentication to AWS.
- Containers for System Callouts: To ensure that the new external services functionality remains secure and cannot impact the CloudCenter appliances, all external services commands are run on the Orchestrator within their own isolated container which is created and then immediately destroyed.
- New APIs:
- Tenant Management
- Permissions Management
- Project Management
- Phase Management
- Custom Actions Management
- The following APIs were enhanced to include the supportsHardwareProvision and the localStorageCountattributes:
- The following APIs were enhanced to change category to profileCategory:
- No Updates