github.com/dkerwin/nomad@v0.3.3-0.20160525181927-74554135514b/website/source/docs/upgrade/upgrade-specific.html.md (about) 1 --- 2 layout: "docs" 3 page_title: "Upgrading Specific Versions" 4 sidebar_current: "docs-upgrade-specific" 5 description: |- 6 Specific versions of Nomad may have additional information about the upgrade 7 process beyond the standard flow. 8 --- 9 10 # Upgrading Specific Versions 11 12 The [upgrading page](/docs/upgrade/index.html) covers the details of doing 13 a standard upgrade. However, specific versions of Nomad may have more 14 details provided for their upgrades as a result of new features or changed 15 behavior. This page is used to document those details separately from the 16 standard upgrade flow. 17 18 ## Nomad 0.3.1 19 20 Nomad 0.3.1 removes artifact downloading from driver configs and places them as 21 a first class element of the task. As such, jobs will have to be rewritten in 22 the proper format and resubmitted to Nomad. Nomad clients will properly 23 re-attach to existing tasks but job definitions must be updated before they can 24 be dispatched to clients running 0.3.1. 25 26 ## Nomad 0.3.0 27 28 Nomad 0.3.0 has made several substantial changes to job files included a new 29 `log` block and variable interpretation syntax (`${var}`), a modified `restart` 30 policy syntax, and minimum resources for tasks as well as validation. These 31 changes require a slight change to the default upgrade flow. 32 33 After upgrading the version of the servers, all previously submitted jobs must 34 be resubmitted with the updated job syntax using a Nomad 0.3.0 binary. 35 36 * All instances of `$var` must be converted to the new syntax of `${var}` 37 38 * All tasks must provide their required resources for CPU, memory and disk as 39 well as required network usage if ports are required by the task. 40 41 * Restart policies must be updated to indicate whether it is desired for the 42 task to restart on failure or to fail using `mode = "delay"` or `mode = 43 "fail"` respectively. 44 45 * Service names that include periods will fail validation. To fix, remove any 46 periods from the service name before running the job. 47 48 After updating the Servers and job files, Nomad Clients can be upgraded by first 49 draining the node so no tasks are running on it. This can be verified by running 50 `nomad node-status <node-id>` and verify there are no tasks in the `running` 51 state. Once that is done the client can be killed, the `data_dir` should be 52 deleted and then Nomad 0.3.0 can be launched.