Go to file
Michael Schurter 8e7870b590 cli: remove info color on monitored output 2018-03-30 15:51:48 -07:00
acl
api cli: remove unreachable drain message 2018-03-30 14:15:12 -07:00
client test: don't rely on alloc runner update count 2018-03-30 09:34:33 -07:00
command cli: remove info color on monitored output 2018-03-30 15:51:48 -07:00
demo demo: give agents unique names 2018-03-27 14:29:53 -07:00
dev spelling: website 2018-03-11 19:17:53 +00:00
dist
e2e Another e2e rescheduling test case 2018-03-29 20:48:55 -05:00
helper testlog: override testlogger with envvar 2018-03-21 16:49:48 -07:00
integrations spelling: registrations 2018-03-11 18:40:53 +00:00
jobspec s/linear/constant/g 2018-03-26 14:45:09 -05:00
lib Move delayheap to lib package 2018-03-14 16:10:32 -05:00
nomad Test transistion from both infinite and a future deadline to force 2018-03-30 11:24:39 -07:00
scheduler Fix lost handling of not actually down nodes 2018-03-30 14:17:41 -07:00
scripts Bump Go to 1.10 in Vagrantfile 2018-03-16 16:17:16 -07:00
terraform Bump Hadoop version in run-time config scripts; update AMI 2018-03-20 19:55:09 +00:00
testutil Unmark drain when nodes hit their deadline and only batch/system left and add all job type integration test 2018-03-28 17:25:58 -07:00
ui Merge pull request #4081 from hashicorp/b-ui-service-breadcrumbs 2018-03-29 15:08:14 -07:00
vendor vendor gosockaddr 2018-03-20 10:39:39 -07:00
version
website Merge pull request #4055 from hashicorp/docs-4008-ports 2018-03-29 17:03:38 -07:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore
.travis.yml travis: use go 1.10.x 2018-03-22 09:53:16 -07:00
CHANGELOG.md changelog 2018-03-30 10:59:31 -07:00
GNUmakefile Run yarn silently during make ember-dist 2018-03-20 11:31:35 -07:00
ISSUE_TEMPLATE.md
LICENSE
README.md Oxford comma-ing 2018-03-06 16:48:54 -08:00
Vagrantfile fixing box timeout issue waiting for interfaces 2018-02-14 21:30:11 -08:00
appveyor.yml
build_linux_arm.go
main.go cli: differentiate normal output vs info 2018-03-30 11:42:11 -07:00
main_test.go

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.

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

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

  • Flexible Workloads: Nomad has extensible support for task drivers, allowing it to run containerized, virtualized, and standalone applications. Users can easily start Docker containers, VMs, or application runtimes like Java. Nomad supports Linux, Windows, BSD, and OSX, providing the flexibility to run any workload.

  • Built for Scale: Nomad was designed from the ground up to support global scale infrastructure. Nomad is distributed and highly available, using both leader election and state replication to provide availability in the face of failures. Nomad is optimistically concurrent, enabling all servers to participate in scheduling decisions which increases the total throughput and reduces latency to support demanding workloads. Nomad has been proven to scale to cluster sizes that exceed 10k nodes in real-world production environments.

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