History

Craig Bryant 55520fe3a6 Change to use the cookbook-monasca-thresh

Requires renaming some databags to monasca_thresh from mon_thresh

This change must be approved AFTER the change to
cookbook-monasca-thresh

Change-Id: I9c65a178409c62d7578e0d9dcbd524b3dffb6f82

2014-08-07 10:53:36 -06:00

bin

Better organization - seperated split setup and hlinux to their own subdirs.

2014-05-15 10:37:38 -06:00

data_bags

Change to use the cookbook-monasca-thresh

2014-08-07 10:53:36 -06:00

roles

Change to use the cookbook-monasca-thresh

2014-08-07 10:53:36 -06:00

README.md

minor name change, other changes will happen as updatedcookbooks are ready.

2014-07-16 15:33:10 -06:00

Vagrantfile

Enable vagrant-cachier and check if vagrant-berkshelf is available

2014-07-30 12:28:00 +02:00

README.md

The chef and Vagrant configuration here runs mini-mon split into 6 different VMs. This split demonstrates and provides a simple test of how the monitoring system can scale but also is useful for some development scenarios.

Using the split mini-mon

Your home dir is synced to /vagrant_home on each vm
Vms created
- api at 192.168.10.4
- kafka at 192.168.10.10 - monasca-notification runs on this box also
- mysql at 192.168.10.6
- persister at 192.168.10.12
- thresh at 192.168.10.14
- vertica at 192.168.10.8
  - The management console is at https://192.168.10.8:5450
- devstack at 192.168.10.5
  - The web interface is at http://192.168.0.5
  - username admin, password admin
Run vagrant help for more info
Run vagrant ssh <vm name> to login to a particular vm
Can also run ssh vagrant@<ip address> to login
- password is vagrant

Start mini-mon

From within this directory, run this simple scripts which aid in bringing up all the vms in the proper order. If desired, the standard vagrant commands can also be used.

bin/vup

Halt mini-mon

In some cases halting mini-mon can result in certain vms being left in an odd state, to avoid this a script has been made to halt boxes in the correct order

bin/vhalt