This project is mirrored from https://gitee.com/mirrors/nomad.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 11 Jun, 2019 2 commits
-
-
Mahmood Ali authored
When a client is running against an old server (e.g. running 0.8), `alloc.AllocatedResources` may be nil, and we need to check the deprecated `alloc.TaskResources` instead. Fixes https://github.com/hashicorp/nomad/issues/5810
-
Mahmood Ali authored
Fix a panic related to updating alloc taskgroups
-
- 10 Jun, 2019 6 commits
-
-
Mahmood Ali authored
Alloc runner already tracks tasks associated with alloc. Here, we become defensive by relying on the alloc runner tracked tasks, rather than depend on server never updating the job unexpectedly.
-
Mahmood Ali authored
-
Mahmood Ali authored
When an alloc is stopped, test that we don't update the job found in alloc with new job that is no longer relevent for this alloc.
-
Mahmood Ali authored
-
Buck Doyle authored
It would be preferable to only generate these for UI PRs but Netlify appears to not have that flexibility. I tried setting up manual deployments in a Travis environment but gave up the experiment; it could probably eventually work if deployment failures become a nuisance.
-
Mahmood Ali authored
Only preempt for network when there is a network
-
- 07 Jun, 2019 3 commits
-
-
Mahmood Ali authored
When examining preemption for networks, only consider allocs that have networks. Fixes https://github.com/hashicorp/nomad/issues/5793
-
Mahmood Ali authored
-
Mahmood Ali authored
flaky e2e test
-
- 06 Jun, 2019 6 commits
-
-
Mahmood Ali authored
tests: Migrated allocs aren't lost
-
Mahmood Ali authored
Fix `TestServiceSched_NodeDown` for checking that the migrated allocs are actually marked to be stopped. The boolean logic in test made it skip actually checking client status as long as desired status was stop. Here, we mark some jobs for migration while leaving others as running, and we check that lost flag is only set for non-migrated allocs.
-
Charlie Voiselle authored
Fix a website link under `Runtime Environment`
-
john-lay authored
-
john-lay authored
Under the `Network-related Variables` the `NOMAD_HOST_PORT_<label>` has a incorrect link.
-
Mahmood Ali authored
Proposing new tfvars with additional inline docs
-
- 05 Jun, 2019 12 commits
-
-
Mahmood Ali authored
More test fixes
-
Mahmood Ali authored
set node.StatusUpdatedAt in raft
-
Mahmood Ali authored
Fix restart attempts of `restart` stanza in `delay` mode.
-
Preetha authored
Revert 0.9.2 release super script tags
-
Preetha Appan authored
-
Preetha Appan authored
-
Preetha Appan authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Nomad Release bot authored
-
Mahmood Ali authored
-
Mahmood Ali authored
nomad: disable service+batch preemption by default
-
- 04 Jun, 2019 11 commits
-
-
Mahmood Ali authored
Add Enterprise docs for Preemption
-
Rob Genova authored
-
Michael Schurter authored
Enterprise only. Disable preemption for service and batch jobs by default. Maintain backward compatibility in a x.y.Z release. Consider switching the default for new clusters in the future.
-
Lang Martin authored
-
Mahmood Ali authored
-
Mahmood Ali authored
client config flag to disable remote exec
-
Mahmood Ali authored
-
Lang Martin authored
-
Lang Martin authored
-
Lang Martin authored
-
Lang Martin authored
-