a0195d8d41
remove comment
2018-03-22 14:49:08 -07:00
7192498ea9
Merge pull request #4027 from hashicorp/f-common
...
New Command Line Groupings
2018-03-22 13:57:37 -07:00
34211f00a7
Allow separate enterprise config overlay
2018-03-22 13:53:08 -07:00
17fc9a6283
Fix old references
2018-03-22 13:39:18 -07:00
ee463f1a28
Grouped commands help description
2018-03-21 20:27:32 -07:00
742382146e
color
2018-03-21 20:27:32 -07:00
aa85b61fc8
Deprecated commands
2018-03-21 20:27:32 -07:00
de08c1891a
aliases
2018-03-21 20:27:32 -07:00
d2af5d22e4
rename files
2018-03-21 20:27:32 -07:00
6faa136e03
common commands
2018-03-21 20:27:32 -07:00
b5bee9e06b
use subcommands
2018-03-21 20:27:32 -07:00
0e0b04afec
test: fix by using mock.BatchJob
2018-03-21 16:51:45 -07:00
39cef16c73
test: don't call t.Fatal from within a goroutine
2018-03-21 16:51:45 -07:00
cb61a4bdc7
Fix linting errors
2018-03-21 16:51:45 -07:00
be7c759867
Improve drain log messages
...
Also delay "node complete" after the node has been marked complete to
capture a few more alloc events. There are other ways to implement this
that could trade off correctness for responsiveness as technically a
node is considered drained when all of its allocs have been marked to
stop and not when they've actually stopped (which may not happen for a
long time).
2018-03-21 16:51:45 -07:00
5eebd53223
Monitor node drains until completion in CLI
...
allow -detach like other commands
2018-03-21 16:51:45 -07:00
3907766b6d
Fix node eligibility test
2018-03-21 16:51:45 -07:00
7b2bad8c5e
Toggle Drain allows resetting eligibility
...
This PR allows marking a node as eligible for scheduling while toggling
drain. By default the `nomad node drain -disable` commmand will mark it
as eligible but the drainer will maintain in-eligibility.
2018-03-21 16:51:44 -07:00
02019f216a
Correct defaulting
2018-03-21 16:51:44 -07:00
78c7c36e65
code review
2018-03-21 16:51:44 -07:00
ac4975cef4
Small refactor and cleanups
2018-03-21 16:51:44 -07:00
d47c68f764
Add eligibility to node view
2018-03-21 16:51:44 -07:00
c0f808205e
node eligibility command
2018-03-21 16:51:44 -07:00
8289cc3c6f
HTTP and API
2018-03-21 16:51:44 -07:00
f44fbac66a
flag comment
2018-03-21 16:51:44 -07:00
b3d2346419
Upgrade path
2018-03-21 16:51:43 -07:00
010228577e
Drain cli, api, http
2018-03-21 16:51:43 -07:00
01898b2c25
Merge pull request #4007 from hashicorp/f-show-rescheduling-cli-job-status
...
Show a section on upcoming delayed evaluations when applicable
2018-03-21 14:37:38 -05:00
ba217e5224
More code review feedback
2018-03-21 14:28:14 -05:00
496ff26d32
Fix test
2018-03-21 09:24:28 -05:00
26b6e70d13
Addressed code review feedback
2018-03-21 09:15:29 -05:00
70c370c6fe
Merge pull request #4003 from jrasell/f_gh_3988
...
Allow Nomads Consul health check names to be configurable.
2018-03-20 16:44:08 -07:00
30fff15de7
Show reschedule policy in addition to when the eval will get rescheduled
2018-03-20 13:34:29 -05:00
121c3bc997
Update Consul check params from using health-check to check.
2018-03-20 16:03:58 +01:00
ec13089be9
Unit test and linting fix
2018-03-19 22:11:07 -05:00
31a3c81c3b
Show a section on upcoming delayed evaluations when applicable
2018-03-19 21:42:37 -05:00
5cbcd6f8a2
Merge pull request #4006 from hashicorp/b-alloc-status-cli-hide-unlimited-attempts
...
Hide the number of reschedule attempts for unlimited rescheduling
2018-03-19 18:25:20 -05:00
96b49cb491
Hide the number of reschedule attempts for unlimited rescheduling
2018-03-19 18:06:15 -05:00
86ccdb9115
Fix generating static assets
...
Broke due to a change in go-bindata-assetfs
2018-03-19 15:52:38 -07:00
15afef9b77
Allow Nomads Consul health checks to be configurable.
...
This change allows the client HTTP and the server HTTP, Serf and
RPC health check names within Consul to be configurable with the
defaults as previous. The configuration can be done via either a
config file or using CLI flags.
Closes #3988
2018-03-19 19:37:56 +01:00
6df57c177c
Merge pull request #4002 from hashicorp/b-reschedule-systemjob-panic
...
Fix incorrect initialization of reschedule policy for system jobs.
2018-03-19 13:06:55 -05:00
161bc66355
Fix incorrect initialization of reschedule policy for system jobs.
2018-03-19 12:16:13 -05:00
9e05c9a50e
Merge pull request #3997 from hashicorp/b-serf-addr
...
RPC Advertise used exclusively for Clients
2018-03-19 09:30:20 -07:00
9ef23ff277
enable server in test
2018-03-16 16:52:37 -07:00
b8607ad6d6
Heartbeat uses client rpc advertise and server defaults server rpc advertise addr
2018-03-16 16:47:08 -07:00
52b7fb5361
Separate client and server rpc advertise addresses
2018-03-16 16:47:08 -07:00
86f562be3a
Remove unnecessary conversions
2018-03-16 16:32:59 -07:00
c3e8f6319c
gofmt -s (simplify) files
2018-03-16 16:31:16 -07:00
1044bc0feb
Merge pull request #3984 from hashicorp/f-loosen-consul-skipverify
...
Replace Consul TLSSkipVerify handling
2018-03-16 11:21:28 -07:00
0971114f0c
Replace Consul TLSSkipVerify handling
...
Instead of checking Consul's version on startup to see if it supports
TLSSkipVerify, assume that it does and only log in the job service
handler if we discover Consul does not support TLSSkipVerify.
The old code would break TLSSkipVerify support if Nomad started before
Consul (such as on system boot) as TLSSkipVerify would default to false
if Consul wasn't running. Since TLSSkipVerify has been supported since
Consul 0.7.2, it's safe to relax our handling.
2018-03-14 17:43:06 -07:00
Alex Dadgar