Find a file
Kent 'picat' Gruber 8ff9b566f1 Cleanup, enable the Vault UI, and bind to all IPv4 addresses in the config
This make the config cleaner, and allows Vault to actually be accessible through a load balancer.
2020-07-16 15:26:22 -04:00
.circleci use node 12 2020-06-24 21:16:15 -04:00
.github Remove minor version from audit comparison action (#8048) 2020-05-26 15:34:12 -05:00
.netlify
acl
api fix volume deregister -force params in API (#8380) 2020-07-08 10:08:22 -04:00
client Merge pull request #8333 from hashicorp/b-test-tweak-20200701 2020-07-10 11:18:28 -04:00
command MRD: all regions should start pending (#8433) 2020-07-14 10:57:37 -04:00
contributing doc: nomad debug cli (#8278) 2020-06-25 13:48:27 -04:00
demo demos: remove externalized demo files 2020-07-02 11:30:59 -05:00
dev
devices/gpu/nvidia
dist
drivers removes nvidia import from docker test (#8312) 2020-06-30 09:34:59 -04:00
e2e Merge pull request #8335 from hashicorp/f-cnative-host-e2e 2020-07-10 10:24:43 -05:00
helper revert changes from earlier change 2020-06-12 14:02:43 -04:00
integrations
internal/testing/apitests tests: non-CAS should be updated 2020-06-26 10:48:33 -04:00
jobspec better testing of scaling parsing, fixed some broken tests by api 2020-07-04 19:32:37 +00:00
lib deps: Switch to Go modules for dependency management 2020-06-02 14:30:36 -05:00
nomad MRD: all regions should start pending (#8433) 2020-07-14 10:57:37 -04:00
plugins csi: add VolumeContext to NodeStage/Publish RPCs (#8239) 2020-06-22 13:54:32 -04:00
scheduler MRD: all regions should start pending (#8433) 2020-07-14 10:57:37 -04:00
scripts build: update from Go 1.14.3 to Go 1.14.4 2020-06-16 10:07:05 -07:00
terraform Cleanup, enable the Vault UI, and bind to all IPv4 addresses in the config 2020-07-16 15:26:22 -04:00
testutil gracefully shutdown test server 2020-05-27 08:59:06 -04:00
tools use specific sha (#8329) 2020-07-01 10:32:45 -04:00
ui Change edition to Octane (#8418) 2020-07-13 09:26:12 -05:00
vendor Merge pull request #8333 from hashicorp/b-test-tweak-20200701 2020-07-10 11:18:28 -04:00
version version to 0.12.1-dev 2020-07-09 16:48:54 +00:00
website Merge pull request #7042 from hashicorp/docs-healthy-deadline 2020-07-13 08:40:11 -07:00
.gitattributes
.gitignore ignore vagrant directory even if symlinked (#8114) 2020-06-04 10:24:15 -04:00
.golangci.yml
build_linux_arm.go
CHANGELOG.md changelog for MRD datacenters validation (#8429) 2020-07-13 14:03:40 -04:00
GNUmakefile use specific sha (#8329) 2020-07-01 10:32:45 -04:00
go.mod tests: avoid os.Exit in a test 2020-07-01 15:25:13 -04:00
go.sum Update github.com/syndtr/gocapability 2020-06-22 17:10:41 -04:00
LICENSE
main.go
main_test.go
README.md build: update from Go 1.14.3 to Go 1.14.4 2020-06-16 10:07:05 -07:00
Vagrantfile

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, CloudFlare, Roblox, Pandora, 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 applications 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. Guides are available on HashiCorp Learn 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.4+ 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.