Overview of MySQL for PCF v2
This topic describes the significant features in MySQL for PCF v2. This topic also presents a checklist that you can use to decide if MySQL for PCF is ready to meet your business requirements.
MySQL for PCF v2 introduces the On-Demand Service, which provides dedicated instances of MySQL that App Developers can provision on-demand from the command line. The MySQL for PCF On-Demand service is designed to improve the flexibility in how and when instances are provisioned and allows for more efficient and seamless resource use for both Operator and App Developer. Additionally, both Operator and App Developer can configure essential MySQL settings. MySQL for PCF v2 can be installed alongside the earlier MySQL for PCF v1.x tiles.
MySQL for PCF’s On-Demand Service leverages the on-demand service broker.
PCF MySQL offers five on-demand plans as the
p.mysql service within the PCF MySQL tile.
The plans can be configured in any way that you see fit.
However, plans should be configured such that they increase in size.
For each service plan, the operator can configure the Multi-Node, Plan name, Plan description, Server VM type and Server Disk type, or choose to disable the plan completely.
Operators can update certain plan settings after the plans have been created. If the Operator updates the VM size or disk size these settings will be implemented in all instances already created. Operators should not downsize the VMs or disk size as this can cause data loss in pre-existing instances.
Review the following table to determine if MySQL for PCF v2 has the features needed to support your enterprise.
|Plans and Instances||More Information|
|On-Demand, Dedicated-VM plans||MySQL for PCF provides On-Demand VM plans||Architecture|
|Customizable plans||For the On-Demand Plan, the operator can customize the VM, disk size, and availability zone.||Configuring|
|Custom schemas||MySQL for PCF supports custom schemas. Using custom schemas allows for apps that share a MySQL service instance to isolate app data by schema.||Create and Use Custom Schemas|
|Installation and Upgrades||More Information|
|Product upgrades||MySQL for PCF can be upgraded within the v2.x tile series. Additionally, it can be installed alongside the MySQL for PCF v1.X tiles to enable easy manual migrations||Upgrading MySQL for PCF|
|Deployment Smoke Tests||MySQL for PCF installation and upgrade runs a post deployment BOSH errand that validates basic MySQL operations|
|Maintenance and Backups||More Information|
|Operational Monitoring and Logging||MySQL for PCF v2 provides metrics for monitoring On-Demand plan usage and quotas, as well as MySQL component metrics. Additionally, MySQL for PCF provides syslog redirection to external log ingestors.||Monitoring MySQL for PCF|
|Backup and Restore||MySQL for PCF v2 includes automatic backups on a configurable schedule to a variety of destinations, as well as a simple restore process.||Manual Backup and Restore of MySQL for PCF|
|Scale and Availability||More Information|
|On-Demand Plan||MySQL for PCF provides up to 50 on-demand instances across all plans|
|Ability to Scale Up / Down||Operators can scale VMs up, but not down||Configuring|
|Rolling Deployments||MySQL for PCF does not support rolling deployments because it is single node; the service is unavailable during upgrades.||Upgrades|
|AZ Support||MySQL for PCF can be deployed to multiple zones to increase availability during unplanned outages of a zone.||About Multiple AZs in MySQL for PCF|
|Transport Layer Security (TLS)||MySQL for PCF 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 PCF has been tested successfully with the BOSH IPsec Add-on||Securing Data in Transit with the IPsec Add-on|
|Encrypted Data at Rest||MySQL for PCF enables integration with commercial vendors for full-disk encryption at rest.||Thales Vormetric plugin|
MySQL for PCF v2 supports configuring multiple AZs. However, assigning multiple AZs to MySQL jobs does not guarantee high availability.
- On-Demand plans can be assigned to any of the configured availability zones.
- You can select two AZs for the multi-node plans to increase the availability. Choosing three AZs for multi-node plans does not increase the number of AZs assigned to three.
- You can select one AZ for the single-node plan. Choosing two AZs for the single-node plan does not increase the number of AZs assigned to two.