The CliQr team is proud to announce the latest release of CloudCenter. Version 3.2.5 includes updates to both CloudCenter Manager and Orchestrator, as well as support for new cloud services, architectural changes, security enhancements, and API updates.
Custom Service with Lifecycle Management – Tenant admins can now create and manage custom services in addition to CliQr provided out-of-box services such as databases like MySQL and Middleware components such as Tomcat, Apache HTTP Server. A new “Services” tab is used to define custom services and configure lifecycle actions such as start, restart, stop, upgrade, and cleanup. All users within a tenant group can include a custom service when modeling and publishing applications to the application marketplace. For example, a user may choose to build An example might include a custom Oracle WebLogic service based on a company specific hardened base OS image such as RHEL, CentOS, or Oracle Enterprise Linux.
“SaaS App” Profile – SaaS applications can now be published to the application marketplace just like any other application. The SaaS App profile includes the application URL and any other required launch parameters. IT organizations can now use CloudCenter as a single service portal for both SaaS and traditional applications.
Nested Application Profile – The topology builder now supports using a published application as part of an N-tier application profile. Complex application profiles may recursively source other application profiles eliminating the need to hardcode deployment parameters. Parameters such as IP addresses may be passed from profile to a sub-profile.
Deployment Environment –Deployment environments offer flexibility when granting a user shared access to multiple development and production accounts within a cloud. This was previously optional, but is now required. A CloudCenter upgrade to 3.2.5 will create a default deployment environment for all user profiles.
Amazon Spot Instance – Users can now use CloudCenter to bid on Amazon EC2 spot instances in addition to on-demand instances which can significantly reduce the cost of high performance computing jobs.
Microsoft Azure Endpoint Access - Every tier can include an “Add Access End Point” value that controls/restricts access via the Internet.
VMware Root Disk Resize – Users can specify root disk size for VMware virtual machines according to OS type.
VMware Dynamic resource enumeration – vCenter resources are automatically discovered and exposed as a deployment option during configuration.
External Storage Repository – Customers can now source external storage repositories in addition to CloudCenter’s shared storage. Files are retrieved from an external location using a URL. Users may also choose to use a combination of external repository for binary files and CloudCenter Storage for scripts.
Agentless Install – CloudCenter can now launch applications without installing the virtual machine agent or relying on CloudCenter’s dynamic agent bootstrapping. This may be useful in scenarios where dynamic bootstrapping is not desirable or where java cannot be installed inside the VM image.
HTML5-based remote access – A new HTML5-based SSH/VNC option is available for one-click node access. Users may continue to use JNLP-based SSH/VNC for browsers that don’t support HTML5, or if access to the proxy server is blocked
FIPS Certified Crypto Library – CloudCenter is now FIPS compliant. The FIPS-compliant Java Cryptography Architecture (JCA) contains the provider architecture and the APIs for digital signatures, message digests (hashes), certificates and certificate validation, encryption, key generation and secure random number generation, and other standards.
Tenant UI for Firewall rules – Effective CloudCenter 3.2.5, no default ports are opened for network communication. The tenant admin can configure firewall rules by opening the required ports for each cloud region.
- allVersions – get a list of all versions of an Application.
- Environments – List all accessible deployment environments for a particular user, or retrieve details about a specific environment. Can also be used to create or update an environment.
- jobID – returns status of job and VM, and has been enhanced to access resource details via URL including N-tier web applications as well as SaaS applications.
- allowedClouds – has been depricated in 3.2.5, but remains backward compatible with CloudCenter 3.2.4. Instead, use the associatedClouds to display clouds contained in a deployment environment.
Additional Resources related to CloudCenter 3.2.5: