f0a86859a0
docker: remove call to global metrics instance
2018-11-19 22:59:17 -05:00
29591a7c2e
task_runner: emit event on task exit with exit result details
2018-11-19 22:59:17 -05:00
8ef73e63ce
docker: moved fingerprint code to it's own file
2018-11-19 22:59:17 -05:00
4be8a86ef9
plugins/driver: remove NodeResources from task Resources and use PercentTicks field for docker driver
2018-11-19 22:59:17 -05:00
ced5d5c445
docker: move recoverable error proto to shared structs
2018-11-19 22:59:16 -05:00
585e468085
docker: implement recover task logic
2018-11-19 22:59:16 -05:00
ee51cb6a93
docker: finished porting tests
2018-11-19 22:59:16 -05:00
69049d37f5
drivers: added NodeResources to drivers.TaskConfig
2018-11-19 22:59:16 -05:00
3d7cdea19e
drivers/docker: more work porting tests from old driver plugin
2018-11-19 22:59:16 -05:00
117b9e6584
drivers: support recoverable errors in the plugin RPC layer
2018-11-19 22:59:15 -05:00
8f8698b3e1
docker: started work on porting docker driver to new plugin framework
2018-11-19 22:59:15 -05:00
9e64ce7d73
docker: properly launch docker logger process
2018-11-19 22:59:12 -05:00
fd35d37f43
Merge pull request #4860 from hashicorp/b-ui-allocation-detail-empty-state
...
UI: Allocation detail empty state
2018-11-19 12:43:39 -08:00
796967c58d
Add an empty state to the allocation detail task list
2018-11-19 12:18:14 -08:00
b252ede5b6
Merge pull request #4850 from hashicorp/f-ui-links-on-error-pages
...
UI: Escape hatch links on error pages
2018-11-19 12:17:36 -08:00
181381f456
change instrumented webserver job file ( #4897 )
2018-11-17 01:10:44 -05:00
ba2514149f
clarification regarding Nomad client generating token vs retrieving ( #4890 )
2018-11-16 19:52:31 -05:00
9479015f51
Merge pull request #4884 from hashicorp/f-alloc-devices-cli
...
Report alloc device statistics in API and CLI
2018-11-16 18:04:54 -05:00
6f9126f475
show Device Stats header in alloc status
2018-11-16 17:34:37 -05:00
00ffd02ced
Show stable order of device attributes
2018-11-16 17:34:37 -05:00
f139234372
address review comments
2018-11-16 17:13:01 -05:00
dac17f5337
Merge pull request #4843 from hashicorp/b-driver-env
...
client: interpolate driver configurations
2018-11-16 12:45:43 -06:00
225f1531cb
Update CHANGELOG.md
2018-11-16 12:31:54 -06:00
5f094633fa
Merge pull request #4889 from hashicorp/f-service-meta
...
Pass service metadata "external-source" for consul UI integration
2018-11-16 12:24:21 -06:00
18708d3f0b
Pass service metadata "external-source" for consul UI integration
2018-11-16 11:28:56 -06:00
33c96a803a
tweak whitespace in device stats output
2018-11-16 10:37:39 -05:00
159b8f866a
Display device stats in `nomad alloc status`
2018-11-16 10:26:32 -05:00
d88a3f8413
Prepare to reuse device resources printing
2018-11-16 10:26:32 -05:00
f72e599ee7
Populate alloc stats API with device stats
...
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 opted to be
consistent in the API.
* With naive concatination, device instances from a single device group used by separate tasks in the alloc, would be aggregated in two separate device group statistics.
2018-11-16 10:26:32 -05:00
7873b212af
Merge pull request #4882 from sportebois/f-update-docs-env-stanza-coercion
...
Change misleading boolean example in env stanza coercion section (#4820 )
2018-11-16 08:00:56 -06:00
0cdb188ae4
tests: fix tests post-rebase
2018-11-15 17:40:56 -08:00
59f106ecee
client/tr: add a bit of context to envbuilder errors
2018-11-15 16:26:25 -08:00
742f8775ba
client: remove old proxy references from comments
2018-11-15 16:26:25 -08:00
2d0b44c3b4
client: test more env key variations
2018-11-15 16:26:25 -08:00
8bcd90d78d
client: add new nested variables to task's hcl ctx
...
The error messages are really bad, but it's extremely difficult to
produce good error messages without the original HCL.
2018-11-15 16:26:25 -08:00
3b8fe566a9
docs: document new interpolation behavior and options
2018-11-15 16:26:25 -08:00
5e51e2c2d5
client: turn env into nested objects for task configs
2018-11-15 16:25:57 -08:00
f8cdd561f0
client: interpolate driver configurations
...
Also add missing SetDriverNetwork calls.
2018-11-15 16:25:57 -08:00
6f3712ed48
gofmt -s -w command/helper_stats_test.go
...
Fixes the static checks build
2018-11-15 14:14:05 -08:00
8bf17fe22d
Merge pull request #4875 from hashicorp/f-constraints
...
scheduler: Make != constraints more flexible
2018-11-15 11:04:21 -08:00
1ec6f551a6
Merge pull request #4879 from hashicorp/f-node-devices-cli
...
Show device stats in nomad CLI
2018-11-15 14:02:22 -05:00
890bde3482
Add changelog entry for != operator
2018-11-15 11:00:32 -08:00
023ef40cd0
docs: Add is_set/is_not_set
2018-11-15 11:00:32 -08:00
9c72dafc95
scheduler: Add is_set/is_not_set constraints
...
This adds constraints for asserting that a given attribute or value
exists, or does not exist. This acts as a companion to =, or !=
operators, e.g:
```hcl
constraint {
attribute = "${attrs.type}"
operator = "!="
value = "database"
}
constraint {
attribute = "${attrs.type}"
operator = "is_set"
}
```
2018-11-15 11:00:32 -08:00
bf494cb86c
Change misleading boolean example in env stanza coercion section
2018-11-15 13:12:58 -05:00
24b37e0aaf
Display StatsObject nested objects as well
2018-11-15 08:09:54 -05:00
ee9353fbd6
Use disk display format for devices
2018-11-14 22:13:23 -05:00
0712be643f
Print verbose device in `nomad node status -stats`
2018-11-14 22:13:23 -05:00
93e8fc53f9
device stats summary in `node status`
...
Sample output with a mock device:
```
Host Resource Utilization
CPU Memory Disk
2651/26400 MHz 9.6 GiB/16 GiB 98 GiB/234 GiB
Device Resource Utilization
nomad/file/mock[README.md] 511 bytes
nomad/file/mock[e2e.go] 239 bytes
nomad/file/mock[e2e_test.go] 128 bytes
Allocations
No allocations placed
```
2018-11-14 22:13:23 -05:00
5e2b31b692
Merge pull request #4872 from hashicorp/f-devices-client-stats
...
Expose Device Stats in Clients API
2018-11-14 21:18:23 -05:00
Nick Ethier