Although a9s MySQL has been renamed to a9s MariaDB, it should be noted that every a9s MariaDB version
>=10.6 is to be
considered part of a new data service.
Be aware that from the a9s MariaDB
10.6 version there were also some changes in the name of some properties, the data
service names, domain names, metric names, etc.
Most of these changes between the version are related to the name
- a9s MariaDB versions
< 10.6will keep using
mysqlin most cases.
- a9s MariaDB versions
>= 10.6will use
mariadbin most cases.
This documentation describes the a9s MariaDB. a9s MariaDB enables on-demand provisioning of VM-based dedicated MariaDB
servers. Developers can create instances of a MariaDB server using Apps Manager or the Cloud Foundry Command Line
cf CLI) and bind these instances to an app.
Depending on the chosen service plan, a service instance may be associated with a single, dedicated virtual machine, or a set of VMs consisting of multiple virtual machines comprising a cluster of MariaDB servers.
When you run the cf CLI
cf create-service a9s-mariadb106 command, the a9s MariaDB data service creates dedicated VMs
for this service instance. This allows the best possible bad neighborhood protection.
MariaDB service instance provisioning, including VM orchestration, is entirely automated. This enables service instances to be highly isolated and shielded by infrastructure virtualization mechanisms.
Due to the on-demand provisioning on VMs, only existing service instances allocate infrastructure resources. These resources are released when service instances are destroyed. Using on-demand provisioning the number of service instances is not limited by design.
The current version of a9s MariaDB includes the following key features:
|On-Demand Service Instance Provisioning
|a9s MariaDB deploys MariaDB instances automatically. Developers can provision a single-VM MariaDB server using a single command.
|Service Instance Isolation
|Each MariaDB server runs on a dedicated VM to ensure bad neighborhood protection in order to be aligned with enterprise security requirements.
a9s MariaDB uses Cloud Foundry security groups to prevent network connections being established by unauthorized apps.
|a9s MariaDB contains a post-deploy smoke tests errand that runs a series of basic tests against your installation to ensure that it is configured properly.
|Service Instance Capacity Upgrade
|Cloud Foundry Service Plan updates allow upgrades to the RAM, CPU, and storage capacity for your MariaDB instances.
|Logging and Monitoring
|Each MariaDB service instance provides log messages and MariaDB-specific metrics to one or more
syslog/graphite endpoints. You can configure the
syslog/graphite endpoint to receive logging and monitoring information.
|This errand automatically updates the stemcell and all provisioned a9s MariaDB service instances to their lastest version.
|CF Service Guard
|The CF Service Guard creates Cloud Foundry App Security Groups for your service instance VMs.
When the IP address of a service instance changes, the CF Service Guard updates the ASG.
|a9s MariaDB ensures high availability.
The Consul-based internal DNS system provided by a9s Consul DNS ensures that the connected application always connects to a working node.