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.2, an on-demand service that creates dedicated, single-tenant service instances dynamically. For the older, pre-provisioned service, see the v1.10 documentation here or select v1.10 from the drop-down menu above.
MySQL for PCF enables PCF app developers to provision and use a MySQL database with a single command.
The MySQL for PCF product delivers dedicated instances on demand, “Database as a Service”, to PCF users. When installed, the tile deploys and maintains a single Service Broker that is responsible for PCF 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.2, see Minor Overview.
MySQL for PCF v2 introduces a new type of service, an on-demand service. MySQL for PCF v2 offers an alternative to 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||Dedicated instance VM(s) dynamically provisioned on demand.||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||February 16, 2018|
|Software component version||Percona Server v5.7.20-19|
|Compatible Ops Manager version(s)||v1.12.x and v2.0.x|
|Compatible Elastic Runtime* version(s)||v1.12.0|
|Compatible Pivotal Application Service (PAS)* version(s)||v2.0.x|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
* As of PCF v2.0, Elastic Runtime is renamed Pivotal Application Service (PAS). For more information, see Pivotal Application Service (PAS) Highlights.
Some PCF services offer on-demand service plans. These plans let developers provision service instances when they want.
These contrast with the more common pre-provisioned service plans, which require operators to provision the service instances during installation and configuration through the service tile UI.
The following PCF services offer on-demand service plans:
MySQL for PCF v2.0 and later
RabbitMQ for PCF
Redis for PCF
Pivotal Cloud Cache (PCC)
These services package and deliver their on-demand service offerings differently. For example, some services, like Redis for PCF, have one tile, and you configure the tile differently depending on whether you want on-demand service plans or pre-provisioned service plans.
For other services, like PCC, you install one tile for on-demand service plans and a different tile for pre-provisioned service plans.
The following table lists and contrasts the different ways that PCF services package on-demand and pre-provisioned service offerings.
|PCF service tile||Standalone product related to the service||Versions supporting on demand||Versions supporting pre-provisioned|
|RabbitMQ for PCF||Pivotal RabbitMQ||v1.8 and later||All versions|
|Redis for PCF||Redis||v1.8 and later||All versions|
|MySQL for PCF||MySQL||v2.x
(based on Percona Server)
(based on MariaDB and Galera)
|PCC||Pivotal GemFire||All versions||NA|
|GemFire for PCF||Pivotal GemFire||NA||All versions|
Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.