x
/
monasca-vagrant
Code Issues Proposed changes

Added Linux install steps, plus other minor tweaks

This commit is contained in:
David Schroeder 2014-06-17 16:39:12 -06:00
parent 90b825d33d
commit 1514002759
1 changed files with 56 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
README.md
View File

@ -16,7 +16,7 @@
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
Install's a mini monitoring environment based on vagrant. Intended for development and monitoring of the monitoring infrastructure.
Installs a mini monitoring environment based on Vagrant. Intended for development and monitoring of the monitoring infrastructure.
# Installation
@ -26,16 +26,19 @@ Install's a mini monitoring environment based on vagrant. Intended for developme
git clone https://github.com/hpcloud-mon/mon-vagrant
```
Vertica must be downloaded from the [Vertica site](https://my.vertica.com/). Download these packages and place in the root of this repository.
- vertica_7.0.1-0_amd64.deb
- vertica-r-lang_7.0.1-0_amd64.deb
The vertica::console recipe is not enabled by default but if it is added this package is also needed.
- vertica-console_7.0.1-0_amd64.deb
- `vertica_7.0.1-0_amd64.deb`
- `vertica-r-lang_7.0.1-0_amd64.deb`
## Setup Vagrant
The `vertica::console` recipe is not enabled by default, but if it is added, this package is also needed.
### Install Vagrant
Assumes you have home homebrew installed, if not download and install VirtualBox and Vagrant from their websites then continue with Setup Berkshelf.
- `vertica-console_7.0.1-0_amd64.deb`
## Install Vagrant
### Install VirtualBox and Vagrant
#### MacOS
The following steps assume you have [Homebrew](http://brew.sh/) installed. Otherwise, install [VirtualBox](http://www.virtualbox.org) and [Vagrant](http://www.vagrantup.com) manually from their websites, then continue with Set Up Berkshelf below.
```
brew tap phinze/cask
@ -44,58 +47,84 @@ brew cask install virtualbox
brew cask install vagrant
```
### Setup Berkshelf
#### Linux (Ubuntu)
```
# For Ubuntu 12.04, you may need to install ruby 1.9 first
sudo apt-get install ruby1.9.3
sudo update-alternatives --set ruby /usr/bin/ruby1.9.1
sudo apt-get install virtualbox
latest=`curl -s http://www.vagrantup.com/downloads.html |tr " " "\n" |grep 'x86_64.deb' |cut -d'"' -f2`
wget $latest && sudo dpkg -i `basename $latest`
```
### Set Up Berkshelf
#### MacOS
```
vagrant plugin install vagrant-berkshelf --plugin-version '>= 2.0.1'
gem install berkshelf
```
#### Linux (Ubuntu)
```
sudo vagrant plugin install vagrant-berkshelf --plugin-version '>= 2.0.1'
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 vm will have an ip of 196.168.10.4 that can be access from other services running on the host.
- Run `vagrant ssh` to login
- 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 VM will have an IP of 196.168.10.4 that can be access from other services running on the host.
- Run `vagrant ssh` to log in
- Run `vagrant help` for more info
## Updating
When someone updates the config this process should allow you to bring up an updated vm.
When someone updates the config, this process should allow you to bring up an updated VM.
- `git pull`
- `berks update`
- `vagrant destroy` - Where vm is the name of the vm being updated, for example 'vertica'
- `vagrant destroy <vm>` Where `<vm>` is the name of the VM being updated, for example 'vertica'
- `vagrant up`
## Improving Provisioning Speed
The slowest part of the provisioning process is the downloading of deb packages. To speed this up a local apt-cacher-ng can be used.
To install on a mac
### Linux (Ubuntu)
```
sudo apt-get install apt-cacher-ng
```
### MacOS
```
brew install apt-cacher-ng
```
Run `apt-cacher-ng -c /usr/local/etc/apt-cacher-ng/` or optionally follow the instructions from brew to start up the cache automatically.
That is all that is needed from now on the cache will be used.
That is all that is needed. From now on, the cache will be used.
A report from the cache is found at http://localhost:3142/acng-report.html
## Cookbook Development
To develop cookbook changes with Vagrant:
- Edit Berksfile changing the appropriate cookbook line to a local path, ie `cookbook 'zookeeper', path: '/Users/kuhlmant/src/mon/cookbooks/zookeeper'`
- Edit your local cookbook as needed.
- run 'berks update <cookbook_name>'
- If the vagrant vm is already up run 'vagrant provision' if not run 'Vagrant up'
- Edit Berksfile, changing the appropriate cookbook line to a local path. For example:
```
cookbook 'zookeeper', path: '/Users/kuhlmant/src/mon/cookbooks/zookeeper'
```
- Edit your local cookbook as needed
- Run `berks update <cookbook_name>`
- If the Vagrant VM is already up, run `vagrant provision`. Otherwise, run `vagrant up`
- When finish testing commit and upload your cookbook as normal but don't forget to bump the cookbook version in the metadata.rb.
## Running behind a Web Proxy
If you are behind a proxy you can install the `vagrant-proxyconf` pluging to have Vagrant honor standard proxy-related environment variables and set the
vm to use them also.
VM to use them also.
```
vagrant plugin install vagrant-proxyconf
```
# Alternate Vagrant Configurations
To run any of these alternate configs, simply run the Vagrant commands from within the subdir, though note the vertica debs must be copied into
the subdir also. See the README.md in the subdir for more details
To run any of these alternate configs, simply run the Vagrant commands from within the subdir. Note that the Vertica debs must be _copied_ (not symlinked) into
the subdir as well. See the README.md in the subdir for more details.
- HPCloud subdir - Runs a vm in the HP Public Cloud rather than using virtual box
- split subdir - The various monitoring components split into their own vms.
- Baremetal - actually not using Vagrant at all, see the baremetal fabric task in the utils directory.
- `HPCloud` subdir - Runs a VM in the HP Public Cloud rather than using VirtualBox
- `split` subdir - The various monitoring components split into their own VMs
- `Baremetal` - Actually not using Vagrant at all; see the baremetal fabric task in the `utils` directory