Go to file
Chris Baker cf353594b5
Merge pull request #8123 from hashicorp/docs-update-version-for-0.12.0
update version for 0.12.0 dev
2020-06-05 14:34:38 -05:00
.circleci ci: run static generators as part of CI 2020-06-04 18:23:29 -04:00
.github Remove minor version from audit comparison action (#8048) 2020-05-26 15:34:12 -05:00
.netlify Remove most Netlify configuration (#6194) 2019-08-22 15:54:23 -05:00
acl fix spelling errors (#6985) 2020-04-20 09:28:19 -04:00
api Merge pull request #8083 from hashicorp/test-deflake-20200531 2020-06-01 09:28:45 -04:00
client Delayed evaluations for `stop_after_client_disconnect` can cause unwanted extra followup evaluations around job garbage collection (#8099) 2020-06-03 09:48:38 -04:00
command deps: Switch to Go modules for dependency management 2020-06-02 14:30:36 -05:00
contributing structs: fix compatibility between api and nomad/structs proxy definitions 2020-04-13 15:59:45 -06:00
demo Merge pull request #7781 from hashicorp/demo-countdash-docker 2020-05-07 08:34:20 -06:00
dev build: use hashicorp hclfmt 2020-05-24 18:31:57 -05:00
devices/gpu/nvidia cleanup driver eventor goroutines 2020-05-26 11:04:04 -04:00
dist dist: make README consistent with service unit (#7648) 2020-04-08 09:32:03 -04:00
drivers Merge pull request #8087 from hashicorp/f-docker-mem-config 2020-06-01 12:16:55 -05:00
e2e base podman e2e test and provisioning updates (#8104) 2020-06-03 14:06:58 -04:00
helper Merge pull request #8047 from hashicorp/f-snapshot-save 2020-06-01 07:55:16 -04:00
integrations spelling: registrations 2018-03-11 18:40:53 +00:00
internal/testing/apitests update rest of consul packages 2020-02-16 16:25:04 -06:00
jobspec build: use hashicorp hclfmt 2020-05-24 18:31:57 -05:00
lib deps: Switch to Go modules for dependency management 2020-06-02 14:30:36 -05:00
nomad Merge pull request #8089 from hashicorp/b-leader-worker-count 2020-06-04 12:01:01 -04:00
plugins cleanup driver eventor goroutines 2020-05-26 11:04:04 -04:00
scheduler Delayed evaluations for `stop_after_client_disconnect` can cause unwanted extra followup evaluations around job garbage collection (#8099) 2020-06-03 09:48:38 -04:00
scripts build: update from Go 1.14.1 to Go 1.14.3 2020-05-16 10:41:20 -04:00
terraform separate vars and outputs into their own files and update default link in nomad binary variable to 0.10.0 release (#6550) 2019-10-25 14:15:30 -04:00
testutil gracefully shutdown test server 2020-05-27 08:59:06 -04:00
tools Ensure we are using the latest go-bindata tools 2020-06-04 18:49:12 -04:00
ui Remove vendored xterm.js files 2020-06-03 09:25:19 -07:00
vendor Vendor gopsutil with go mod fix (#8108) 2020-06-03 16:09:27 -04:00
version update version for 0.12.0 dev 2020-06-05 19:32:52 +00:00
website Fix review comments. 2020-06-01 19:15:01 -07:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore ignore vagrant directory even if symlinked (#8114) 2020-06-04 10:24:15 -04:00
.golangci.yml chore: Switch from gometalinter to golangci-lint 2019-12-05 18:58:13 -06:00
CHANGELOG.md changelog updates from release-0.11.3 2020-06-05 19:29:57 +00:00
GNUmakefile Ensure we are using the latest go-bindata tools 2020-06-04 18:49:12 -04:00
LICENSE Initial commit 2015-06-01 12:21:00 +02:00
README.md docs: add note in readme about exported package policy 2020-06-02 16:36:44 -05:00
Vagrantfile Remove rkt as a built-in driver 2020-02-26 22:16:41 -05:00
build_linux_arm.go Fix 32bit arm build 2017-02-09 11:22:17 -08:00
go.mod Revert "fix go.mod replace for api by using older semantics (#8113)" (#8115) 2020-06-04 11:29:03 -04:00
go.sum Vendor gopsutil with go mod fix (#8108) 2020-06-03 16:09:27 -04:00
main.go fix comment typo 2019-09-18 09:11:08 -04:00
main_test.go Adding initial skeleton 2015-06-01 13:46:21 +02:00

README.md

Nomad Build Status Discuss

Overview

Nomad is an easy-to-use, flexible, and performant workload orchestrator that deploys:

Nomad enables developers to use declarative infrastructure-as-code for deploying their applications (jobs). Nomad uses bin packing to efficiently schedule jobs and optimize for resource utilization. Nomad is supported on macOS, Windows, and Linux.

Nomad is widely adopted and used in production by PagerDuty, Target, Citadel, Trivago, SAP, Pandora, Roblox, eBay, Deluxe Entertainment, and more.

  • Deploy Containers and Legacy Applications: Nomads flexibility as an orchestrator enables an organization to run containers, legacy, and batch applications together on the same infrastructure. Nomad brings core orchestration benefits to legacy applications without needing to containerize via pluggable task drivers.

  • Simple & Reliable: Nomad runs as a single 75MB binary and is entirely self contained - combining resource management and scheduling into a single system. Nomad does not require any external services for storage or coordination. Nomad automatically handles application, node, and driver failures. Nomad is distributed and resilient, using leader election and state replication to provide high availability in the event of failures.

  • Device Plugins & GPU Support: Nomad offers built-in support for GPU workloads such as machine learning (ML) and artificial intelligence (AI). Nomad uses device plugins to automatically detect and utilize resources from hardware devices such as GPU, FPGAs, and TPUs.

  • Federation for Multi-Region, Multi-Cloud: Nomad was designed to support infrastructure at a global scale. Nomad supports federation out-of-the-box and can deploy jobs across multiple regions and clouds.

  • Proven Scalability: Nomad is optimistically concurrent, which increases throughput and reduces latency for workloads. Nomad has been proven to scale to clusters of 10K+ nodes in real-world production environments.

  • HashiCorp Ecosystem: Nomad integrates seamlessly with Terraform, Consul, Vault for provisioning, service discovery, and secrets management.

Getting Started

Get started with Nomad quickly in a sandbox environment on the public cloud or on your computer.

These methods are not meant for production.

Documentation & Guides

Documentation is available on the Nomad website here.

Resources

Who Uses Nomad

...and more!

Contributing to Nomad

If you wish to contribute to Nomad, you will need Go installed on your machine (version 1.14.3+ is required, and gcc-go is not supported).

See the contributing directory for more developer documentation.

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

Nomad creates many file handles for communicating with tasks, log handlers, etc. In some development environments, particularly macOS, the default number of file descriptors is too small to run Nomad's test suite. You should set ulimit -n 1024 or higher in your shell. This setting is scoped to your current shell and doesn't affect other running shells or future shells.

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

API Compatibility

Only the api/ and plugins/ packages are intended to be imported by other projects. The root Nomad module does not follow semver and is not intended to be imported directly by other projects.