8650429e38
Add network stanza to group
...
Adds a network stanza and additional options to the task group level
in prep for allowing shared networking between tasks of an alloc.
2019-07-31 01:03:12 -04:00
d048029b5a
remove generated code and change version to 0.10.0
2019-07-30 15:56:05 -05:00
e39fb11531
Generate files for 0.9.4 release
2019-07-30 19:05:18 +00:00
6b4c40f5a8
remove generated code
2019-07-23 12:07:49 -05:00
04187c8b86
Generate files for 0.9.4-rc1 release
2019-07-22 21:42:36 +00:00
2157f6ddf1
add formatting for hcl parsing error messages ( #5972 )
2019-07-19 10:04:39 -07:00
f282da4ced
blocked_evals_test disable calls Flush
2019-07-18 10:32:13 -04:00
8f7a20839e
worker comment system -> core
2019-07-18 10:32:13 -04:00
83d20169f6
blocked_evals reset system evals on Flush
2019-07-18 10:32:13 -04:00
6e3425babf
blocked_evals_test Test_UnblockNode
2019-07-18 10:32:12 -04:00
ea275d5ce7
fsm attach UnblockNode on node updates
2019-07-18 10:32:12 -04:00
3bf618f217
blocked_evals system evals indexed by job and node
2019-07-18 10:32:12 -04:00
81b4b6f19b
Merge pull request #5791 from hashicorp/b-plan-snapshotindex
...
nomad: include snapshot index when submitting plans
2019-07-17 09:25:00 -07:00
ad39bcef60
rpc: use tls wrapped connection for streaming rpc
...
This ensures that server-to-server streaming RPC calls use the tls
wrapped connections.
Prior to this, `streamingRpcImpl` function uses tls for setting header
and invoking the rpc method, but returns unwrapped tls connection.
Thus, streaming writes fail with tls errors.
This tls streaming bug existed since 0.8.0[1], but PR #5654[2]
exacerbated it in 0.9.2. Prior to PR #5654 , nomad client used to
shuffle servers at every heartbeat -- `servers.Manager.setServers`[3]
always shuffled servers and was called by heartbeat code[4]. Shuffling
servers meant that a nomad client would heartbeat and establish a
connection against all nomad servers eventually. When handling
streaming RPC calls, nomad servers used these local connection to
communicate directly to the client. The server-to-server forwarding
logic was left mostly unexercised.
PR #5654 means that a nomad client may connect to a single server only
and caused the server-to-server forward streaming RPC code to get
exercised more and unearthed the problem.
[1] https://github.com/hashicorp/nomad/blob/v0.8.0/nomad/rpc.go#L501-L515
[2] https://github.com/hashicorp/nomad/pull/5654
[3] https://github.com/hashicorp/nomad/blob/v0.9.1/client/servers/manager.go#L198-L216
[4] https://github.com/hashicorp/nomad/blob/v0.9.1/client/client.go#L1603
2019-07-12 14:41:44 +08:00
9c9bec62fd
rpc: add positive tests for server streaming RPC
2019-07-12 14:32:52 +08:00
0b97175a16
node_endpoint preserve both messages as rpcs and in raft
2019-07-10 13:56:20 -04:00
ee4848167c
core_sched add compat comment for later removal
2019-07-10 13:56:20 -04:00
c13c97c6c2
structs drop deprecation warning, revert unnecessary comment change
2019-07-10 13:56:20 -04:00
a95225d754
NodeDeregisterBatch -> NodeBatchDeregister match JobBatch pattern
2019-07-10 13:56:20 -04:00
a8e72a5b68
state_store error if called without node_ids
2019-07-10 13:56:20 -04:00
44cbca9b98
fsm new NodeDeregisterBatchRequestType sorted at the end of the case
2019-07-10 13:56:20 -04:00
91e139dcb5
structs NodeDeregisterBatchRequestType must go at the end
2019-07-10 13:56:20 -04:00
1cc6b4062c
fsm label batch_deregister_node metrics explicitly
...
Co-Authored-By: Mahmood Ali <mahmood@notnoop.com>
2019-07-10 13:56:20 -04:00
ad3549f906
core_sched use the new rpc names
2019-07-10 13:56:20 -04:00
ce0f03651a
fsm support new NodeDeregisterBatchRequest
2019-07-10 13:56:20 -04:00
fa5649998e
node endpoint support new NodeDeregisterBatchRequest
2019-07-10 13:56:19 -04:00
683ab8d1d2
structs add NodeDeregisterBatchRequest
2019-07-10 13:56:19 -04:00
82349aba5d
node_endpoint argument setup
2019-07-10 13:56:19 -04:00
6dbf5d7d13
fsm return an error on both NodeDeregisterRequest fields set
2019-07-10 13:56:19 -04:00
fbc78ba96c
fsm variable names for consistency
2019-07-10 13:56:19 -04:00
09fd05bd8f
node_endpoint raft store then shutdown, test deprecation
2019-07-10 13:56:19 -04:00
4610c70777
util simplify partitionAll
2019-07-10 13:56:19 -04:00
d22d9fb5b2
core_sched check ServersMeetMinimumVersion
2019-07-10 13:56:19 -04:00
3bf41211fb
fsm honor new and old style NodeDeregisterRequests
2019-07-10 13:56:19 -04:00
3fb82e83a5
structs add back NodeDeregisterRequest.NodeID, compatibility
2019-07-10 13:56:19 -04:00
a4472e3d34
core_sched check ServersMeetMinimumVersion, send old node deregister
2019-07-10 13:56:19 -04:00
8e53c105fc
state_store just one index update, test deletion
2019-07-10 13:56:19 -04:00
3e2d1f0338
node_endpoint improve error messages
2019-07-10 13:56:19 -04:00
5a6a947e98
state_store improve error messages
2019-07-10 13:56:19 -04:00
fd14cedf95
drainer watch_nodes_test batch of 1
2019-07-10 13:56:19 -04:00
b176066d42
node_endpoint deregister the batch of nodes
2019-07-10 13:56:19 -04:00
a97407e030
fsm NodeDeregisterRequest is now a batch
2019-07-10 13:56:19 -04:00
d5ff2834ca
core_sched batch node deregistration requests
2019-07-10 13:56:19 -04:00
10848841be
util partitionAll for paging
2019-07-10 13:56:19 -04:00
be2d6853cb
state_store DeleteNode operates on a batch of ids
2019-07-10 13:56:19 -04:00
77cf037bff
struct NodeDeregisterRequest has a batch of NodeIDs
2019-07-10 13:56:19 -04:00
3cb798235d
Missed one revert of backwards compatibility for node drain
2019-07-01 16:46:05 -05:00
aa2b4b4e00
Undo removal of node drain compat changes
...
Decided to remove that in 0.10
2019-07-01 15:12:01 -05:00
3484f18984
Fix more tests
2019-06-26 16:30:53 -05:00
ff1b80dba6
Fix node drain test
2019-06-26 16:12:07 -05:00
Nick Ethier