Aerospike Service Broker for PCF
This documentation describes the Aerospike Service Broker for Pivotal Cloud Foundry (PCF). The Aerospike Service Broker registers a service broker on PCF and exposes its service plans on the Marketplace. Developers can create instances of these service plans using Apps Manager or the Cloud Foundry Command Line Interface (cf CLI), and bind them to applications to access an existing Aerospike database.
Aerospike is a high-performance, distributed, scalable NoSQL database and key/value store.
The Aerospike Service Broker for PCF integrates your Aerospike database with your PCF deployment, by automatically discovering the namespaces that have been created on the database and exposing them as service plans in the Marketplace. Developers can create instances of these service plans and bind them to applications to provide connection information to the applications.
The Aerospike Service Broker for PCF has the following features:
- Key-value store
- Flexible data model
- User-defined functions
- Geospatial support
- Geographic replication
For more information about Aerospike, see the Aerospike documentation.
The following table provides version and version-support information about Aerospike Service Broker for PCF.
|Release date||February 15, 2019|
|Software component version||Aerospike Server (Community or Enterprise) 3.9.1 or later|
|Compatible Ops Manager version(s)||2.1, 2.2, 2.3, and 2.4|
|Compatible Pivotal Application Service version(s)||2.1, 2.2, 2.3, and 2.4|
|BOSH stemcell version||Ubuntu Xenial|
|IaaS support||AWS, OpenStack, vSphere, and GCP|
WARNING: Aerospike Service Broker for PCF v1.0.2 and earlier require a Ubuntu Trusty stemcell. The end-of-life date for Ubuntu Trusty is April 2019. If a security vulnerability is found on this stemcell after April, it will not be fixed.
Aerospike Service Broker for PCF has the following requirements:
- You must have an Aerospike database server deployed.
- Your Aerospike database must have a namespace configured to store service and application binding information for the Aerospike Service Broker.
- If you have deployed the Enterprise Edition of the Aerospike database server, you must also configure a user with read-write permissions to the designated namespace. This user must also have user-admin permissions because the Aerospike Service Broker will create and delete users during the application binding and unbinding operations.
For more information about how to deploy an Aerospike database, see the Aerospike documentation.
Customers interested in deploying the Aerospike database server can download and install it from the download page. To obtain a license for the Enterprise Edition of the server, use this form to contact the Aerospike sales team.