luxolus/open-nomad
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

Vagrant optional (#5724)

Browse source 
* specify Vagrant as optional in getting started and installation

* edit next steps
This commit is contained in:
Omar Khawaja 2019-05-17 16:50:16 -04:00 committed by GitHub
parent 0256cf700d
commit 8039426701
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 29 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
website/source/guides/install/quickstart/index.html.md
View file

@ -3,18 +3,23 @@ layout: "guides"
page_title: "Installing Nomad for QuickStart" page_title: "Installing Nomad for QuickStart"
sidebar_current: "guides-install-quickstart" sidebar_current: "guides-install-quickstart"
description: |- description: |-
Learn how to install Nomad for sandbox. Learn how to install Nomad locally or in a sandbox.
--- ---
#Quickstart #Quickstart
This page lists multiple methods to installing Nomad in a sandbox environment. This page lists multiple methods to installing Nomad locally or in a sandbox
environment.
These installations are designed to get you started with Nomad easily and should be used only for experimentation purposes. If you are looking to install Nomad in production, please refer to our [Production Installation](/guides/install/production/index.html) guide here. These installations are designed to get you started with Nomad easily and should
be used only for experimentation purposes. If you are looking to install Nomad
in production, please refer to our [Production
Installation](/guides/install/production/index.html) guide here.
##Local ##Local
Install Nomad on your local machine. Install Nomad on your local machine.
* [Vagrant](/intro/getting-started/install.html) * [Installing the Pre-compiled Binary][installing-binary]
* [Installing Nomad with Vagrant][vagrant-environment]
##Cloud ##Cloud
Install Nomad on the public cloud. Install Nomad on the public cloud.
@ -30,3 +35,6 @@ Experiment with Nomad in your browser via KataCoda's interactive learning platfo
* [Introduction to Nomad](https://www.katacoda.com/hashicorp/scenarios/nomad-introduction) * [Introduction to Nomad](https://www.katacoda.com/hashicorp/scenarios/nomad-introduction)
* [Nomad Playground](https://katacoda.com/hashicorp/scenarios/playground) * [Nomad Playground](https://katacoda.com/hashicorp/scenarios/playground)
[installing-binary]: /guides/install/index.html#precompiled-binaries
[vagrant-environment]: /intro/getting-started/install.html#vagrant-setup-optional-

25
website/source/intro/getting-started/install.html.md
View file

@ -8,16 +8,21 @@ description: |-
# Install Nomad # Install Nomad
To simplify the getting started experience, we will be working in a Vagrant To simplify the getting started experience, you can download the pre-compiled
environment. Create a new directory, and download [this binary and run it directly (see the instructions [here][binary-instructions]) or
you can optionally work in a Vagrant environment (detailed in the following
section).
## Vagrant Setup (Optional)
Note: To use the Vagrant Setup first install Vagrant following these
[instructions][install-instructions].
Create a new directory, and download [this
`Vagrantfile`](https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile). `Vagrantfile`](https://raw.githubusercontent.com/hashicorp/nomad/master/demo/vagrant/Vagrantfile).
## Vagrant Setup Once you have created a new directory and downloaded the `Vagrantfile` you must
create the virtual machine:
Note: To use the Vagrant Setup first install Vagrant following these instructions: https://www.vagrantup.com/docs/installation/
Once you have created a new directory and downloaded the `Vagrantfile`
you must create the virtual machine:
```shell ```shell
$ vagrant up $ vagrant up
@ -80,6 +85,8 @@ re-create it.
## Next Steps ## Next Steps
Vagrant is running and Nomad is installed. Let's [start Nomad](/intro/getting-started/running.html)! Nomad is installed. Let's [start Nomad](/intro/getting-started/running.html)!
[binary-instructions]: /guides/install/index.html#precompiled-binaries
[destroy]: https://www.vagrantup.com/docs/cli/destroy.html [destroy]: https://www.vagrantup.com/docs/cli/destroy.html
[install-instructions]: https://www.vagrantup.com/docs/installation/

5
website/source/intro/getting-started/running.html.md
View file

@ -27,7 +27,7 @@ job configurations or prototype interactions. It should _**not**_ be used in
production as it does not persist state. production as it does not persist state.
```text ```text
vagrant@nomad:~$ sudo nomad agent -dev $ sudo nomad agent -dev
==> Starting Nomad agent... ==> Starting Nomad agent...
==> Nomad agent configuration: ==> Nomad agent configuration:
@ -78,9 +78,6 @@ If you run [`nomad node status`](/docs/commands/node/status.html) in another
terminal, you can see the registered nodes of the Nomad cluster: terminal, you can see the registered nodes of the Nomad cluster:
```text ```text
$ vagrant ssh
...
$ nomad node status $ nomad node status
ID DC Name Class Drain Eligibility Status ID DC Name Class Drain Eligibility Status
171a583b dc1 nomad <none> false eligible ready 171a583b dc1 nomad <none> false eligible ready