f05d4cc93a
Merge pull request #9112 from sahiljambhekar/patch-1
...
Remove Nomad-spark reference from use-cases.mdx
2020-10-16 06:47:43 -05:00
e83b4d470e
Remove Nomad-spark reference from use-cases.mdx
...
Removed ref to [Spark](https://github.com/hashicorp/nomad-spark ) based on
2c6092a2a6
2020-10-16 05:41:49 -04:00
4c04b40c62
Merge pull request #9108 from hashicorp/rm-special-node-drain-event
...
remove special node drain event type
2020-10-15 17:30:53 -04:00
70a0253f0d
Update loading spinner to be logo-based ( #9106 )
...
Thanks to @mikehobi, whose work here this is adapted from:
https://icons8.com/cssload/en/3d-loaders
2020-10-15 16:05:58 -05:00
a5b5681248
Use GOPATH/src explicitly in proto build target
...
-I ../../.. is meant to navigate from `GOPATH/src/github.com/hashicorp/nomad` to `GOPATH/src`
This is fine but it assumes a few things about how the dev has setup nomad, which is also fine if that is the expected dev environment, however the `../../..` is not as explicit as "GOPATH/src" and it would also enable a few more scenarios so it seems strictly better to me.
Random example: nomad is a subrepo of ours, but with this change we can symlink from GOPATH/src/github.com/hashicorp/nomad and `make proto` will work.
2020-10-15 21:05:27 +00:00
ae75f192a8
Merge pull request #9107 from hashicorp/event-cfg-positive
...
event buffer size and durable count must be non negative
2020-10-15 16:50:54 -04:00
c57e760933
remove special node drain event type
...
rely on standardized events instead of special node drain event
2020-10-15 16:44:36 -04:00
fba0d6dc6a
event buffer size and durable count must be non negative
2020-10-15 16:34:33 -04:00
175dbaf380
Set env var ( #9103 )
2020-10-15 16:13:49 -04:00
4903e5b114
Consul with CNI and host_network addresses ( #9095 )
...
* consul: advertise cni and multi host interface addresses
* structs: add service/check address_mode validation
* ar/groupservices: fetch networkstatus at hook runtime
* ar/groupservice: nil check network status getter before calling
* consul: comment network status can be nil
2020-10-15 15:32:21 -04:00
3917695602
Changelog entry for topo viz
2020-10-15 12:11:16 -07:00
eff5f6949c
changelog entry for Docker config image_delay fix ( #9104 )
2020-10-15 15:09:34 -04:00
12cae40388
Merge pull request #9077 from hashicorp/f-ui/topo-viz
...
UI: Topology Visualization
2020-10-15 11:58:10 -07:00
5c34e94529
Typo
2020-10-15 11:45:59 -07:00
329fecac6d
Work around Safari's lack of text transform support
2020-10-15 11:45:59 -07:00
2309baf080
Factor out the common sum aggregator used in the topology controller
2020-10-15 11:45:59 -07:00
f3300bcbf0
Remove the scenarios I didn't need/didn't get to
2020-10-15 11:45:59 -07:00
56bf526778
Describe the glimmer-factory better including the motive
2020-10-15 11:45:59 -07:00
41df088abe
Reset the standard environment values
2020-10-15 11:45:59 -07:00
649873745f
Treat legend term pairs as single wrapping elements
2020-10-15 10:30:34 -07:00
11580c518d
Update HSM version w/ waypoint ( #9102 )
2020-10-15 11:59:15 -05:00
f9e659164f
docker: image_delay default missing without gc stanza ( #9101 )
...
In the Docker driver plugin config for garbage collection, the `image_delay`
field was missing from the default we set if the entire `gc` stanza is
missing. This results in a default of 0s and immediate GC of Docker images.
Expanded docker gc config test fields.
2020-10-15 12:36:01 -04:00
ea55c497b7
Merge pull request #9094 from hashicorp/f-1.0
...
s/0.13/1.0/g
2020-10-15 08:53:33 -07:00
90a0b5e558
vendor: update go-getter and x/net ( #9099 )
...
Update go-getter to the latest release now that hashicorp/go-getter#256 is merged.
Also, pick up a xz CVE fix that go-getter merged in hashicorp/go-getter#279 .
2020-10-15 10:24:24 -04:00
13218dc345
Enforce bounds on MaxQueryTime ( #9064 )
...
The MaxQueryTime value used in QueryOptions.HasTimedOut() can be set to
an invalid value that would throw off how RPC requests are retried.
This fix uses the same logic that enforces the MaxQueryTime bounds in the
blockingRPC() call.
2020-10-15 08:43:06 -04:00
97510a8397
Some light topology acceptance tests
2020-10-15 03:06:51 -07:00
a2b57c15eb
Unit and integration tests for TopoViz component
2020-10-15 02:54:16 -07:00
c8ea019629
Test coverage for TopoViz::Datacenter
2020-10-15 02:54:16 -07:00
8b96667a61
Remove temp reloading of nodes in the TopoViz component
2020-10-15 02:54:16 -07:00
4f537c8511
Update scenarios to use new resources code
2020-10-15 02:54:16 -07:00
9fc33a1f9b
Adjust topo viz controller to new resource code
2020-10-15 02:54:16 -07:00
f918987d51
Unit test for for GiB in format-bytes
2020-10-15 02:54:16 -07:00
3c39895168
Update topo viz code to use new alloc/node resources pattern
2020-10-15 02:54:16 -07:00
64fc738733
Migrate to the new resources properties for allocs and nodes
2020-10-15 02:54:16 -07:00
b2b7d5e19e
Test coverage for TopoViz::Node
2020-10-15 02:54:16 -07:00
78b1efc531
FlexMasonry integration tests
2020-10-15 02:54:15 -07:00
e21a2a03b2
More information about clients in the info panel
2020-10-15 02:54:15 -07:00
ba8675ae87
Filter total alloc count by only scheduled allocs
2020-10-15 02:54:15 -07:00
d9ac6a63c6
Add icons to denote draining or ineligibility of clients
2020-10-15 02:54:15 -07:00
7477f32012
Label empty clients in the topo viz chart
2020-10-15 02:54:15 -07:00
f3aed88a10
Improved curves for allocation associations
2020-10-15 02:54:15 -07:00
ef12488d1c
Fix a re-render bug with flexmasonry
2020-10-15 02:54:15 -07:00
066502d408
Make the topo viz denser when there are >50 nodes
...
By hiding node details and making nodes interactive instead, we can pack
more allocations on a screen.
2020-10-15 02:54:15 -07:00
6e55d8a6eb
Conditionally use the FlexMasonry layout for datacenters within TopoViz
2020-10-15 02:54:15 -07:00
1602d72789
Apply FlexMasonry to the TopoViz component
2020-10-15 02:54:15 -07:00
f27895c4c8
New FlexMasonry component implements a masonry layout using flexbox
2020-10-15 02:54:15 -07:00
d9083fdde6
Second attempt at a masonry layout
2020-10-15 02:54:15 -07:00
99746a24ac
A better loading screen for the topo viz while nodes load
2020-10-15 02:54:14 -07:00
6d99f96425
Connect the memory and cpu rectangles
2020-10-15 02:54:14 -07:00
0ab6b31cab
Refactor topo viz to do as much computation upfront & use faster data structures
...
Now all data loading happens in the TopoViz component as well as
computation of resource proportions.
Allocation selection state is also managed centrally uses a dedicated
structure indexed by group key (job id and task group name). This way
allocations don't need to be scanned at the node level, which is O(n) at
the best (assuming no ember overhead on recomputes).
2020-10-15 02:54:14 -07:00
Mahmood Ali