Hazelcast IMDG Enterprise for Pivotal Cloud Foundry
This documentation describes how to install, configure, and use Hazelcast IMDG Enterprise for Pivotal Cloud Foundry (PCF). Hazelcast IMDG Enterprise for PCF registers a service broker on PCF and exposes its service plans on the Marketplace. Developers can provision Hazelcast clusters by creating instances of the service plans using the Cloud Foundry Command Line Interface (cf CLI).
Hazelcast IMDG Enterprise for PCF uses an on-demand services SDK, which is a part of Pivotal Cloud Services SDK, to fully utilize BOSH v2 features and let you provision instances more flexibly.
Features of Hazelcast IMDG Enterprise for PCF include the following:
- Based on Hazelcast IMDG Enterprise, the leading in-memory data grid (IMDG)
- The ability to dynamically pass your Hazelcast configuration in JSON format when creating services
- An on-demand service broker that dynamically creates and scales Hazelcast clusters without pre-provisioning blocks of VMs
The following table provides version and version-support information about Hazelcast IMDG Enterprise for PCF:
|Release date||April 11, 2019||May 20, 2019||April 19, 2019||February 21, 2019||December 20, 2018|
|Software component version||3.12||3.11.4||3.11.3||3.11.2||3.10|
|Compatible Ops Manager version(s)||v2.2, v2.3, v2.4, and v2.5||v2.2, v2.3, v2.4, and v2.5||v2.2, v2.3, v2.4, and v2.5||v2.2, v2.3, and v2.4||v2.2 and v2.3|
|Compatible Pivotal Application Services (PAS) version(s)||v2.2, v2.3, v2.4 and v2.5||v2.2, v2.3, v2.4 and v2.5||v2.2, v2.3, v2.4 and v2.5||v2.2, v2.3, and v2.4||v2.2 and v2.3|
|BOSH stemcell version||Ubuntu Xenial||Ubuntu Xenial||Ubuntu Xenial||Ubuntu Xenial||Ubuntu Trusty|
|IaaS support||All Reference Architectures||All Reference Architectures||All Reference Architectures||All Reference Architectures||All Reference Architectures|
WARNING: Hazelcast IMDG Enterprise for PCF v1.6.2 and earlier require a Ubuntu Trusty stemcell. The end-of-life date for Ubuntu Trusty is April 2019. If a security vulnerability is found on this stemcell after April, it will not be fixed.
If you change
managementCenterConfig in your JSON configuration file, then all VMs are shutdown at the same time. This means that you lose all the cluster data unless you are persisting that data elsewhere.