Go to file
Chelsea Holland Komlo 649f86f094 refactor creating a new tls configuration 2018-01-16 08:02:39 -05:00
acl fixup from code review 2017-10-17 17:34:06 -04:00
api Merge branch 'master' into 0.8 2018-01-03 16:06:38 -06:00
client refactor creating a new tls configuration 2018-01-16 08:02:39 -05:00
command adding additional test assertions; differentiate reloading agent and http server 2018-01-16 07:34:39 -05:00
demo Update site for 0.7.0 2017-11-01 11:25:34 -07:00
dev guide 2017-10-31 13:14:16 -07:00
dist Lots of fixes from @sethvargo 2017-08-01 15:40:36 -07:00
e2e/migrations remove unnecessary test output print 2017-11-01 15:21:05 -05:00
helper refactor creating a new tls configuration 2018-01-16 08:02:39 -05:00
integrations Fix typos in metric names. #3610 2017-12-01 15:24:14 +01:00
jobspec Allow custom ports for services and checks 2017-12-08 12:03:00 -08:00
nomad refactor creating a new tls configuration 2018-01-16 08:02:39 -05:00
scheduler gofmt 2018-01-04 14:45:15 -08:00
scripts Merge branch 'master' into 0.8 2018-01-03 16:06:38 -06:00
terraform Update README.md 2017-12-07 10:35:46 -08:00
testutil move to consul freeport implementation 2017-10-23 16:51:40 -07:00
ui Lock down nodejs version 2017-12-15 10:50:06 -08:00
vendor reload raft transport layer 2018-01-08 14:52:28 -05:00
version bump version and remove generated structs 2017-12-19 17:10:52 -08:00
website add documentation 2018-01-09 06:34:46 -05:00
.gitattributes Initial commit 2015-06-01 12:21:00 +02:00
.gitignore generated files 2017-12-19 16:57:34 -08:00
.travis.yml Makes macos/osx builds optional in Travis 2017-12-20 16:32:15 -08:00
CHANGELOG.md gofmt 2018-01-04 14:45:15 -08:00
GNUmakefile Add changelog formatting to make dev 2018-01-03 16:38:41 -06:00
ISSUE_TEMPLATE.md Update ISSUE_TEMPLATE.md 2016-03-21 18:12:50 -07:00
LICENSE Initial commit 2015-06-01 12:21:00 +02:00
README.md Update README.md 2017-12-06 10:51:39 -08:00
Vagrantfile Fix whitespace 2017-11-01 11:14:25 -07:00
appveyor.yml sync 2017-09-19 10:08:23 -05:00
build_linux_arm.go Fix 32bit arm build 2017-02-09 11:22:17 -08:00
commands.go policy list and token self commands 2017-10-13 16:31:46 -07:00
main.go sync 2017-10-13 14:36:02 -07:00
main_test.go Adding initial skeleton 2015-06-01 13:46:21 +02:00

README.md

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
...
$ bin/nomad
...

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
...