Aerospike EE OnDemand Service for PCF

This documentation describes Aerospike EE OnDemand Service for Pivotal Cloud Foundry (PCF). Aerospike EE OnDemand Service for PCF allows you to configure and deploy multiple Aerospike Enterprise Edition NoSQL database clusters to your PCF deployment.

These clusters can be configured and scaled independently as required by your application. The tile allows you to configure the default settings for small, medium, and large cluster plans. Developers can create instances of these service plans using the Cloud Foundry Command Line Interface (cf CLI) and bind them to applications to access the Aerospike database managed by this service.

Once created, Aerospike clusters can be modified using the cf CLI. This allows dynamic scaling of the services as required.

Overview

Aerospike EE OnDemand Service for PCF includes the following key features:

  • Create and destroy Aerospike database cluster services as required using the cf CLI
  • Dynamically scale individual Aerospike database cluster services
  • Monitor and manage Aerospike database cluster service using the Aerospike Management Console

Product Snapshot

Aerospike EE OnDemand Service for PCF Details:
Version: v1.0.0
Release date: March 3, 2017
Software component version: Aerospike Server Enterprise Edition v3.11.0.1
Compatible Ops Manager version(s): v1.8.x, v1.9.x
Compatible Elastic Runtime version(s): v1.8.x, v1.9.x
vSphere support? Yes
OpenStack support? No
AWS support? No

Requirements

Aerospike EE OnDemand Service for PCF requires a valid Enterprise Edition license for the Aerospike database.

Limitations

The current version has only been tested in the vSphere environment.

Feedback

Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list or send an email to pcf-support@aerospike.com.

License

To obtain a license for the Enterprise Edition of the server, use this form to contact the Aerospike sales team.

Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub