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.
- 20 Nov, 2018 23 commits
-
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Michael Schurter authored
Co-Authored-By:
nickethier <ncethier@gmail.com>
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
plugins/driver: remove NodeResources from task Resources and use PercentTicks field for docker driver
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
Nick Ethier authored
-
- 19 Nov, 2018 3 commits
-
-
Michael Lange authored
UI: Allocation detail empty state
-
Michael Lange authored
-
Michael Lange authored
UI: Escape hatch links on error pages
-
- 17 Nov, 2018 2 commits
-
-
Omar Khawaja authored
-
Omar Khawaja authored
-
- 16 Nov, 2018 12 commits
-
-
Mahmood Ali authored
Report alloc device statistics in API and CLI
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Michael Schurter authored
client: interpolate driver configurations
-
Preetha authored
-
Preetha authored
Pass service metadata "external-source" for consul UI integration
-
Preetha Appan authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
This change makes few compromises: * Looks up the devices associated with tasks at look up time. Given that `nomad alloc status` is called rarely generally (compared to stats telemetry and general job reporting), it seems fine. However, the lookup overhead grows bounded by number of `tasks x total-host-devices`, which can be significant. * `client.Client` performs the task devices->statistics lookup. It passes self to alloc/task runners so they can look up the device statistics allocated to them. * Currently alloc/task runners are responsible for constructing the entire RPC response for stats * The alternatives for making task runners device statistics aware don't seem appealing (e.g. having task runners contain reference to hostStats) * On the alloc aggregation resource usage, I did a naive merging of task device statistics. * Personally, I question the value of such aggregation, compared to costs of struct duplication and bloating the response - but...
-