| commit | 8dede0ce5b3d821ba0310a09e75f0c74bdefc8fc | [log] [tgz] |
|---|---|---|
| author | Carlos Frias <friasc@google.com> | Fri Mar 10 11:51:19 2017 -0500 |
| committer | Carlos Frias <friasc@google.com> | Fri Mar 10 11:51:19 2017 -0500 |
| tree | 7fad5cb1afd2b6583b705fd810c3d7218a6605a0 | |
| parent | 8bd978bdc96dab0cb4e81e9b19cff2b748df75bc [diff] |
updated docs
This is an Ansible playbook that performs a modification of the Cassandra replication factor used with Apigee components with zero downtime in a two data center topology.
This playbook uses ansible-galaxy to download roles that are used by this playbook. Once roles are downloaded the playbook and be invoked in several ways. The playbook can be invoked in its entirety, a tag can be used to invoke a subset of playbook services or the playbook may be run manually. These ways of invoking the playbook are described below.
The playbook roles and their location is found in the requirements.yml file. This file is provided to ansible-galaxy so that the roles may be downloaded.
Ansible galaxy will download the required roles when invoked with the install action and the requirements file. This is accomplished in the following way:
ansible-galaxy install -r requirements.yml
The update-replication-factor.yml script performs the update of the Cassandra replication factor for keyspaces in a Cassandra ring. This playbook assumes that you are changing Cassandra replication on a planet that is composed of two regions or two data centers.
This script expects you to provide the replication_factor setting you wish to use when the script is invoked at the command line.
The full playbook invocation is performed in the following way:
ansible-playbook update-replication-factor -e replication_factor=6 -vvv -b
This playbook enables tasks to be invoked manually. Manual invocation of this playbook is accomplished in the following way:
ansible-playbook update-replication-factor -e replication_factor=6 -vvv --step
During manual invocation the playbook will stop before every task. The user is prompted on each task
for permission to execute, stop execution or continue execution to the first task of the next play. The prompt accepts y to execute; n to stop execution or c to continue execution and stop on the first task of the next play.
This playbook contains a convenience playbook that uses the replication_factor_update.yml and requires that you specify only the replication_factor.
ansible-playbook update.yml -vv -b -e replication_factor=3
| Playbook Name | Tag Name | Description |
|---|---|---|
| update.yml | dc-1 | All tasks on dc-1 only |
| update.yml | dc-2 | All tasks on dc-2 only |
| update.yml | restart | Restart apigee components other than ds profile components |
| replication_factor_update.yml | cache | Update ansible cache, includes apigee specific attributes |
| replication_factor_update.yml | update | Update replication factor |
| replication_factor_update.yml | repair | Perform nodetool repair |
| replication_factor_update.yml | restart | Restart all apigee components on the node |
| replication_factor_update.yml | stop | Stop all apigee components on the node |
| replication_factor_update.yml | start | Start all apigee components on the node |