Find a file
2018-03-08 10:40:31 -08:00
acl
api fix test 2018-02-15 13:59:03 -08:00
client Fix original client server list behavior 2018-02-15 16:04:53 -08:00
command Merge pull request #3892 from hashicorp/f-tunnel 2018-02-20 16:35:42 -08:00
demo Update client2.hcl 2018-02-15 13:59:03 -08:00
dev
dist
e2e/migrations remove unnecessary test output print 2017-11-01 15:21:05 -05:00
helper Client tls 2018-02-15 15:22:57 -08:00
integrations Fix typos in metric names. #3610 2017-12-01 15:24:14 +01:00
jobspec Fix linting 2018-01-31 09:56:53 -06:00
nomad vet 2018-02-15 17:08:58 -08:00
scheduler Clarify comment 2018-02-05 16:37:07 -06:00
scripts Merge pull request #3819 from schmichael/qemu-graceful-shutdown-alpine 2018-02-12 12:32:14 -08:00
terraform Update AWS scripts and README to reflect latest, pre-built AMI 2018-01-09 22:35:58 +00:00
testutil Skip QEMU graceful shutdown test except on Travis 2018-01-31 15:47:26 -08:00
ui Don't let aborted requests redirect to error 2018-03-08 10:40:31 -08:00
vendor Vendored go-sockaddr and go-sockaddr/template 2018-02-08 09:30:05 -05:00
version bump version and remove generated structs 2017-12-19 17:10:52 -08:00
website Merge pull request #3897 from hashicorp/f-docs-command-with-output 2018-02-26 10:47:22 -08:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore generated files 2017-12-19 16:57:34 -08:00
.travis.yml Add chrome to Travis 2018-01-17 09:04:00 -08:00
appveyor.yml
build_linux_arm.go
CHANGELOG.md changelog 2018-02-20 16:38:59 -08:00
commands.go Add autopilot functionality based on Consul's autopilot 2017-12-18 14:29:41 -08:00
GNUmakefile Disables verbose mode in travis 2018-02-20 18:38:18 -06:00
ISSUE_TEMPLATE.md
LICENSE
main.go
main_test.go
README.md Docs: Add command consul agent & fix nomad command 2018-01-22 13:23:42 +01:00
Vagrantfile Fix whitespace 2017-11-01 11:14:25 -07:00

Nomad Build Status Join the chat at https://gitter.im/hashicorp-nomad/Lobby

Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.

The key features of Nomad are:

  • Docker Support: Jobs can specify tasks which are Docker containers. Nomad will automatically run the containers on clients which have Docker installed, scale up and down based on the number of instances requested, and automatically recover from failures.

  • Multi-Datacenter and Multi-Region Aware: Nomad is designed to be a global-scale scheduler. Multiple datacenters can be managed as part of a larger region, and jobs can be scheduled across datacenters if requested. Multiple regions join together and federate jobs making it easy to run jobs anywhere.

  • Operationally Simple: Nomad runs as a single binary that can be either a client or server, and is completely self contained. Nomad does not require any external services for storage or coordination. This means Nomad combines the features of a resource manager and scheduler in a single system.

  • Distributed and Highly-Available: Nomad servers cluster together and perform leader election and state replication to provide high availability in the face of failure. The Nomad scheduling engine is optimized for optimistic concurrency allowing all servers to make scheduling decisions to maximize throughput.

  • HashiCorp Ecosystem: HashiCorp Ecosystem: Nomad integrates with the entire HashiCorp ecosystem of tools. Like all HashiCorp tools, Nomad follows the UNIX design philosophy of doing something specific and doing it well. Nomad integrates with Terraform, Consul, and Vault for provisioning, service discovery, and secrets management.

For more information, see the introduction section of the Nomad website.

Getting Started & Documentation

All documentation is available on the Nomad website.

Developing Nomad

If you wish to work on Nomad itself or any of its built-in systems, you will first need Go installed on your machine (version 1.9+ is required).

Developing with Vagrant There is an included Vagrantfile that can help bootstrap the process. The created virtual machine is based off of Ubuntu 16, and installs several of the base libraries that can be used by Nomad.

To use this virtual machine, checkout Nomad and run vagrant up from the root of the repository:

$ git clone https://github.com/hashicorp/nomad.git
$ cd nomad
$ vagrant up

The virtual machine will launch, and a provisioning script will install the needed dependencies.

Developing locally For local dev first make sure Go is properly installed, including setting up a GOPATH. After setting up Go, clone this repository into $GOPATH/src/github.com/hashicorp/nomad. Then you can download the required build tools such as vet, cover, godep etc by bootstrapping your environment.

$ make bootstrap
...

Afterwards type make test. This will run the tests. If this exits with exit status 0, then everything is working!

$ make test
...

To compile a development version of Nomad, run make dev. This will put the Nomad binary in the bin and $GOPATH/bin folders:

$ make dev

Optionally run Consul to enable service discovery and health checks:

$ sudo consul agent -dev

And finally start the nomad agent:

$ sudo bin/nomad agent -dev

If the Nomad UI is desired in the development version, run make dev-ui. This will build the UI from source and compile it into the dev binary.

$ make dev-ui
...
$ bin/nomad
...

Note: Building the Nomad UI from source requires Node, Yarn, and Ember CLI. These tools are already in the Vagrant VM. Read the UI README for more info.

To cross-compile Nomad, run make release. This will compile Nomad for multiple platforms and place the resulting binaries into the ./pkg directory:

$ make release
...
$ ls ./pkg
...