Sandy Walsh 72c8f298e4 Ansible scripts now default monitor.*3
In order to run StackTach.v2 and StackTach.v2 in parallel,
we need to have two queue from OpenStack (vs. having to change
--notification_topics to include a new queue).

This approach makes a new queue with the same routing_key off the
same exchange, resulting in mirrored queues which can be consumed
separately.

Exchange "nova" -> (routing key "monitor.info") -> Queue "monitor.info"
                -> (routing key "monitor.info") -> Queue "monitor.info3"

Change-Id: Icce87c7eb43025672759d442553feb325e186128
2015-02-04 15:10:09 -08:00
..
2014-12-22 10:14:37 -08:00
2014-12-22 10:14:37 -08:00

stv3-config

Configuration playbooks for StackTach.v3 deployments

Assumes an inventory value that has nodes or groups that start with "stv3-api" or "stv3-workers".

Execution would look like:

ansible-playbook workers.yaml

Assumes a stv3-db setup already exists.

There are also roles for database and api. The common role is responsible for installing the tarball and creating the necessary user/group accounts. Both the API and workers depend on the common role since they both require the codebase and winchester configuration files.

What it does

  • Creates stv3 user and stv3 group
  • Creates /etc/stv3 directory for configuration data
  • Creates /var/run/stv3 directory for pid files
  • Creates /var/log/stv3 directory for log files
  • Copies config files to /etc/stv3
  • Copies init.d files to /etc/init.d for yagi-events and pipeline-worker
  • Copies and expands the StackTach.v3 tarball to /opt/stv3
  • Starts the yagi worker daemon and the winchester worker (yagi-events and pipeline-worker respectively)

The init.d files handle the .pid file creation and running as stv3 user.

While yagi-events and pipeline-worker are capable to running daemonized, we don't use that code. Instead, we let the init.d scripts handle the backgrounding and process management.

The connection from the host machine to the target machine has to have a secure account already created for anisble to run. Currently it assumes an account called stacktach and it has root capabilities. When the daemons run, they run as stv3 ... which is just a service account.