MySQL for PCF v2.0

MySQL for Pivotal Cloud Foundry (Pre-Release)

This guide describes setting up and using MySQL for Pivotal Cloud Foundry (PCF) as an on-demand service.

IMPORTANT: This version is a pre-release and is not intended for production use.

About MySQL for PCF

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 p.mysql (with a dot)
Pre-Provisioned Service v1.4 Multi-tenant VMs shared by apps across PCF deployment PCF creates all VMs when operator deploys or updates service p-mysql (with a dash)

Product Snapshot

The following table provides version and version-support information about MySQL for PCF.

Element Details
Version v2.0.0
Release date April 15, 2017
Software component version Percona Server v5.7.17-13
Compatible Ops Manager version(s) v1.10.x
Compatible Elastic Runtime version(s) v1.10.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.

When installed, developers can attach a database to their applications in as little as two commands, cf create-service and cf bind-service. Connection credentials are automatically provided in the standard manner. Developers select from a menu of service plans options, which are configured by the platform operator.

Each instance of the service offering meets the following criteria:

MySQL Server1 dedicated VM
Service Broker1 dedicated VM
High Availabilityn/a
Multi-AZ SupportYes
Rolling Upgradesn/a
Automated BackupsYes
Customizable PlansYes
Customizable VM InstancesYes
Plan MigrationsYes
Encrypted CommunicationYes ✝
Encrypted Data at-restn/a
Long-lived Canariesn/a

(*) vSphere only, v1.7 and earlier
(✝) Requires IPSEC BOSH plug-in

Create a pull request or raise an issue on the source for this page in GitHub