Find a file
2017-12-11 17:06:07 -08:00
acl
api Allow custom ports for services and checks 2017-12-08 12:03:00 -08:00
client Fix test broken by mock updates 2017-12-08 16:45:25 -08:00
command Be more defensive in port checks 2017-12-08 12:27:57 -08:00
demo
dev
dist
e2e/migrations
helper Changes service name validation logic to ignore any environment variables first. 2017-11-15 15:35:43 -06: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 Lowercase service IDs to prevent eye bleeding 2017-12-08 15:54:04 -08:00
scheduler Fix port labels on mock Alloc/Job/Node 2017-12-08 14:50:06 -08:00
scripts chown $GOPATH for vagrant user 2017-12-11 17:06:07 -08:00
terraform Update README.md 2017-12-07 10:35:46 -08:00
testutil
ui Merge pull request #3631 from hashicorp/b-ui-expand-definition 2017-12-07 14:42:01 -08:00
vendor Merge pull request #3608 from hashicorp/b-3342-windows-log-leak 2017-12-08 10:59:26 -08:00
version
website Merge pull request #3619 from hashicorp/f-3380-custom-ports 2017-12-11 11:43:33 -08:00
.gitattributes
.gitignore add Azure .pem file to .gitignore 2017-11-15 19:42:30 +00:00
.travis.yml
appveyor.yml
build_linux_arm.go
CHANGELOG.md Hash fields used in task service IDs 2017-12-08 12:03:43 -08:00
commands.go
GNUmakefile drop gas 2017-12-04 13:07:24 -08:00
ISSUE_TEMPLATE.md
LICENSE
main.go
main_test.go
README.md Update README.md 2017-12-06 10:51:39 -08:00
Vagrantfile

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