Go to file
Preetha Appan b4a722e08f
Basic consul registration e2e
2019-01-26 10:58:25 -06:00
.circleci add circleci website build 2018-11-20 16:59:34 -05:00
acl fixup: Code Review 2018-12-12 12:43:16 +01:00
api Merge pull request #5223 from hashicorp/f-jobs-list-datacenters 2019-01-24 08:13:30 -06:00
client Merge branch 'master' into f-driver-upgradepath-test 2019-01-23 21:01:24 -05:00
command Merge pull request #5196 from hashicorp/f-plugin-utils 2019-01-23 06:59:32 -08:00
demo no need to double the work 2018-12-02 01:03:44 +03: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 systemd unit - Do not restart if unit fails 3 times in 10s 2018-08-06 14:52:08 +02:00
drivers Merge pull request #5237 from hashicorp/b-docker-09upgrade-shutdown 2019-01-25 12:13:03 -05:00
e2e Basic consul registration e2e 2019-01-26 10:58:25 -06:00
helper drivers: pass logger through driver plugin client 2019-01-25 09:38:41 -05:00
integrations spelling: registrations 2018-03-11 18:40:53 +00:00
jobspec convert driver to device for device constraint/attributes 2019-01-23 10:58:45 -08:00
lib code review feedback 2018-09-04 16:10:11 -05:00
nomad Merge pull request #5228 from hashicorp/f-vault-err-tweaks 2019-01-25 11:17:31 -05:00
plugins drivers: pass logger through driver plugin client 2019-01-25 09:38:41 -05:00
scheduler convert driver to device for device constraint/attributes 2019-01-23 10:58:45 -08:00
scripts ci: run checkscripts 2019-01-23 10:54:52 -05:00
terraform change retry_join to a map for easier tag handling 2018-12-18 15:48:17 -08:00
testutil goimports 2019-01-22 15:44:31 -08:00
ui Merge pull request #4981 from hashicorp/b-ui-hide-stats-graphs-for-non-running-resources 2018-12-18 11:15:39 -08:00
vendor drivers/rkt: Remove unused github.com/rkt/rkt 2019-01-23 10:53:49 -05:00
version remove structs + bump version 2018-06-11 13:52:19 -07:00
website Fix broken scheduling links in advanced scheduling guide 2019-01-26 10:57:49 -06:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore client/state: support upgrading from 0.8->0.9 2018-12-19 10:39:27 -08:00
.travis.yml ci: run seperate build jobs for slower packages 2019-01-23 15:39:34 -05:00
CHANGELOG.md changelog 2019-01-25 14:18:56 -05:00
GNUmakefile ci: run seperate build jobs for slower packages 2019-01-23 15:39:34 -05: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 client: add proper build flag to allocrunner testing.go 2018-12-19 20:22:07 -05:00
Vagrantfile renamed vagrant script to accurately reflect non-privileged requirement 2018-10-05 10:07:05 -04:00
appveyor.yml appveyor: disable tests on windows again 2019-01-17 18:43:14 +01:00
build_linux_arm.go Fix 32bit arm build 2017-02-09 11:22:17 -08:00
main.go cli: Hide `nomad docker_logger` from help output 2019-01-23 16:27:05 +01:00
main_test.go Adding initial skeleton 2015-06-01 13:46:21 +02:00
nsenter_linux.go executor v2 (#4656) 2018-10-16 16:53:31 -07: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
...