+ Contributing to StackTach.v3
+StackTach.v3 is licensed under the Apache 2.0 license
+All the source repos for StackTach.v3 (and .v2) are available on SourceForge. Details on contributing to StackForge projects are available here
+The core developers are available on Freenode IRC in the #stacktach channel
These docs are available in the Sandbox repo. Patches welcome!
+ + + +
diff --git a/docs/install.html b/docs/install.html
new file mode 100644
index 0000000..f6f2bac
--- /dev/null
+++ b/docs/install.html
@@ -0,0 +1,94 @@
+
+
+
+
+
+
+
+
+
+
+
+
+ How StackTach.v3 is deployed at Rackspace
+For Rackspace Public Cloud, OpenStack is deployed in many different regions and each region is comprised of many cells.
+ +
+
+ In this deployment scenario, we have a set of "worker" boxes that run the yagi-event workers (to consume notifications from RabbitMQ). We run one yagi-event worker per OpenStack cell. We also run the Winchester pipeline-workers on this box. The pipeline-worker manages pipeline processing for ready streams. We run as many pipeline-workers as needed to keep each core busy. Both the yagi-event and pipeline-worker processes are single threaded so we spawn more to keep the host busy. We add more servers like these to handle the load in the pipeline processing and/or the source queues.
Additionally, we have servers for the API nodes and the MySQL database. Load balancing the API servers and making MySQL highly available is left to the deployer.
+The Ansible deployment scripts
+In the StackTach Sandbox repo, there is an ansible directory that contains roles for the workers, the API nodes and the database. There is a fourth "common" role that is used by the other roles.
+These scripts assume a multi-cell deployment where there is one StackTach.v3 deployment per region (each with it's own API servers and database). If you are not running with cells, pretend it's a single cell.
+The Build script
+The StackTach Sandbox repo is the umbrella repo for all the other StackTach modules. It:
+-
+
- can create a local dev environment for anyone wanting to contribute to StackTach or just play around with it +
- can package StackTach into a python virtual environment and tarball it up for larger scale deployment. The ansible scripts use this tarball approach. +
- git clones all the dependent python modules so you can develop locally and see your changes immediately and easily. +
The sandbox readme will get you started, but the gory details are in the build.sh script. There are essentially three options:
-
+
./build.sh- run the local StackTach.v3 dev environment in a screen session. +./build.sh -t- run the tests on all the StackTach.v3 repos. +./build.sh -p- install StackTach.v3 into the virtual env and package it up into a tarball for deployment. +./build.sh -p -d- package and deploy the tarball. Currently this just lists the ansible incantation required to do the deployment. +
The screencasts cover using the sandbox for local dev in more detail.
+ + +
+ The History of StackTach
+StackTach started as a tool for debugging OpenStack Nova deployments. Before we started on StackTach.v3 (a complete rewrite), we had plans to integrate with Ceilometer. This presentation from the Hong Kong summit gives a good overview of how StackTach has evolved over the years. It also gives great detail on the usage verification process as well as some of the key architectural concepts behind version 3.
+ + + +The StackTach.v3 Components
+An early screencast of the components of StackTach.v3 ... some things have changed since. Oahu has now been replaced with Winchester and all the repos have been moved to StackForge.
+ + + +The StackTach.v3 Sandbox
+An early screencast of the StackTach.v3 Sandbox. Shows how to launch the sandbox for local dev and how to navigate the various components. This video was done before packaging was added and before Winchester support was added. The Oahu config file is no longer required as we now use Winchester.
+ + + +The Notigen Event Simulator
+In order to play with StackTach.v3 you need a good source of notifications. To make this easier we don't want to require you stand up a full OpenStack environment. Instead, we use Notigen to simulate Nova-like notifications and publish these to RabbitMQ. This video explains how this works.
+ + + +The REST API - Quincy and Quince
+How we separate the REST API from the implementation within StackTach.v3. If you decide you want to implement your own steam engine, but stay compatible with the StackTach.v3 API, these libraries make it easy to do so.
+ + +Klugman - client library/cmdline tool
+An early video of the Klugman cmdline tool and client library. A newer video is required to reflect the most recent changes, but this will get you started.
+ + + +
Monasca and StackTach.v3 Integration +
Our joint-presentation with the Monasca team at the Paris OpenStack summit.
+ + + + + +