x
/
monasca-vagrant
Code Issues Proposed changes

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

Change-Id: I918e0026ed96fb3cb1c5582c19744ccf771566ef
This commit is contained in:
Tim Kuhlman 2014-07-16 15:32:24 -06:00
parent 4c4b9d42a8
commit 5520c2e38c
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -29,7 +29,7 @@ Installs a mini monitoring environment based on Vagrant. Intended for developmen
## Get the Code
```
git clone https://github.com/hpcloud-mon/mon-vagrant
git clone https://github.com/stackforge/monasca-vagrant
```
## Install Vagrant
@ -72,7 +72,7 @@ sudo gem install berkshelf
# Using mini-mon
- Your host OS home dir is synced to `/vagrant_home` on the VM.
- The root dir of the mon-vagrant repo on your host OS is synced to `/vagrant` on the VM.
- The root dir of the monasca-vagrant repo on your host OS is synced to `/vagrant` on the VM.
- The main VM will have an IP of 192.168.10.4 that can be access from other services running on the host.
- An additional VM running DevStack will be created at 192.168.10.5
- You can access UI by navigating to http://192.168.10.5 and logging in as mini-mon with password
@ -135,7 +135,7 @@ The `vertica::console` recipe is not enabled by default, but if it is added, thi
- `vertica-console_7.0.1-0_amd64.deb`
After the vertica packages are installed the configuration must be changed to run Vertica. Specifically besides starting Vertica the data bags
for the mon_api and the mon_persister need to be updated so these services use Vertica rather than InfluxDB.
for the monasca_api and the monasca_persister need to be updated so these services use Vertica rather than InfluxDB.
The alternative split setup is configured for running Vertica.

2
split/README.md
View File

@ -5,7 +5,7 @@ monitoring system can scale but also is useful for some development scenarios.
- 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` - mon-notification runs on this box also
- `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`