DevStack-like environment for StackTach.v3
Go to file
OpenDev Sysadmins c0a16e5d7e OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:50:22 +00:00
ansible Status utility now support different vhosts per cell. 2015-04-16 12:04:47 -07:00
bin Status utility now support different vhosts per cell. 2015-04-16 12:04:47 -07:00
docs Fix up build script for stackforge repo rename. 2015-10-29 18:45:11 +00:00
etc Status utility now support different vhosts per cell. 2015-04-16 12:04:47 -07:00
vagrant Fix up build script for stackforge repo rename. 2015-10-29 18:45:11 +00:00
winchester UsageHandler and NotabeneHandler docs. 2015-03-20 09:15:47 -07:00
.gitignore Initial commit 2014-05-26 23:10:55 -03:00
.gitreview OpenDev Migration Patch 2019-04-19 19:50:22 +00:00
LICENSE Initial commit 2014-05-26 23:10:55 -03:00
README.md Fix up build script for stackforge repo rename. 2015-10-29 18:45:11 +00:00
build.sh Fix up build script for stackforge repo rename. 2015-10-29 18:45:11 +00:00
distiller.conf distiller support for metadata extraction 2014-05-29 20:15:04 +00:00
flush.sh lots of experiments 2014-08-19 13:40:06 +00:00
logging.conf Start on STv3 docs 2015-02-19 10:24:47 -08:00
pip_freeze_versions.txt Fix up build script for stackforge repo rename. 2015-10-29 18:45:11 +00:00
quincy.conf Enable quincy API w/ winchester pipeline engine 2014-12-03 19:58:12 +00:00
reset.sh Preliminary time-sync and usage support 2014-10-16 13:08:42 -07:00
reset.sql Preliminary time-sync and usage support 2014-10-16 13:08:42 -07:00
screenrc.winchester Fix klugman call in screen script for new cmdline ordering. 2015-04-27 11:55:41 -07:00
winchester.yaml Fix up defaults to use notabene handler and usage 2015-02-10 12:57:28 -08:00
yagi.conf.common Supports the new tarball style of WritingJSONRollManager. 2015-02-24 11:29:25 -08:00
yagi.conf.winchester Updates yagi.conf to write json files of every event. 2015-02-17 15:00:45 -08:00

README.md

sandbox

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

Note: read the Operators Guide etherpad for deployment notes.

Prerequisites:

make sure you have a working python dev environment (2.7+ ideally)
    including virtualenv.
Install rabbitmq and mysql-server.

TL;DR:

handle the prerequisites above.
git clone https://github.com/openstack/stacktach-sandbox
cd sandbox
create a mysql database to use
set the database url appropriately in winchester.yaml
./build.sh

Using Vagrant for fast local provisioning:

* Install [Vagrant](https://www.vagrantup.com/downloads.html)
* Install [VirtualBox](https://www.virtualbox.org/wiki/Downloads)
* git clone https://github.com/StackTach/sandbox.git
* cd sandbox/vagrant
* vagrant up
* vagrant ssh
* cd stacktach-sandbox
* ./build.sh

Tweaks:

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.oahu or screenrc.winchester 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 yagi.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 yagi.conf.

The sandbox environment configures shoebox to archive notifications to local .json files and tarball them up after the directory reaches 20GB.

To have shoebox upload to Swift, you are required to 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.