For local setup, please install Virtualbox and Vagrant on your machine. Follow the installation instructions on their websites.
- Boot the master node
The following command will create a VM with salt installed and activated:
$ vagrant up monitor
- Create BCCVL certificates
$ vagrant ssh monitor $ pushd /srv/CA $ ./createcerts.sh $ popd
This copies also all generated certs and keys into pillar/base/certs from where they can be used in normal pillar files
- Provision the monitor node
Create an empty users.sls:
$ touch /srv/pillar/base/users.sls
Copy /srv/pillar/base/variables.yml to /srv/pillar/dev/variables.yml and change the authtkt and requests sections to:
authtkt:
name: __ac
domain: {{ bccvl.hostname }}
secret: secret
secure: True
requests:
ssl:
verify: false
Because the master "salts" itself, we have to run highstate on the master first:
$ vagrant ssh monitor $ sudo salt-call state.highstate
This should trigger a restart of the salt master daemon, which causes the minion to loose it's connection. If that's the case we'll have to re-run the highstate:
$ sudo salt-call state.highstate $ exit
First, create the SSH keys for the various components:
$ pushd salt/roots/pillar/dev/keys $ ./createkeys.sh $ popd
Then, bring up the BCCVL node. This works very similar to building the master node:
$ vagrant up bccvl $ vagrant ssh bccvl $ sudo salt-call state.highstate $ exit
Run the script downloadrlibs.sh to fetch all required R libraries. This step is necessary until a bug in salt file.managed with multiple alternative source locations is fixed:
$ ./downloadrlibs.sh
Go to http://www.cs.princeton.edu/~schapire/maxent/ and download a copy of maxent.jar v3.3.3k and place it in salt/roots/salt/prod/worker
The last steps are the same steps as above:
$ vagrant up worker $ vagrant ssh worker $ sudo salt-call state.highstate $ exit
URL | Description |
---|---|
https://192.168.100.100/loganalyzer/ | Loganalyzer |
https://192.168.100.100/flower/ | Flower |
https://192.168.100.100/kibana/ | Elasticsearch |
URL | Description |
---|---|
https://192.168.100.200/ http://192.168.100.200/ | BCCVL |
https://192.168.100.200/_debug/ http://192.168.100.200/_debug/ | BCCVL debug |
https://192.168.100.200:15671 | Rabbitmq |
https://192.168.100.200/_visualiser/ http://192.168.100.200/_visualiser/ | Visualiser |
https://192.168.100.200/_datamover/ http://192.168.100.200/_datamover/ | Datamover |
Nothing exposed here
- When updating the master config via salt, the master will be restarted and the minion looses the connection with the master and fails to finish executing the remainder of the state tree
- document folder structure ... esp. pillar/base/keys and certs
- document how and what to override for different environments