rlec #2

  • By redislabs
  • Latest version (#2)
  • trusty
  • Stable

Description

Redis Labs Enterprise Cluster enables you to install an enterprise-grade cluster that acts as a container for managing and running multiple Redis databases in a highly available and scalable manner, with predictable and stable top performance.


Overview

This charm deploys Redis Labs Enterprise Cluster.

Redis Labs Enterprise Cluster (RLEC) extends open source Redis and delivers operational benefits of high performance and high availability at scale with substantially lower operational costs.

Enterprise Grade Redis Scaling & Clustering:

Scale Redis deployments seamlessly for larger datasets or higher throughput and lower latencies by creating additional database instances (shards), on the same server or across multiple servers dynamically, with no performance impact or downtime. Utilize multiple cores on a single server more efficiently and overcome the limitations of memory on a single server by extending Redis clusters across servers, with the simple click of a button or through API calls.

Always On, Automated High Availability

Ensure high availability with built-in data persistence (AOF or snapshots), rack-aware multi-datacenter/region/cloud database replication and periodic backups to AWS S3, Azure Blob Storage, Google Cloud Storage, OpenStack Swift or an FTP server, all enabled through a simple, intuitive UI. Protect your applications against unplanned downtime, outages and data loss with instant automated failover. Gain the performance benefits of a local copy with continuous database replication across datacenters, regions and clouds.

Dramatically Lower Operational Costs

Lower costs of Redis deployment by running Redis on Flash memory used as RAM extension and ensure consistent high performance with configurable RAM: Flash ratios. Use UI, CLI or Rest API based provisioning, configuration, deployment and continuous monitoring. Run multiple Redis databases and clusters, on a single RLEC deployment, each as its own process and in a non-blocking manner. Track over 20 important Redis metrics with threshold-based alerts and use RLEC’s auto-migration mechanism to isolate high load databases to ensure high performance.

RLEC can be deployed in two configurations:

  • Single node
  • Multiple nodes

When a multiple node cluster is used you can create highly-available databases that consist of master and slave shards located on different nodes.

Usage

Single Node

To deploy this charm, issue the following commands:

juju deploy rlec
juju expose rlec

Multiple Nodes

Once the first node is deployed and active, you can easily add one or more nodes to the cluster by using the following commands:

juju add-unit rlec
juju add-unit rlec -n 3

Removing Nodes from Cluster

Removing a node from the cluster should be done using the remove-unit command. For instance, to remove the node deployed on unit
rlec/1 issue the following command:

juju remove-unit rlec/1

RLEC Management

Once the first node is deployed, you can manage your RLEC via its web interface by pointing your browser to master node
unit's public ip and port 8443 over https. For instance, if your node unit's public ip is 10.0.3.86, point your browser to:

https://10.0.3.86:8443

Configuration

This charm can be configured with the following parameters:

  • username: Admin username. Default: 'demo@redislabs.com'.
  • password: Admin password. Default: '123456'.
  • cluster-name: Fully qualified cluster name, limited to 64 characters and must comply with the IETF’s RFC 952 standard and section 2.1 of the RFC 1123 standard. Default: 'mycluster.local'. You can read more in the documentation.

You can deploy this charm with your own configuration file- for instance, create a my-config.yaml file as follows:

rlec:
  username: "juju@redislabs.com"
  password: "something-secret"
  cluster-name: "juju.cluster"

Then, issue the following command:

juju deploy rlec --config my-config.yaml

Alternatively, you can set the config parameters immediately after the deploy command with:

juju set rlec username=juju@redislabs.com password=something-secret cluster-name=juju.cluster

RLEC Documentation

Support

For support visit: https://redislabs.com/support

Configuration

username
(string) Admin username.
demo@redislabs.com
password
(string) Admin password.
123456
cluster-name
(string) Fully qualified cluster name.
mycluster.local