Find a file
Tim Gross 7e4fd79eee
e2e: CSI test should detect un-deregisterable volumes (#9343)
Assert that deregistering a volume works without errors following a volume
reap. Use CLI helpers where feasible to exercise CSI command line. Dump plugin
allocation logs on deregistration failures for debugging purposes.
2020-11-13 09:31:21 -05:00
.circleci build: upgrade from Go 1.15.4 to 1.15.5 2020-11-12 14:19:26 -08:00
.github remove local SECURITY.md in favor of org-wide policy 2020-08-24 15:41:28 -07:00
.netlify
acl added new policy capabilities for recommendations API 2020-10-28 14:32:16 +00:00
api lifecycle: add poststop hook (#8194) 2020-11-12 08:01:42 -08:00
client lifecycle: add poststop hook (#8194) 2020-11-12 08:01:42 -08:00
command nomad operator debug - add client node filtering arguments (#9331) 2020-11-12 11:25:28 -05:00
contributing docs: add contributor docs for issue labels (#8723) 2020-08-24 10:19:57 -04:00
demo Update Cinder CSI example docs (#9267) 2020-11-05 08:19:16 -05:00
dev
devices/gpu/nvidia
dist
drivers Merge pull request #8291 from shishir-a412ed/cpusets 2020-11-11 17:13:27 -05:00
e2e e2e: CSI test should detect un-deregisterable volumes (#9343) 2020-11-13 09:31:21 -05:00
helper Send events to EventSinks (#9171) 2020-10-26 17:27:54 -04:00
integrations
internal/testing/apitests
jobspec added new policy capabilities for recommendations API 2020-10-28 14:32:16 +00:00
jobspec2 appease deadcode linter 2020-11-12 11:44:49 -05:00
lib
nomad nomad/structs: fix noop breaks (#9348) 2020-11-13 08:28:11 -05:00
plugins protos: Update .proto files not to use Go package name (#9301) 2020-11-10 08:42:35 -08:00
scheduler Events/msgtype cleanup (#9117) 2020-10-19 09:30:15 -04:00
scripts build: upgrade from Go 1.15.4 to 1.15.5 2020-11-12 14:19:26 -08:00
terraform Use latest AMI for Ubuntu Xenial based on search (#9076) 2020-10-14 11:01:54 -04:00
testutil nomad operator debug - add client node filtering arguments (#9331) 2020-11-12 11:25:28 -05:00
tools added new policy capabilities for recommendations API 2020-10-28 14:32:16 +00:00
ui Fix flaky lifecycle chart tests 2020-11-12 09:16:53 -08:00
vendor auto-complete for recommendations CLI, plus OSS components of recommendations prefix search 2020-11-11 11:13:43 +00:00
version s/0.13/1.0/g 2020-10-14 15:17:47 -07:00
website docs: update brige network subnet docs 2020-11-12 09:11:24 -06:00
.gitattributes
.gitignore
.golangci.yml
build_linux_arm.go
CHANGELOG.md docs: mention upgrade to Go 1.15.5 2020-11-12 14:23:32 -08:00
GNUmakefile protos: Update .proto files not to use Go package name (#9301) 2020-11-10 08:42:35 -08:00
go.mod Api/event stream payload values (#9277) 2020-11-05 13:04:18 -05:00
go.sum Api/event stream payload values (#9277) 2020-11-05 13:04:18 -05:00
LICENSE
main.go add helper commands for debugging state 2020-08-31 08:45:59 -04:00
main_test.go
README.md build: upgrade from Go 1.15.4 to 1.15.5 2020-11-12 14:19:26 -08: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 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.15.5+ 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.