95a9a5da71
Merge pull request #2787 from hashicorp/f-docker-test-mac
...
Test #2652 - Docker MAC Address option
2017-07-07 16:22:10 -07:00
4be4df21c9
Merge pull request #2797 from hashicorp/f-2785-docker-bridge-ip
...
Add driver.docker.bridge_ip node attribute
2017-07-07 16:20:20 -07:00
94389c3ecc
Remove debug logging
2017-07-07 16:19:42 -07:00
d9b8fd126f
When restoring periodic jobs, take into consideration launch time zone
...
Fixes https://github.com/hashicorp/nomad/issues/2721
2017-07-07 16:18:56 -07:00
773125e606
Merge pull request #2805 from hashicorp/b-2722-invalid-type
...
Validate job type
2017-07-07 16:18:37 -07:00
e2a79d330c
Prevent port conflicts
...
Validate that no two tasks in the same task group can reserve the same
static port.
2017-07-07 16:17:05 -07:00
5086f1c868
Document new upgrade stanza
...
This PR adds documentation and examples for the new update stanza.
2017-07-07 16:04:35 -07:00
5e3e3818db
Merge pull request #2804 from hashicorp/b-2802-docker-panic
...
Don't panic in container list/remove/inspect race
2017-07-07 15:35:51 -07:00
517c799439
Validate job type
...
Fixes #2722
2017-07-07 15:34:26 -07:00
67a7b0eac9
Don't panic in container list/remove/inspect race
...
Fixes #2802
While it's hard to reproduce the theoretical race is:
1. This goroutine calls ListContainers()
2. Another goroutine removes a container X
3. This goroutine attempts to InspectContainer(X)
However, this bug could be hit in the much simpler case of
InspectContainer() timing out.
In those cases an error is returned and the old code attempted to wrap
the error with the now-nil container.ID. Storing the container ID fixes
that panic.
2017-07-07 15:10:59 -07:00
e98e599419
Merge pull request #2801 from hashicorp/f-update-go-winio
...
Update go-winio to get some fixes
2017-07-07 15:04:02 -07:00
fe69901fb9
Merge pull request #2803 from hashicorp/f-update-ct
...
Update consul-template
2017-07-07 15:03:46 -07:00
9235743cac
changelog
2017-07-07 15:03:33 -07:00
27d142433c
Merge pull request #2799 from hashicorp/f-deployment
...
Introduce deployments to make rolling updates based on allocation health
2017-07-07 14:58:26 -07:00
bf97a2455c
Vet and small improvement on watcher failure detection
2017-07-07 14:53:01 -07:00
eee850b1e6
Update consul-template
2017-07-07 14:42:31 -07:00
f9c52676e0
Update go-winio to get some fixes
...
* Microsoft/go-winio#53
* Microsoft/go-winio#54
2017-07-07 14:33:47 -07:00
45712c6ca3
test fixes
2017-07-07 14:11:27 -07:00
717b57c736
rewording and minor fixes to various pages
2017-07-07 13:20:40 -07:00
db93d51530
vendor
2017-07-07 12:18:14 -07:00
bf2dafb8e9
check id method name changed
2017-07-07 12:15:09 -07:00
20005f925a
Rolling node drains using max_parallel and stagger
...
This PR adds rolling node drains done at max_parallel and stagger of the
update spec. It brings it inline with old behavior.
2017-07-07 12:12:48 -07:00
73ec282529
an user -> a user
2017-07-07 12:12:48 -07:00
3a29b38108
Status description shows requiring promotion
2017-07-07 12:12:48 -07:00
461e36584e
events
2017-07-07 12:12:48 -07:00
ade9a7c768
@jippi Changed my mind! Good suggestion
2017-07-07 12:12:48 -07:00
e6f5e3f301
deployment status in job status view
2017-07-07 12:12:48 -07:00
770af68119
alloc-status
2017-07-07 12:12:48 -07:00
40b04a5ea9
alloc-list shows version
2017-07-07 12:12:48 -07:00
08bf34f9a3
Fix JobModifyIndex changing when job is marked stable
2017-07-07 12:12:48 -07:00
7867f2cdb8
deployment status indicates whether canaries were promoted
2017-07-07 12:12:48 -07:00
4e014e36f7
Fix broken things on deployment promote
2017-07-07 12:12:48 -07:00
9f016606aa
Fix some tests, eval monitor shows deployment id and deployment cancels based on version
2017-07-07 12:12:48 -07:00
398c4a6be7
Vendor columnize
2017-07-07 12:11:39 -07:00
91451228eb
Fix some commands test
2017-07-07 12:11:39 -07:00
1cb877699a
Disallow update stanza on batch jobs
...
This PR:
* disallows update stanzas on batch jobs
* undeprecates the stagger field
* changes the way warnings are returned
2017-07-07 12:11:39 -07:00
de54ffd1f6
Deployment from inplace updates tracks placed properly.
2017-07-07 12:10:04 -07:00
867012b9cb
add to docs
2017-07-07 12:10:04 -07:00
bfc22346d5
Return the reverted job version
2017-07-07 12:10:04 -07:00
371b2bdacc
add reverted job version to deployment update response
2017-07-07 12:10:04 -07:00
a7fdc74bd4
feedback
2017-07-07 12:10:04 -07:00
d4bdc866f0
HTTP API docs for job
2017-07-07 12:10:04 -07:00
5457bb7962
Job stability
2017-07-07 12:10:04 -07:00
d07a5a2008
Complete deployments mark jobs as stable
...
This PR allows jobs to be marked as stable automatically by a successful
deployment.
2017-07-07 12:10:04 -07:00
9aa1f2fea2
Respond to comments
2017-07-07 12:10:04 -07:00
454083ba1b
Remove canary
2017-07-07 12:10:04 -07:00
952a22fb02
plan apply tests
2017-07-07 12:10:04 -07:00
d352d85bb9
Test scheduler's handling of canaries/inplace updates
2017-07-07 12:10:04 -07:00
83c60483f2
Test marking as complete
2017-07-07 12:10:04 -07:00
477c713df5
Plan apply handles canaries and success is set via update
2017-07-07 12:10:04 -07:00
Michael Schurter