Installing Paz Using Vagrant
This page will explain how you can get started with Paz using Vagrant
Welcome to Paz. By the end of this tutorial you will be running your own installation.
Don't forget
Install Paz Dependencies before continuing
Paz Dashboard
Before you start with this guide please make sure you install Vagrant and VirtualBox (https://www.virtualbox.org/wiki/Downloads).
Installing Paz on Vagrant
Clone Paz and install it in Vagrant
git clone https://github.com/paz-sh/paz.git
cd paz
./scripts/install-vagrant.sh
This will bring up a three-node CoreOS Vagrant cluster and install Paz on it.
Notice
Please be aware that the process of starting the cluster can take 10 or more minutes to complete. If you are looking for ways to get a more verbose output you can set the
DEBUG=1environment variable.
Remember!
You will need to edit your
/etc/hostsfile, and the instructions for doing so are printed at the end of the console output of the installation script.
Re-installing/Updating your Vagrant Installation
If you already have a Vagrant cluster running and want to reinstall the units, use:
./script/reinstall-units-vagrant.sh
Note that this will first remove existing running units, i.e. it will uninstall Paz, keeping your CoreOS cluster, then reinstall Paz.
Interacting Directly with the Cluster Using Fleet
To interact with the units in the cluster via Fleet, just specify the URL to Etcd on one of your hosts as a parameter to Fleet. e.g.:
fleetctl -strict-host-key-checking=false -endpoint=http://172.17.9.101:4001 list-units
You can also SSH into one of the VMs and run fleetctl from there:
cd coreos-vagrant
vagrant ssh core-01
Notice
Fleet needs to SSH into the other VMs in order to perform operations that involve calling down to systemd (e.g. journal), and for this you need to have SSHd into the VM running the unit in question. For this reason you may find it simpler (albeit more verbose) to run fleetctl from outside the CoreOS VMs.
Updated less than a minute ago