github.com/mattyr/nomad@v0.3.3-0.20160919021406-3485a065154a/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.4.0
    19  
    20  Nomad 0.4.0 has backward incompatible changes in the logic for Consul
    21  deregistration.  When a Task which was started by Nomad 0.3.X is uncleanly shut
    22  down, the Nomad 0.4 Client will no longer clean up any stale services.  If an
    23  in-place upgrade of the Nomad client to 0.4 prevents the Task from gracefully
    24  shutting down and deregistering its Consul-registered services, the Nomad Client
    25  will not clean up the remaining Consul services registered with the 0.3
    26  Executor.
    27  
    28  We recommend draining a node before upgrading to 0.4.0 and then re-enabling the
    29  node once the upgrade is complete.
    30  
    31  
    32  ## Nomad 0.3.1
    33  
    34  Nomad 0.3.1 removes artifact downloading from driver configs and places them as
    35  a first class element of the task. As such, jobs will have to be rewritten in
    36  the proper format and resubmitted to Nomad. Nomad clients will properly
    37  re-attach to existing tasks but job definitions must be updated before they can
    38  be dispatched to clients running 0.3.1.
    39  
    40  ## Nomad 0.3.0
    41  
    42  Nomad 0.3.0 has made several substantial changes to job files included a new
    43  `log` block and variable interpretation syntax (`${var}`), a modified `restart`
    44  policy syntax, and minimum resources for tasks as well as validation. These
    45  changes require a slight change to the default upgrade flow.
    46  
    47  After upgrading the version of the servers, all previously submitted jobs must
    48  be resubmitted with the updated job syntax using a Nomad 0.3.0 binary.
    49  
    50  * All instances of `$var` must be converted to the new syntax of `${var}`
    51  
    52  * All tasks must provide their required resources for CPU, memory and disk as
    53    well as required network usage if ports are required by the task.
    54  
    55  * Restart policies must be updated to indicate whether it is desired for the
    56    task to restart on failure or to fail using `mode = "delay"` or `mode =
    57    "fail"` respectively.
    58  
    59  * Service names that include periods will fail validation. To fix, remove any
    60    periods from the service name before running the job.
    61  
    62  After updating the Servers and job files, Nomad Clients can be upgraded by first
    63  draining the node so no tasks are running on it. This can be verified by running
    64  `nomad node-status <node-id>` and verify there are no tasks in the `running`
    65  state. Once that is done the client can be killed, the `data_dir` should be
    66  deleted and then Nomad 0.3.0 can be launched.