{"_id":"54fa0051f63cf9210041c3c4","__v":14,"body":"Welcome to Paz. By the end of this tutorial you will be running your own installation.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Don't forget\",\n  \"body\": \"Install [Paz Dependencies](http://paz.readme.io/v1.0/docs/installation) before continuing\"\n}\n[/block]\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/bu9DRtR6awgYrQAzcxgr_screenshot:::at:::2x.png\",\n        \"screenshot@2x.png\",\n        \"2106\",\n        \"1388\",\n        \"#fc5c4b\",\n        \"\"\n      ],\n      \"caption\": \"Paz Dashboard\"\n    }\n  ]\n}\n[/block]\nBefore you start with this guide please make sure you install [Vagrant](https://www.vagrantup.com/) and VirtualBox (https://www.virtualbox.org/wiki/Downloads).\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Installing Paz on Vagrant\"\n}\n[/block]\nClone [Paz](http://paz.sh) and install it in Vagrant\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"git clone https://github.com/paz-sh/paz.git\\ncd paz\\n./scripts/install-vagrant.sh\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\n This will bring up a three-node CoreOS Vagrant cluster and install Paz on it. \n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Notice\",\n  \"body\": \"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=1` environment variable.\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"warning\",\n  \"title\": \"Remember!\",\n  \"body\": \"You will need to edit your `/etc/hosts` file, and the instructions for doing so are printed at the end of the console output of the installation script.\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Re-installing/Updating your Vagrant Installation\"\n}\n[/block]\nIf you already have a Vagrant cluster running and want to reinstall the units, use:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"./script/reinstall-units-vagrant.sh\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\nNote that this will first remove existing running units, i.e. it will uninstall Paz, keeping your CoreOS cluster, then reinstall Paz.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Interacting Directly with the Cluster Using Fleet\"\n}\n[/block]\nTo interact with the units in the cluster via [Fleet](https://coreos.com/using-coreos/clustering/), just specify the URL to [Etcd](https://coreos.com/using-coreos/etcd/) on one of your hosts as a parameter to Fleet. e.g.:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"fleetctl -strict-host-key-checking=false -endpoint=http://172.17.9.101:4001 list-units\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\nYou can also SSH into one of the VMs and run fleetctl from there:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"cd coreos-vagrant\\nvagrant ssh core-01\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Notice\",\n  \"body\": \"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.\"\n}\n[/block]","hidden":false,"link_url":"","project":"54fa004ff63cf9210041c3be","api":{"settings":"","url":"","auth":"required","params":[],"results":{"codes":[]}},"excerpt":"This page will explain how you can get started with Paz using Vagrant","githubsync":"","link_external":false,"title":"Installing Paz Using Vagrant","category":"54fa42b3961fea210092068e","createdAt":"2015-03-06T19:30:25.542Z","sync_unique":"","type":"basic","updates":["54fb3d663dc1790d00b5420a"],"user":"54fa0018e7a0ba2f00306211","order":0,"slug":"installing-paz-using-vagrant","version":"54fa0050f63cf9210041c3c1","childrenPages":[]}

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. [block:callout] { "type": "info", "title": "Don't forget", "body": "Install [Paz Dependencies](http://paz.readme.io/v1.0/docs/installation) before continuing" } [/block] [block:image] { "images": [ { "image": [ "https://files.readme.io/bu9DRtR6awgYrQAzcxgr_screenshot@2x.png", "screenshot@2x.png", "2106", "1388", "#fc5c4b", "" ], "caption": "Paz Dashboard" } ] } [/block] Before you start with this guide please make sure you install [Vagrant](https://www.vagrantup.com/) and VirtualBox (https://www.virtualbox.org/wiki/Downloads). [block:api-header] { "type": "basic", "title": "Installing Paz on Vagrant" } [/block] Clone [Paz](http://paz.sh) and install it in Vagrant [block:code] { "codes": [ { "code": "git clone https://github.com/paz-sh/paz.git\ncd paz\n./scripts/install-vagrant.sh", "language": "shell" } ] } [/block] This will bring up a three-node CoreOS Vagrant cluster and install Paz on it. [block:callout] { "type": "warning", "title": "Notice", "body": "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=1` environment variable." } [/block] [block:callout] { "type": "warning", "title": "Remember!", "body": "You will need to edit your `/etc/hosts` file, and the instructions for doing so are printed at the end of the console output of the installation script." } [/block] [block:api-header] { "type": "basic", "title": "Re-installing/Updating your Vagrant Installation" } [/block] If you already have a Vagrant cluster running and want to reinstall the units, use: [block:code] { "codes": [ { "code": "./script/reinstall-units-vagrant.sh", "language": "shell" } ] } [/block] Note that this will first remove existing running units, i.e. it will uninstall Paz, keeping your CoreOS cluster, then reinstall Paz. [block:api-header] { "type": "basic", "title": "Interacting Directly with the Cluster Using Fleet" } [/block] To interact with the units in the cluster via [Fleet](https://coreos.com/using-coreos/clustering/), just specify the URL to [Etcd](https://coreos.com/using-coreos/etcd/) on one of your hosts as a parameter to Fleet. e.g.: [block:code] { "codes": [ { "code": "fleetctl -strict-host-key-checking=false -endpoint=http://172.17.9.101:4001 list-units", "language": "shell" } ] } [/block] You can also SSH into one of the VMs and run fleetctl from there: [block:code] { "codes": [ { "code": "cd coreos-vagrant\nvagrant ssh core-01", "language": "shell" } ] } [/block] [block:callout] { "type": "info", "title": "Notice", "body": "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." } [/block]