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.
- 03 Apr, 2019 1 commit
-
-
Danielle Lancashire authored
-
- 01 Apr, 2019 2 commits
-
-
Danielle Lancashire authored
This adds a `nomad alloc restart` command and api that allows a job operator with the alloc-lifecycle acl to perform an in-place restart of a Nomad allocation, or a given subtask.
-
Danielle Tomlinson authored
This capability will gate access to features that allow interacting with a running allocation, for example, signalling, stopping, and rescheduling specific allocations.
-
- 28 Mar, 2019 1 commit
-
-
Preetha authored
Use specific url prefix for metrics test
-
- 27 Mar, 2019 2 commits
-
-
Preetha Appan authored
Also changed the output to show client node IP addresses
-
Michael Schurter authored
Fixup mixed tabs in script for Vagrantfile demo
-
- 26 Mar, 2019 3 commits
-
-
Brian Cain authored
This commit replaces a hard tab with two spaces to match the intendation of the rest of the defined script
-
Preetha authored
minor fixes to spread stanza documentation
-
Preetha Appan authored
-
- 25 Mar, 2019 3 commits
-
-
Mahmood Ali authored
-
Michael Schurter authored
tests: port pre-0.9 task env tests
-
Michael Schurter authored
I chose to make them more of integration tests since there's a lot more plumbing involved. The internal implementation details of how we craft task envs can now change and these tests will still properly assert the task runtime environment is setup properly.
-
- 22 Mar, 2019 6 commits
-
-
Mahmood Ali authored
test: properly skip client state in beforeall
-
Mahmood Ali authored
release: skip check step when cutting release
-
Preetha Appan authored
-
Michael Schurter authored
-
Michael Schurter authored
-
Michael Schurter authored
-
- 21 Mar, 2019 13 commits
-
-
Nomad Release bot authored
-
Mahmood Ali authored
Now `prerelease` no longer requires linters
-
Mahmood Ali authored
`make check` runs very intensive linters that slow and seem to behave differently on different machines. Linting is still a part of our CI and we shouldn't be cutting a release when CI isn't green anyway.
-
Mahmood Ali authored
-
Mahmood Ali authored
client/logmon: restart log collection correctly when a task is restarted
-
Mahmood Ali authored
-
Preetha authored
Prometheus metrics for the e2e environment
-
Preetha Appan authored
-
Michael Schurter authored
Test state corruption
-
Michael Schurter authored
-
Michael Schurter authored
The e2e test code is absolutely hideous and leaks processes and files on disk. NomadAgent seems useful, but the clientstate e2e tests are very messy and slow. The last test "Corrupt" is probably the most useful as it explicitly corrupts the state file whereas the other tests attempt to reproduce steps thought to cause corruption in earlier releases of Nomad.
-
Nick Ethier authored
-
Nick Ethier authored
-
- 20 Mar, 2019 9 commits
-
-
Michael Schurter authored
docs: sync systemd unit files; update deploy guide
-
Michael Schurter authored
Point users to security doc instead. Right now it takes a lot of explaining to describe to users exactly how to validate the binary and what the output of the tools used means. For example, this is the output when validating according to the instructions in this guide and the linked doc: ``` vagrant@linux:/tmp$ gpg --verify nomad_0.8.7_SHA256SUMS.sig nomad_0.8.7_SHA256SUMS gpg: Signature made Fri 11 Jan 2019 09:47:56 PM UTC using RSA key ID 348FFC4C gpg: Good signature from "HashiCorp Security <security@hashicorp.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 91A6 E7F8 5D05 C656 30BE F189 5185 2D87 348F FC4C vagrant@linux:/tmp$ shasum -a 256 -c nomad_0.8.7_SHA256SUMS shasum: ./nomad_0.8.7_darwin_amd64.zip: ./nomad_0.8.7_darwin_amd64.zip: FAILED open or read shasum: ./nomad_0.8.7_linux_386.zip: No such file or directory ./nomad_0.8.7_linux_386.zip: FAILED open or read shasum: ./nomad_0.8.7_linux_amd64-lxc.zip: No such file or directory ./nomad_0.8.7_linux_amd64-lxc.zip: FAILED open or read ./nomad_0.8.7_linux_amd64.zip: OK shasum: ./nomad_0.8.7_linux_arm64.zip: No such file or directory ./nomad_0.8.7_linux_arm64.zip: FAILED open or read shasum: ./nomad_0.8.7_linux_arm.zip: No such file or directory ./nomad_0.8.7_linux_arm.zip: FAILED open or read shasum: ./nomad_0.8.7_windows_386.zip: No such file or directory ./nomad_0.8.7_windows_386.zip: FAILED open or read shasum: ./nomad_0.8.7_windows_amd64.zip: No such file or directory ./nomad_0.8.7_windows_amd64.zip: FAILED open or read shasum: WARNING: 7 listed files could not be read ``` There are only two lines that matter in all of that output: ``` ... gpg: Good signature from "HashiCorp Security <security@hashicorp.com>" ... ./nomad_0.8.7_linux_amd64.zip: OK ... ``` I feel like trying to teach users how to use and interpret these tools in our deployment guide may be as likely to reduce confidence as increase it.
-
Mahmood Ali authored
tls_cipher_suites only accept a comma-separated string, as evident in: https://github.com/hashicorp/nomad/blob/0535dfd414214efd14183bf23d1447f679b57af8/nomad/structs/config/tls.go#L61 https://github.com/hashicorp/nomad/blob/d37ed5c193ac8237666b92bd3f3b0b7e0a8ebfd5/helper/tlsutil/config.go#L405
-
Mahmood Ali authored
-
Mahmood Ali authored
Co-Authored-By:
schmichael <michael.schurter@gmail.com>
-
Michael Schurter authored
docs: add #5381 to changelog
-
Nick Ethier authored
-
Michael Schurter authored
-
Mahmood Ali authored
server: inconsistent receiver notation corrected
-