Go to file
Tim Gross 766025cde7
CSI: plugin supervisor prestart should not mark itself done (#12752)
The task runner hook `Prestart` response object includes a `Done`
field that's intended to tell the client not to run the hook
again. The plugin supervisor creates mount points for the task during
prestart and saves these mounts in the hook resources. But if a client
restarts the hook resources will not be populated. If the plugin task
restarts at any time after the client restarts, it will fail to have
the correct mounts and crash loop until restart attempts run out.

Fix this by not returning `Done` in the response, just as we do for
the `volume_mount_hook`.
2022-04-22 13:07:47 -04:00
.changelog CSI: plugin supervisor prestart should not mark itself done (#12752) 2022-04-22 13:07:47 -04:00
.circleci
.github
.release
.semgrep
.tours
acl
api vault: revert support for entity aliases (#12723) 2022-04-22 10:46:34 -04:00
ci
client CSI: plugin supervisor prestart should not mark itself done (#12752) 2022-04-22 13:07:47 -04:00
command vault: revert support for entity aliases (#12723) 2022-04-22 10:46:34 -04:00
contributing
demo
dev
drivers
e2e E2E: remove platform specific realpath code from UI run script (#12750) 2022-04-22 10:10:18 -04:00
helper
integrations
internal/testing/apitests
jobspec vault: revert support for entity aliases (#12723) 2022-04-22 10:46:34 -04:00
jobspec2
lib
nomad vault: revert support for entity aliases (#12723) 2022-04-22 10:46:34 -04:00
plugins
scheduler
scripts
terraform
testutil
tools
ui [ui] Disconnected Clients: "Unknown" allocations in the UI (#12544) 2022-04-22 11:25:02 -04:00
version
website vault: revert support for entity aliases (#12723) 2022-04-22 10:46:34 -04:00
.gitattributes
.gitignore
.go-version
.golangci.yml
.semgrepignore
CHANGELOG.md
CODEOWNERS
GNUmakefile
LICENSE
README.md
Vagrantfile
build_linux_arm.go
go.mod deps: update consul-template to v0.29.0 (#12747) 2022-04-22 09:58:54 -07:00
go.sum deps: update consul-template to v0.29.0 (#12747) 2022-04-22 09:58:54 -07:00
jsconfig.json [ui, bugfix] Link fix for volumes where per_alloc=true (#12713) 2022-04-21 13:57:18 -04:00
main.go
main_test.go

README.md

Nomad Build Status 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.

Contributing

See the contributing directory for more developer documentation.