Go to file
Mahmood Ali 55456fc823 Set a 1s floor for Vault renew operation backoff 2018-11-20 17:10:54 -05:00
.circleci add circleci website build 2018-11-20 16:59:34 -05:00
acl fixup from code review 2017-10-17 17:34:06 -04:00
api Populate alloc stats API with device stats 2018-11-16 10:26:32 -05:00
client Set User-Agent header when hitting Vault API 2018-11-20 17:10:54 -05:00
command Merge pull request #4884 from hashicorp/f-alloc-devices-cli 2018-11-16 18:04:54 -05:00
demo Merge pull request #4164 from PeterDaveHello/update-demo-vagrantfile 2018-04-20 13:59:01 -07:00
dev dev files 2018-06-01 13:29:11 -07:00
devices/gpu/nvidia Allow nullable fields in StatValues 2018-11-14 14:41:19 -05:00
dist systemd unit - Do not restart if unit fails 3 times in 10s 2018-08-06 14:52:08 +02:00
drivers client: interpolate driver configurations 2018-11-15 16:25:57 -08:00
e2e skip e2e/vault if integration isn't set 2018-09-25 11:29:09 -07:00
helper address review comments 2018-10-30 13:58:52 -04:00
integrations spelling: registrations 2018-03-11 18:40:53 +00:00
jobspec review comments 2018-10-15 15:31:13 -07:00
lib code review feedback 2018-09-04 16:10:11 -05:00
nomad Set a 1s floor for Vault renew operation backoff 2018-11-20 17:10:54 -05:00
plugins Expose Device Stats in /client/stats API endpoint 2018-11-14 14:41:19 -05:00
scheduler scheduler: Add is_set/is_not_set constraints 2018-11-15 11:00:32 -08:00
scripts Ignore apt-get update failures in CI 2018-11-13 10:21:40 -05:00
terraform AWS sandbox environment upgrade (#4873) 2018-11-13 23:21:01 -05:00
testutil tests: test logs endpoint against pending task 2018-10-16 16:56:55 -07:00
ui Merge pull request #4860 from hashicorp/b-ui-allocation-detail-empty-state 2018-11-19 12:43:39 -08:00
vendor update consul template 2018-11-15 14:15:12 -06:00
version remove structs + bump version 2018-06-11 13:52:19 -07:00
website remove packer.json since CircleCI builds the site 2018-11-20 16:59:42 -05:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore Remove committed test output and gitignore it 2018-11-20 10:16:03 -08:00
.travis.yml docs: broke docs testing out into its own travis stage 2018-10-08 15:11:46 -04:00
CHANGELOG.md Update CHANGELOG.md 2018-11-20 14:16:37 -06:00
GNUmakefile webiste -> website 2018-11-19 18:50:42 -08: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 add note to readme to install protoc for local development 2018-08-06 11:45:00 -04:00
Vagrantfile renamed vagrant script to accurately reflect non-privileged requirement 2018-10-05 10:07:05 -04:00
appveyor.yml test: build with mock_driver by default 2018-04-18 14:45:33 -07:00
build_linux_arm.go Fix 32bit arm build 2017-02-09 11:22:17 -08:00
main.go executor v2 (#4656) 2018-10-16 16:53:31 -07: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 release. This will compile Nomad for multiple platforms and place the resulting binaries into the ./pkg directory:

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