Provides virtual machines targets for a Boundary Demo
- Git 1.7 or later, here
- Vagrant 1.7.2 or later. Vagrant can be downloaded here
- VirtualBox 4.3.2.6 or later. VirtualBox can be downloaded here
The Boundary meter is installed on each of the virtual machines via the Boundary Puppet Module. Boundary Meter installation requires that the api token be known at install time. The Boundary API Token can be found in the Settings -> Account dialog in the Boundary user interface.
The table below provides the mapping of platform to virtual machine name that is used later to start a virtual machine for testing plugins.
Role | Virtual Machine Name | Notes |
---|---|---|
Web Server #1 | web-01 |
|
Web Server #2 | web-02 |
|
Web Server #3 | web-03 |
|
Database Server #1 | db-01 |
|
Database Server #2 | db-02 |
|
Monitor Server #1 | monitor-01 |
With the Boundary API token perform the following:
- Either checkout or clone the git repository ()[]
- Issue the following command, the target platforms are listed in the table below:
$ BOUNDARY_API_TOKEN=<api token> vagrant up <virtual machine name>
$ vagrant halt <virtual machine name>
$ vagrant destroy <virtual machine name>
- Start virtual machines
$ BOUNDARY_API_TOKEN=<api token> vagrant up web-01 --provider virtualbox
- Deploy Apache plugin on each of the web servers
$ BOUNDARY_API_TOKEN=<api token> vagrant up db-01 db-02 --provider virtualbox
- Deploy MySQL plugin on each of the database servers
- Start virtual machine
$ BOUNDARY_API_TOKEN=<api token> vagrant up monitor-01 --provider virtualbox
- Deploy httpcheck plugin
- Configure check of web-01
- Configure check of web-02
- Configure check of web-03