Go to file
Tim Gross 62548616d4
client: allow `drain_on_shutdown` configuration (#16827)
Adds a new configuration to clients to optionally allow them to drain their
workloads on shutdown. The client sends the `Node.UpdateDrain` RPC targeting
itself and then monitors the drain state as seen by the server until the drain
is complete or the deadline expires. If it loses connection with the server, it
will monitor local client status instead to ensure allocations are stopped
before exiting.
2023-04-14 15:35:32 -04:00
.changelog client: allow `drain_on_shutdown` configuration (#16827) 2023-04-14 15:35:32 -04:00
.circleci [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
.github [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
.release [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
.semgrep [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
.tours
acl [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
api api: enable support for setting original job source (#16763) 2023-04-11 08:45:08 -05:00
ci [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
client client: allow `drain_on_shutdown` configuration (#16827) 2023-04-14 15:35:32 -04:00
command client: allow `drain_on_shutdown` configuration (#16827) 2023-04-14 15:35:32 -04:00
contributing upgrade go to 1.20.3 2023-04-05 12:18:19 -04:00
demo [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
dev [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
drivers deps: update docker to 23.0.3 (#16862) 2023-04-12 14:13:36 -05:00
e2e drain: use client status to determine drain is complete (#14348) 2023-04-13 08:55:28 -04:00
helper [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
integrations [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
internal/testing/apitests [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
jobspec [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
jobspec2 api: enable support for setting original job source (#16763) 2023-04-11 08:45:08 -05:00
lib [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
nomad client: allow `drain_on_shutdown` configuration (#16827) 2023-04-14 15:35:32 -04:00
plugins deps: update docker to 23.0.3 (#16862) 2023-04-12 14:13:36 -05:00
scheduler api: enable support for setting original job source (#16763) 2023-04-11 08:45:08 -05:00
scripts [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
terraform [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
testutil [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
tools [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
ui [ui, compliance] Remove the newline after .hbs copyright headers (#16861) 2023-04-14 13:08:13 -04:00
version [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
website client: allow `drain_on_shutdown` configuration (#16827) 2023-04-14 15:35:32 -04:00
.git-blame-ignore-revs ignore b0a20b4dc965a38b0c843f47c16685ccad7439da (#13648) 2022-07-07 15:16:18 -07:00
.gitattributes
.gitignore git: ignore .fleet directory (#16144) 2023-02-13 07:39:30 -06:00
.go-version upgrade go to 1.20.3 2023-04-05 12:18:19 -04:00
.golangci.yml [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
.semgrepignore
CHANGELOG.md Merge release 1.5.3 files 2023-04-05 12:32:00 -04:00
CODEOWNERS ensure engineering has merge authority on build pipeline (#15350) 2022-11-21 14:30:02 -05:00
GNUmakefile deps: bump build and linter tool versions (#16858) 2023-04-11 17:01:14 -05:00
LICENSE [COMPLIANCE] Update MPL 2.0 LICENSE (#14884) 2022-10-13 08:43:12 -04:00
README.md Adds public roadmap project to readme 2023-03-20 15:11:38 -07:00
Vagrantfile dev: make cni, consul, dev, docker, and vault scripts Lima compat. (#16689) 2023-03-28 16:21:14 +01:00
build_linux_arm.go [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
go.mod deps: update docker to 23.0.3 (#16862) 2023-04-12 14:13:36 -05:00
go.sum deps: update docker to 23.0.3 (#16862) 2023-04-12 14:13:36 -05:00
main.go [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00
main_test.go [COMPLIANCE] Add Copyright and License Headers 2023-04-10 15:36:59 +00:00

README.md

Nomad License: MPL 2.0 Discuss

HashiCorp Nomad logo

Nomad is a simple and flexible workload orchestrator to deploy and manage containers (docker, podman), non-containerized applications (executable, Java), and virtual machines (qemu) across on-prem and clouds at scale.

Nomad is supported on Linux, Windows, and macOS. A commercial version of Nomad, Nomad Enterprise, is also available.

Nomad provides several key features:

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

Quick Start

Testing

See Learn: Getting Started for instructions on setting up a local Nomad cluster for non-production use.

Optionally, find Terraform manifests for bringing up a development Nomad cluster on a public cloud in the terraform directory.

Production

See Learn: Nomad Reference Architecture for recommended practices and a reference architecture for production deployments.

Documentation

Full, comprehensive documentation is available on the Nomad website: https://www.nomadproject.io/docs

Guides are available on HashiCorp Learn.

Roadmap

A timeline of major features expected for the next release or two can be found in the Public Roadmap.

This roadmap is a best guess at any given point, and both release dates and projects in each release are subject to change. Do not take any of these items as commitments, especially ones later than one major release away.

Contributing

See the contributing directory for more developer documentation.