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.
- 19 Nov, 2019 23 commits
-
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
Noticed that ACL endpoints return 500 status code for user errors. This is confusing and can lead to false monitoring alerts. Here, I introduce a concept of RPCCoded errors to be returned by RPC that signal a code in addition to error message. Codes for now match HTTP codes to ease reasoning. ``` $ nomad acl bootstrap Error bootstrapping: Unexpected response code: 500 (ACL bootstrap already done (reset index: 9)) $ nomad acl bootstrap Error bootstrapping: Unexpected response code: 400 (ACL bootstrap already done (reset index: 9)) ```
-
Michael Schurter authored
Add new "semver" constraint
-
Drew Bailey authored
Removes checking constraints for inplace update
-
Michael Schurter authored
-
Drew Bailey authored
-
Michael Schurter authored
-
Buck Doyle authored
The task is required, not optional, there’s no default as was described.
-
Michael Schurter authored
The existing version constraint uses logic optimized for package managers, not schedulers, when checking prereleases: - 1.3.0-beta1 will *not* satisfy ">= 0.6.1" - 1.7.0-rc1 will *not* satisfy ">= 1.6.0-beta1" This is due to package managers wishing to favor final releases over prereleases. In a scheduler versions more often represent the earliest release all required features/APIs are available in a system. Whether the constraint or the version being evaluated are prereleases has no impact on ordering. This commit adds a new constraint - `semver` - which will use Semver v2.0 ordering when evaluating constraints. Given the above examples: - 1.3.0-beta1 satisfies ">= 0.6.1" using `semver` - 1.7.0-rc1 satisfies ">= 1.6.0-beta1" using `semver` Since existing jobspecs may rely on the old behavior, a new constraint was added and the implicit Consul Connect and Vault constraints were updated to use it.
-
Michael Schurter authored
-
Tim Gross authored
Includes: * baseline Windows AMI * initial pass at Terraform configurations * OpenSSH for Windows Using OpenSSH is a lot nicer for Nomad developers than winrm would be, plus it lets us avoid passing around the Windows password in the clear. Note that now we're copying up all the provisioning scripts and configs as a zipped bundle because TF's file provisioner dies in the middle of pushing up multiple files (whereas `scp -r` works fine). We're also running all the provisioning scripts inside the userdata by polling for the zip file to show up (gross!). This is because `remote-exec` provisioners are failing on Windows with the same symptoms as: https://github.com/hashicorp/terraform/issues/17728 If we can't fix this, it'll prevent us from having multiple Windows clients running until TF supports count interpolation in the `template_file`, which is planned for a later 0.12 release.
-
Tim Gross authored
-
Tim Gross authored
-
Chris Baker authored
SetConfig bug in plugin launcher tool
-
Chris Baker authored
SetConfig, resulting in msgpack decoding errors
-
Lang Martin authored
-
Lang Martin authored
-
Drew Bailey authored
Check for changes to affinity, constraints and spread during update
-
Drew Bailey authored
-
Drew Bailey authored
Fixes documentation inaccuracy for spread stanza placement. Spreads can only exist on the top level job struct or within a group. comment about nil assumption
-
Drew Bailey authored
Adds checks for affinity and constraint changes when determining if we should update inplace. refactor to check all levels at once check for spread changes when checking inplace update
-
- 18 Nov, 2019 1 commit
-
-
Nick Ethier authored
* client: improve group service stanza interpolation and check_restart support Interpolation can now be done on group service stanzas. Note that some task runtime specific information that was previously available when the service was registered poststart of a task is no longer available. The check_restart stanza for checks defined on group services will now properly restart the allocation upon check failures if configured.
-
- 15 Nov, 2019 2 commits
-
-
Luiz Aoqui authored
-
Luiz Aoqui authored
api: add `StartedAt` in `Node.DrainStrategy`
-
- 14 Nov, 2019 10 commits
-
-
Charlie Voiselle authored
Update redirects.txt
-
Charlie Voiselle authored
-
Charlie Voiselle authored
-
Luiz Aoqui authored
-
Drew Bailey authored
Nomad monitor - target remote servers
-
Drew Bailey authored
handle the case where we request a server-id which is this current server update docs, error on node and server id params more accurate names for tests use shared no leader err, formatting rm bad comment remove redundant variable
-
Drew Bailey authored
-
Drew Bailey authored
Allows user to pass in node-id=leader to forward monitor request to remote a remote leader.
-
Drew Bailey authored
updates consul template deps to v0.22.1
-
Drew Bailey authored
pin to v0.22.1
-
- 13 Nov, 2019 4 commits
-
-
Luiz Aoqui authored
-
Drew Bailey authored
nomad: fix dropped test error
-
Lars Lehtonen authored
-
Drew Bailey authored
test rootfallthrough handler
-