This documentation describes the a9s Redis. a9s Redis enables on-demand provisioning of VM-based, dedicated Redis servers. Developers can create instances of a Redis server using Apps Manager or the Cloud Foundry Command Line interface (cf CLI) and bind these instances to an app.
When you run the cf CLI
create-service redis command, BOSH creates dedicated VMs for this service instance. This allows the best possible bad neighborhood protection.
Redis 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 Redis includes the following key features:
|On-Demand Service Instance Provisioning||a9s Redis deploys Redis instances automatically. Developers can provision a single-VM Redis server using a single command.|
|Service Instance Isolation||Each Redis server runs on a dedicated VM to ensure bad neighborhood protection in order to be aligned with enterprise security requirements. |
a9s Redis uses Cloud Foundry security groups to prevent network connections being established by unauthorized apps.
|Smoke Tests||a9s Redis contains a post-deploy smoke tests errand that runs a series of basic test 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 Redis instances.|
|Logging and Monitoring||Each Redis service instance provides log messages and Redis-specific metrics to one or more |
|Deployment Updater||This errand automatically updates the stemcell and all provisioned a9s Redis service instances to their lastest version.|
|Backup Manager||The Backup Manager does regular backup of your instances and offers endpoints to backup instantly and restore backups.|
|Service Guard||The Service Guard creates Cloud Foundry security groups for your service instance VMs. |
When the IP address of a service instance changes, the guard updates the security group. The Service Guard also restarts the application instances bound to the affected service instance. The instances of one application are restarted one by one to avoid downtime.
|Customazible Snapshots||a9s Redis supports RDB persistence with point-in-time snapshots. |
This setting can be changed by the user.
|High Availability||a9s Redis ensures high-availability using Redis Sentinel. |
The Consul-based internal DNS system ensures that the connected application always connects to a working node. The user can modify Sentinel related settings like
|Improved Memory Handling||a9s Redis now supports a better memory handling. In addition, the user can modify the |
Specification of a9s Redis service plans:
|High Availability |
(number of nodes)
|Number of vCPUs||2||2||2||2||2||2|
|RAM||0.5 GB||2 GB||4 GB||2 GB||4 GB||4 GB|
|Disk *||3 GB||10 GB||50 GB||10 GB||50 GB||150 GB|
For example, one backing service instance of size m is high available (consists of 3 nodes), has 2 vCPUs, 4 GB RAM, 50 GB disk, up to 10000 connections and logging component.
* Total virtual disk size. You cannot use the whole disk for your data. For more information, refer Disk Alerts.
Any questions left?
Except where otherwise noted, content on this site is licensed under the MindSphere Development License Agreement.