2016-02-25 04:11:16 +00:00
|
|
|
---
|
|
|
|
|
layout: "docs"
|
2016-10-09 07:01:59 +00:00
|
|
|
page_title: "Upgrade Guides"
|
2016-02-25 04:11:16 +00:00
|
|
|
sidebar_current: "docs-upgrade-specific"
|
|
|
|
|
description: |-
|
|
|
|
|
Specific versions of Nomad may have additional information about the upgrade
|
|
|
|
|
process beyond the standard flow.
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Upgrading Specific Versions
|
|
|
|
|
|
|
|
|
|
The [upgrading page](/docs/upgrade/index.html) covers the details of doing
|
|
|
|
|
a standard upgrade. However, specific versions of Nomad may have more
|
|
|
|
|
details provided for their upgrades as a result of new features or changed
|
|
|
|
|
behavior. This page is used to document those details separately from the
|
|
|
|
|
standard upgrade flow.
|
|
|
|
|
|
2016-07-06 18:46:41 +00:00
|
|
|
## Nomad 0.4.0
|
|
|
|
|
|
2016-07-06 19:00:06 +00:00
|
|
|
Nomad 0.4.0 has backward incompatible changes in the logic for Consul
|
|
|
|
|
deregistration. When a Task which was started by Nomad 0.3.X is uncleanly shut
|
|
|
|
|
down, the Nomad 0.4 Client will no longer clean up any stale services. If an
|
|
|
|
|
in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
|
|
|
|
|
shutting down and deregistering its Consul-registered services, the Nomad Client
|
|
|
|
|
will not clean up the remaining Consul services registered with the 0.3
|
|
|
|
|
Executor.
|
2016-07-06 18:46:41 +00:00
|
|
|
|
|
|
|
|
We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
|
|
|
|
|
node once the upgrade is complete.
|
|
|
|
|
|
2016-07-06 19:00:06 +00:00
|
|
|
|
2016-03-16 16:56:04 +00:00
|
|
|
## Nomad 0.3.1
|
|
|
|
|
|
|
|
|
|
Nomad 0.3.1 removes artifact downloading from driver configs and places them as
|
|
|
|
|
a first class element of the task. As such, jobs will have to be rewritten in
|
|
|
|
|
the proper format and resubmitted to Nomad. Nomad clients will properly
|
|
|
|
|
re-attach to existing tasks but job definitions must be updated before they can
|
|
|
|
|
be dispatched to clients running 0.3.1.
|
|
|
|
|
|
2016-02-25 04:11:16 +00:00
|
|
|
## Nomad 0.3.0
|
|
|
|
|
|
|
|
|
|
Nomad 0.3.0 has made several substantial changes to job files included a new
|
|
|
|
|
`log` block and variable interpretation syntax (`${var}`), a modified `restart`
|
|
|
|
|
policy syntax, and minimum resources for tasks as well as validation. These
|
|
|
|
|
changes require a slight change to the default upgrade flow.
|
|
|
|
|
|
|
|
|
|
After upgrading the version of the servers, all previously submitted jobs must
|
|
|
|
|
be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
|
|
|
|
|
|
|
|
|
|
* All instances of `$var` must be converted to the new syntax of `${var}`
|
|
|
|
|
|
|
|
|
|
* All tasks must provide their required resources for CPU, memory and disk as
|
|
|
|
|
well as required network usage if ports are required by the task.
|
|
|
|
|
|
|
|
|
|
* Restart policies must be updated to indicate whether it is desired for the
|
|
|
|
|
task to restart on failure or to fail using `mode = "delay"` or `mode =
|
|
|
|
|
"fail"` respectively.
|
|
|
|
|
|
|
|
|
|
* Service names that include periods will fail validation. To fix, remove any
|
|
|
|
|
periods from the service name before running the job.
|
|
|
|
|
|
|
|
|
|
After updating the Servers and job files, Nomad Clients can be upgraded by first
|
|
|
|
|
draining the node so no tasks are running on it. This can be verified by running
|
|
|
|
|
`nomad node-status <node-id>` and verify there are no tasks in the `running`
|
|
|
|
|
state. Once that is done the client can be killed, the `data_dir` should be
|
|
|
|
|
deleted and then Nomad 0.3.0 can be launched.
|
