Go to file
Michael Lange 96ef93ca5f Commit the deprecation workflow to prevent fixed deprecations from creeping back in 2019-04-10 14:54:35 -07:00
.circleci add circleci website build 2018-11-20 16:59:34 -05:00
.github Mention nomad-oss-debug in issue template 2019-04-02 10:07:06 -07:00
acl fixup: Code Review 2018-12-12 12:43:16 +01:00
api Update api/jobs.go 2019-04-10 10:34:10 -05:00
client vault client test: minor formatting 2019-04-10 10:34:10 -05:00
command agent config: cleaner VAULT_ env lookup 2019-04-10 10:34:10 -05:00
demo Fixup mixed tabs in script for Vagrantfile demo 2019-03-26 15:23:38 -07:00
dev revert unintended change 2019-01-18 17:36:35 -06:00
devices/gpu/nvidia Update devices/gpu/nvidia/README.md 2019-01-23 17:44:24 -08:00
dist docs: sync systemd unit files; update deploy guide 2019-03-19 15:18:12 -07:00
drivers drivers/docker: fix image name handleing when prefixed with https:// 2019-04-04 22:10:18 -04:00
e2e vault e2e: pass vault version into setup instead of having to infer it from test name 2019-04-10 10:34:10 -05:00
helper e2e: add NomadAgent and basic client state test 2019-03-21 07:14:34 -07:00
integrations spelling: registrations 2018-03-11 18:40:53 +00:00
internal/testing/apitests Divest api/ package of deps elsewhere in the nomad repo. (#5488) 2019-03-29 14:47:40 -04:00
jobspec Change types of weights on spread/affinity 2019-01-30 12:20:38 -08:00
lib circbufwritter: add defer to stop ticker in flush loop 2019-01-28 14:33:20 -05:00
nomad server vault client: use two vault clients, one with namespace, one without for /sys calls 2019-04-10 10:34:10 -05:00
plugins Simplify proto conversion and handle swap 2019-03-30 15:18:28 -04:00
scheduler Add NodeName to the alloc/job status outputs. 2019-04-10 10:34:10 -05:00
scripts scripts: better prerelease extractor 2019-04-08 21:42:10 -04:00
terraform docs: sync systemd unit files; update deploy guide 2019-03-19 15:18:12 -07:00
testutil tests: IsTravis() -> IsCI() 2019-02-20 08:21:03 -05:00
ui Commit the deprecation workflow to prevent fixed deprecations from creeping back in 2019-04-10 14:54:35 -07:00
vendor vault client test: minor formatting 2019-04-10 10:34:10 -05:00
version Bump to 0.9.1-dev 2019-04-09 09:01:48 -07:00
website docs: -vault-namespace, VAULT_NAMESPACE, and config 2019-04-10 10:34:10 -05:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore Upgrade to Ember 3.4 2019-04-10 14:54:34 -07:00
.travis.yml Regenerate Proto files (#5421) 2019-03-14 10:56:27 -04:00
CHANGELOG.md Bump to 0.9.1-dev 2019-04-09 09:01:48 -07:00
GNUmakefile release: skip check step when cutting release 2019-03-21 14:57:03 -04:00
LICENSE Initial commit 2015-06-01 12:21:00 +02:00
README.md client: add proper build flag to allocrunner testing.go 2018-12-19 20:22:07 -05:00
Vagrantfile Add a Docker release scripts 2019-03-17 10:37:36 -04:00
appveyor.yml run fifo tests on Windows 2019-04-01 13:18:03 -04:00
build_linux_arm.go Fix 32bit arm build 2017-02-09 11:22:17 -08:00
main.go ui: Support colored output on Windows 2019-02-20 14:01:35 +01:00
main_test.go Adding initial skeleton 2015-06-01 13:46:21 +02:00
nsenter_linux.go fix possible panic in libcontainer shim init 2019-03-11 21:57:21 -04: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.

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

To compile protobuf files, installing protoc is required: See
https://github.com/google/protobuf for more information.

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 prerelease and make release. This will generate all the static assets, compile Nomad for multiple platforms and place the resulting binaries into the ./pkg directory:

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