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.
- 18 Nov, 2017 1 commit
-
-
Preetha authored
-
- 17 Nov, 2017 11 commits
-
-
Preetha Appan authored
-
Preetha authored
-
Preetha authored
Make validate command ignore environment variables in service name
-
Preetha authored
-
Alex Dadgar authored
-
Alex Dadgar authored
-
Alex Dadgar authored
Don't emit metrics for non-running tasks
-
Preetha Appan authored
Change error message to use original name for clarity, rather than the name after substituting env vars with placeholder.
-
Preetha authored
-
Michael Schurter authored
Remove rkt pods when exiting
-
Michael Schurter authored
Fix Docker name conflict bug by updating dockerclient
-
- 16 Nov, 2017 8 commits
-
-
Michael Schurter authored
-
Preetha Appan authored
-
Michael Schurter authored
Fixes #3561
-
Charlie Voiselle authored
Dropped loglevel for AWS fingerprinter env read misses to DEBUG
-
Charlie Voiselle authored
-
Alex Dadgar authored
-
Preetha Appan authored
-
Preetha authored
-
- 15 Nov, 2017 16 commits
-
-
Preetha authored
-
Preetha Appan authored
-
Preetha Appan authored
-
Alex Dadgar authored
-
Alex Dadgar authored
Better interface selection heuristic
-
Alex Dadgar authored
-
Alex Dadgar authored
-
Alex Dadgar authored
-
Michael Schurter authored
Handle leader task being dead in RestoreState
-
Michael Schurter authored
Fixes the panic mentioned in https://github.com/hashicorp/nomad/issues/3420#issuecomment-341666932 While a leader task dying serially stops all follower tasks, the synchronizing of state is asynchrnous. Nomad can shutdown before all follower tasks have updated their state to dead thus saving the state necessary to hit this panic: *have a non-terminal alloc with a dead leader.* The actual fix is a simple nil check to not assume non-terminal allocs leader's have a TaskRunner.
-
Charlie Voiselle authored
Certain environments use WARN for serious logging; however, it's very possible to have machines without some of the fingerprinted keys (public-ipv4 and public-hostname specifcally). Setting log level to INFO seems more consistent with this possibility.
-
Preetha Appan authored
-
Preetha Appan authored
-
Preetha authored
Handle edge case when allocation create/modify time difference is les…
-
Preetha Appan authored
-
Chelsea Komlo authored
* Allow server TLS configuration to be reloaded via SIGHUP * dynamic tls reloading for nomad agents * code cleanup and refactoring * ensure keyloader is initialized, add comments * allow downgrading from TLS * initalize keyloader if necessary * integration test for tls reload * fix up test to assert success on reloaded TLS configuration * failure in loading a new TLS config should remain at current Reload only the config if agent is already using TLS * reload agent configuration before specific server/client lock keyloader before loading/caching a new certificate * introduce a get-or-set method for keyloader * fixups from code review * fix up linting errors * fixups from code review * add lock for config updates; improve copy of tls config * GetCertificate only reloads certificates dynamically for the server * config updates/copies should be on agent * improve http integration test * simplify agent reloading storing a local copy of config * reuse the same keyloader when reloading * Test that server and client get reloaded but keep keyloader * Keyloader exposes GetClientCertificate as well for outgoing connections * Fix spelling * correct changelog style
-
- 14 Nov, 2017 4 commits
-
-
Michael Schurter authored
Includes this workaround: https://github.com/fsouza/go-dockerclient/blob/99ba9a9ff48803e4bf801b025c6be7707d83c421/container.go#L634-L637
-
Michael Schurter authored
Fails on Docker 17.09, passes on Docker 17.06 and earlier
-
Alex Dadgar authored
-
Preetha Appan authored
-