MySQL for Pivotal Cloud Foundry
Note: This version of MySQL for Pivotal Platform is no longer supported because it has reached the End of General Support phase. To stay up to date with the latest software and security updates, upgrade to a supported version.
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.4, an on-demand service that creates dedicated, single-tenant service instances dynamically. For the older, pre-provisioned service, see the v1.10 documentation 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.4, 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 an app developer creates service instance||
|Pre-Provisioned Service||v1.4||Multi-tenant VMs shared by apps across PCF deployment||PCF creates all VMs when the operator deploys or updates service||
The following table provides version and version-support information about MySQL for PCF.
|Release date||June 13, 2019|
|Software component version||Percona Server 5.7.24-26|
|Compatible Ops Manager version(s)||2.2, 2.3, and 2.4|
|Compatible Pivotal Application Service (PAS) version(s)||2.2, 2.3, and 2.4|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
As well as MySQL for Pivotal Platform, other Pivotal Platform services offer on-demand service plans. These plans let developers provision service instances when they want.
These contrast with the older pre-provisioned service plans, which require operators to provision the service instances during installation and configuration through the service tile UI.
The following table lists which Pivotal Platform services offer on-demand and pre-provisioned service plans:
|Pivotal Platform service tile||Standalone product related to the service||Supports on-demand||Supports pre-provisioned|
|RabbitMQ for Pivotal Platform||Pivotal RabbitMQ||Yes||Yes. Only recommended for test environments.|
|Redis for PCF||Redis||Yes||Yes (shared-VM plan). Only recommended for test environments.|
|MySQL for Pivotal Platform||MySQL||Yes
|Pivotal Cloud Cache (PCC)||Pivotal GemFire||Yes||No|
For services that offer both on-demand and pre-provisioned plans, you can choose the plan you want to use when configuring the tile.
Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.