MySQL for Pivotal Cloud Foundry
This guide describes setting up and using MySQL for Pivotal Cloud Foundry (PCF) as an on-demand service.
Note: This documents MySQL for PCF v2.0, an on-demand service that creates dedicated, single-tenant service instances dynamically. For the older, pre-provisioned service, see the v.1.9 documentation here or select v1.9 from the dropdown above.
MySQL for PCF enables PCF app developers to provision and use a MySQL database with a single command.
MySQL for PCF v2.0 introduces a new type of service, an on-demand service. MySQL for PCF v2.0 replaces the pre-provisioned service that was in the v1.x series.
This table summarizes the main differences between the two:
|Available since||VMs it runs on||How VMs are created||Metrics name prefix|
|On-Demand Service||New for v2.0||Dedicated VM that serves a single service instance||PCF creates each VM on-demand when app developer creates service instance||
|Pre-Provisioned Service||v1.4||Multi-tenant VMs shared by apps across PCF deployment||PCF creates all VMs when operator deploys or updates service||
The following table provides version and version-support information about MySQL for PCF.
|Release date||July 31, 2017|
|Software component version||Percona Server v5.7.18–14|
|Compatible Ops Manager version(s)||v1.10.x, v1.11.x|
|Compatible Elastic Runtime version(s)||v1.10.11 and later, v1.11.x|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
The MySQL for PCF product delivers dedicated instances on demand, “Database as a Service”, to Cloud Foundry users. When installed, the tile deploys and maintains a single Service Broker that is responsible for Cloud Foundry integration. The service is configured with sane defaults, following the principle of least surprise for a general-use relational database service.
For more information about MySQL for PCF v2.0 see the product’s Minor Overview.