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.
- 30 Apr, 2020 3 commits
-
-
Michael Lange authored
-
Michael Lange authored
Typically a failover means that the client can't be reached. However, if the client does eventually return after the timeout period, the log will stream indefinitely. This fixes that using an API that wasn't broadly available at the time this was first written.
-
Michael Lange authored
Now options can be provided without also having to remember to pass credentials. This is convenient for abort controller signals.
-
- 29 Apr, 2020 10 commits
-
-
Seth Hoenig authored
env_aws: use best-effort lookup table for CPU performance in EC2
-
Seth Hoenig authored
-
Seth Hoenig authored
Co-Authored-By:
Mahmood Ali <mahmood@hashicorp.com>
-
Seth Hoenig authored
Co-Authored-By:
Mahmood Ali <mahmood@hashicorp.com>
-
Tim Gross authored
The `CSIVolumeClaim` fields were added after 0.11.1, so claims made before that may be missing the value. Repair this when we read the volume out of the state store. The `NodeID` field was added after 0.11.0, so we need to ensure it's been populated during upgrades from 0.11.0.
-
Buck Doyle authored
This closes #7814. It makes URL-generation more central and changes the exec URL to include job id instead of name.
-
Mahmood Ali authored
Vendor: update fsouza/go-dockerclient to v1.6.5
-
ccn authored
-
ccn authored
-
Seth Hoenig authored
Fixes #7681 The current behavior of the CPU fingerprinter in AWS is that it reads the **current** speed from `/proc/cpuinfo` (`CPU MHz` field). This is because the max CPU frequency is not available by reading anything on the EC2 instance itself. Normally on Linux one would look at e.g. `sys/devices/system/cpu/cpuN/cpufreq/cpuinfo_max_freq` or perhaps parse the values from the `CPU max MHz` field in `/proc/cpuinfo`, but those values are not available. Furthermore, no metadata about the CPU is made available in the EC2 metadata service. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-categories.html Since `go-psutil` cannot determine the max CPU speed it defaults to the current CPU speed, which could be basically any number between 0 and the true max. This is particularly bad on large, powerful reserved instances which often idle at ~800 MHz while Nomad does its fingerprinting (typically IO bound), which Nomad then uses as the max, which results in severe loss of available resources. Since the CPU specification is unavailable programmatically (at least not without sudo) use a best-effort lookup table. This table was generated by going through every instance type in AWS documentation and copy-pasting the numbers. https://aws.amazon.com/ec2/instance-types/ This approach obviously is not ideal as future instance types will need to be added as they are introduced to AWS. However, using the table should only be an improvement over the status quo since right now Nomad miscalculates available CPU resources on all instance types.
-
- 28 Apr, 2020 9 commits
-
-
Mahmood Ali authored
Harmonize go-msgpack/codec/codecgen
-
Mahmood Ali authored
Use v1.1.5 of go-msgpack/codec/codecgen, so go-msgpack codecgen matches the library version. We branched off earlier to pick up https://github.com/hashicorp/go-msgpack/commit/f51b5189210768cf0d476580cf287620374d4f02 , but apparently that's not needed as we could customize the package via `-c` argument.
-
Tim Gross authored
-
Lang Martin authored
-
Mahmood Ali authored
structs: give codecgen import
-
Buck Doyle authored
-
Chris Baker authored
fix issues in Job.ScaleStatus
-
Yoan Blanc authored
Signed-off-by:
Yoan Blanc <yoan@dosimple.ch>
-
Nick Ethier authored
-
- 27 Apr, 2020 7 commits
-
-
Chris Baker authored
-
Chris Baker authored
allocations, ignoring canaries
-
Charlie Voiselle authored
-
Charlie Voiselle authored
[docs] Update credential helper example in docker.mdx
-
Mahmood Ali authored
api: fix some documentation typos
-
Mahmood Ali authored
Vendor: update armon/go-metrics to v0.3.3
-
Yoan Blanc authored
Signed-off-by:
Yoan Blanc <yoan@dosimple.ch>
-
- 26 Apr, 2020 1 commit
-
-
Mahmood Ali authored
To pick up a lock contention fix in prometheus sink: https://github.com/armon/go-metrics/pull/107 .
-
- 25 Apr, 2020 2 commits
-
-
Charlie Voiselle authored
-
Charlie Voiselle authored
Disable dangling container GC for demo
-
- 24 Apr, 2020 2 commits
-
-
Seth Hoenig authored
demo: create a demo service for grpc healthchecks
-
Seth Hoenig authored
Examples for HTTP based task-group service healthchecks are covered by the `countdash` demo, but gRPC checks currently have no runnable examples. This PR adds a trivial gRPC enabled application that provides a Service implementing the standard gRPC healthcheck interface.
-
- 23 Apr, 2020 6 commits
-
-
Tim Gross authored
Running `make dev` runs `hclfmt`, but this isn't checked as part of CI. That makes it possible to merge un-formatted HCL and Nomad jobspecs that later will make for dirty git staging areas when developers pull master. This changeset adds HCL linting to the `make check` target.
-
Charlie Voiselle authored
-
Tim Gross authored
Adds a `CSIVolumeClaim` type to be tracked as current and past claims on a volume. Allows for a client RPC failure during node or controller detachment without having to keep the allocation around after the first garbage collection eval. This changeset lays groundwork for moving the actual detachment RPCs into a volume watching loop outside the GC eval.
-
Tim Gross authored
-
Chris Baker authored
parsing should error if scaling block includes multiple policy blocks
-
Chris Baker authored
-