Go to file
Seth Hoenig 9a6988f55b deps: adjust to gzip handler zero length response body
After swapping gzip handler to use the gorilla library, we
must account for a quirk in how zero/minimal length response
bodies are delivered.

The previous gzip handler was configured to compress all responses
regardless of size - even if the data was zero length or below the
network MTU. This behavior changed in [v1.1.0](c551b6c3b4 (diff-de723e6602cc2f16f7a9d85fd89d69954edc12a49134dab8901b10ee06d1879d))
which is why we could not upgrade.

The Nomad HTTP Client mutates the http.Response.Body object, making
a strong assumption that if the Content-Encoding header is set to "gzip",
the response will be readable via gzip decoder. This is no longer true
for the nytimes gzip handler, and is also not true for the gorilla gzip
handler.

It seems in practice this only makes a difference on the /v1/operator/license
endpoint which returns an empty response in OSS Nomad.

The fix here is to simply not wrap the response body reader if we
encounter an io.EOF while creating the gzip reader - indicating there
is no data to decode.
2022-01-19 11:52:19 -06:00
.changelog deps: adjust to gzip handler zero length response body 2022-01-19 11:52:19 -06:00
.circleci Version 1.2.3 2021-12-13 10:12:07 -05:00
.github fix: backport release branch target (#11627) 2021-12-07 09:45:46 -05:00
.tours Make number of scheduler workers reloadable (#11593) 2022-01-06 11:56:13 -05:00
acl lint: mark false positive or fix gocritic append lint errors. 2021-09-06 10:49:44 +02:00
api deps: adjust to gzip handler zero length response body 2022-01-19 11:52:19 -06:00
client remove generated files 2022-01-19 00:23:24 +00:00
command deps: swap gzip handler for gorilla 2022-01-19 11:52:19 -06:00
contributing Version 1.2.3 2021-12-13 10:12:07 -05:00
demo [demo] Kadalu CSI support for Nomad (#11207) 2021-10-06 15:29:15 -04:00
dev docs: swap master for main in Nomad repo 2021-03-08 14:26:31 -05:00
drivers deps: upgrade docker and runc 2022-01-18 08:35:26 -06:00
e2e chore: fixup inconsistent method receiver names. (#11704) 2021-12-20 11:44:21 +01:00
helper deps: upgrade docker and runc 2022-01-18 08:35:26 -06:00
integrations spelling: registrations 2018-03-11 18:40:53 +00:00
internal/testing/apitests Revert "Return SchedulerConfig instead of SchedulerConfigResponse struct (#10799)" (#11433) 2021-11-02 17:42:52 -04:00
jobspec Parse `job > group > consul` block in HCL1 (#11423) 2021-11-03 13:49:32 -04:00
jobspec2 Expose Consul template configuration parameters (#11606) 2022-01-10 10:19:07 -05:00
lib chore: fixup inconsistent method receiver names. (#11704) 2021-12-20 11:44:21 +01:00
nomad remove generated files 2022-01-19 00:23:24 +00:00
plugins chore: fixup inconsistent method receiver names. (#11704) 2021-12-20 11:44:21 +01:00
scheduler scheduler: detect and log unexpected scheduling collisions (#11793) 2022-01-14 20:09:14 -05:00
scripts golang security update 1.17.5 2021-12-10 13:50:22 -05:00
terraform terraform: update installed version used to 1.0.11. 2021-11-19 09:33:11 +01:00
testutil cli: refactor operator debug capture (#11466) 2021-11-05 19:43:10 -04:00
tools build: bump go version to 1.17.3 (#11461) 2021-11-05 15:34:24 -04:00
ui ui: fix test (#11870) 2022-01-18 10:36:10 -05:00
version prepare for next release 2022-01-19 11:51:59 -05:00
website update download to Nomad v1.2.4 (#11880) 2022-01-19 11:10:24 -05:00
.gitattributes Remove invalid gitattributes 2018-02-14 14:47:43 -08:00
.gitignore terraform: update installed version used to 1.0.11. 2021-11-19 09:33:11 +01:00
.golangci.yml chore: fixup inconsistent method receiver names. (#11704) 2021-12-20 11:44:21 +01:00
CHANGELOG.md prepare for next release 2022-01-19 11:51:59 -05:00
GNUmakefile prepare for next release 2022-01-19 11:51:59 -05:00
LICENSE Initial commit 2015-06-01 12:21:00 +02:00
README.md README: Align with Consul README (#9681) 2020-12-18 09:38:34 -08:00
Vagrantfile tools: update virtualbox networking configuration (#11561) 2021-11-24 10:45:58 -05:00
build_linux_arm.go gofmt all the files 2021-10-01 10:14:28 -04:00
go.mod deps: swap gzip handler for gorilla 2022-01-19 11:52:19 -06:00
go.sum deps: swap gzip handler for gorilla 2022-01-19 11:52:19 -06:00
main.go Raft Debugging Improvements (#11414) 2021-11-04 10:16:12 -04:00
main_test.go Adding initial skeleton 2015-06-01 13:46:21 +02:00

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.