MySQL for Pivotal Platform
Note: Pivotal has renamed MySQL for Pivotal Cloud Foundry to MySQL for Pivotal Platform.
Note: Pivotal has renamed Pivotal Cloud Foundry to Pivotal Platform.
Page last updated:
This topic provides an overview of the on-demand MySQL for Pivotal Platform service.
MySQL for Pivotal Platform enables developers to provision and use a dedicated instances MySQL database on demand. When you install MySQL for Pivotal Platform, the tile deploys and maintains a single service broker that integrates MySQL for Pivotal Platform with Pivotal Platform.
MySQL for Pivotal Platform is configured with sensible settings by default so that the service meets user expectations for a general-use relational database
MySQL for Pivotal Platform supports the following VM topologies:
- Single node.
- Leader-follower. For more information, see About Leader-Follower.
Highly available (HA) cluster. For highly available clusters MySQL for Pivotal Platform uses a patched Galera Cluster named Percona XtraDB Cluster (PXC). For more information about PXC, see Percona XtraDB Cluster.
Warning: Highly available plans are in general availability (GA). However, they are for advanced use cases only.
The following table provides version and version-support information about MySQL for Pivotal Platform.
|Release date||January 21, 2020|
|Software component version||Percona Server v5.7.28-31|
|Compatible Pivotal Operations Manager versions||2.8, 2.7, 2.6, and 2.5|
|Compatible Pivotal Application Service (PAS) versions||2.8, 2.7, 2.6, and 2.5|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
MySQL for Pivotal Platform is an on-demand service. This means that the service provides dedicated instances of MySQL that developers can provision on-demand using the cf CLI or Apps Manager.
With MySQL for Pivotal Platform you have more options for how and when instances are provisioned. MySQL for Pivotal Platform enables both the operator and developer to configure MySQL settings and resource use.
The MySQL for Pivotal Platform on-demand service uses the on-demand service broker. For information about the on-demand service broker, see On-Demand Services SDK.
MySQL for Pivotal Platform offers an on-demand service plan called
Operators can configured and update the plan settings.
When operators update the VM or disk size these settings are applied to all existing instances. If an operators decreases the disk size, data loss might occur in existing instances.
Review the following table to determine if MySQL for Pivotal Platform has the features needed to support your enterprise:
|Plans and Instances||More Information|
|On-Demand, Dedicated-VM Plans||MySQL for Pivotal Platform provides on-demand service plans.||On-Demand Networking|
|Customizable Plans||Operators can customize the VM, disk size, and availability zone for service plans.||Configure Service Plans|
|Custom Schemas||MySQL for Pivotal Platform supports custom schemas. Using custom schemas enables apps to share a MySQL service instance and isolate app data by schema.||Use Custom Schemas|
|Share Service Instances||MySQL for Pivotal Platform supports sharing service instances between different orgs and spaces.||Share Service Instances|
|Installation and Upgrades||More Information|
|Product Upgrades||MySQL for Pivotal Platform can be upgraded within the v2 tile series.||Upgrading MySQL for Pivotal Platform|
|Deployment Smoke Tests||MySQL for Pivotal Platform installations and upgrades run a post-deployment BOSH errand that validates basic MySQL operations.||smoke-tests|
|Maintenance and Backups||More Information|
|Operational Monitoring and Logging||MySQL for Pivotal Platform provides metrics for monitoring service plan usage, service quotas, and MySQL component metrics. MySQL for Pivotal Platform can also forward metrics to an external service.||Monitoring MySQL for Pivotal Platform|
|Backup and Restore||MySQL for Pivotal Platform provides automatic backups to an external storage solution on a configurable schedule. MySQL for Pivotal Platform alsp provides a restore process.||Backing Up and Restoring MySQL for Pivotal Platform|
|Scale and Availability||More Information|
|On-Demand Plans||MySQL for Pivotal Platform provides up to 200 on-demand instances across all plans.|
|Scaling||Operators can scale size of VMs up, but not down.||Installing Configuring MySQL for Pivotal Platform|
|Rolling Deployments||MySQL for Pivotal Platform supports rolling deployments when upgrading HA clusters. However, single node and leader-follower service instances are unavailable during upgrades.||Upgrading MySQL for Pivotal Platform|
|AZ Support||MySQL for Pivotal Platform can be deployed to multiple zones to ensure availability if an unplanned outage of a zone occurs.||About Availability Zones|
|Transport Layer Security (TLS)||MySQL for Pivotal Platform supports TLS. Enabling TLS provisions a MySQL server with a certificate so that apps and clients can establish an encrypted connection with the data service.||Preparing for TLS|
|Encrypted Communication in Transit||MySQL for Pivotal Platform has been tested successfully with the BOSH IPsec Add-on.||IPsec Add-on|
|Encrypted Data at Rest||MySQL for Pivotal Platform enables integration with commercial vendors for full-disk encryption at rest.||Thales Vormetric plugin|
MySQL for Pivotal Platform supports configuring multiple availability zones (AZs). However, assigning multiple AZs to MySQL jobs does not guarantee high availability.
- You can assign on-demand plans to any of the configured AZs.
- BOSH randomly deploys service instances across configured AZs. This minimizes the impact of an AZ outage and removes single points of failure.
- For all MySQL for Pivotal Platform plans, select three AZs. Choosing three AZs does not increase the number of AZs assigned to service instances to three.
Please provide any bugs, feature requests, or questions to the Pivotal Platform Feedback list.