x/stacktach-sandbox
Code Issues Proposed changes
DevStack-like environment for StackTach.v3
14 Commits 1 Branch 3 Tags 645 KiB
Jinja 52.4%
Shell 29.7%
Python 16.5%
Ruby 1.2%
SQL 0.2%
27ee997bd0
Go to file
Sandy Walsh 27ee997bd0 Merge pull request #2 from StackTach/quincy 
Quincy/klugman support
2014-06-12 16:09:26 -03:00
.gitignore Initial commit 2014-05-26 23:10:55 -03:00
build.sh start on quincy support 2014-06-06 11:34:06 +00:00
distiller.conf distiller support for metadata extraction 2014-05-29 20:15:04 +00:00
LICENSE Initial commit 2014-05-26 23:10:55 -03:00
README.md Added support for Swift shoebox handler 2014-06-03 03:46:20 +00:00
screenrc basics of quincy/klugman working 2014-06-12 19:07:29 +00:00
shoebox.conf Added support for Swift shoebox handler 2014-06-03 03:46:20 +00:00

README.md

sandbox

Dev env for StackTach development. Uses Notigen event generator and yagi.

You can create a local.sh to override the defaults:

SOURCE_DIR=git  # where the StackTach repos are cloned
VENV_DIR=.venv  # name of the .venv

The build.sh script will create clone each of the StackTach projects into the $SOURCE_DIR directory (so you can work on them in a running env).

The virtualenv will be created and each of the projects (and their dependencies) installed into it.

A screen session is started, based on screenrc which will start the notigen event generator. The event generator simulated OpenStack notifications and pumps them into rabbitmq. yagi-event is also started with the shoebox.conf configuration file. This will read events from the rabbit queue and save them to local files. The working directory and archive directory for shoebox is specified in shoebox.conf.

The sandbox environment configures shoebox to upload archive files to Swift automatically. This requires you create a credentials file in the .../sandbox/ directory (like in .../git/sandbox/etc/sample_rax_credentials.conf) Call it swift_credentials.conf or alter the shoebox.conf file accordingly. If you don't have access to a Swift server, like CloudFiles, read the config file for details on disabling this feature.