github.com/rohankumardubey/nomad@v0.11.8/e2e/upgrades/README.md (about)

     1  Upgrade Tests
     2  =============
     3  
     4  This directory has a set of scripts for Nomad upgrade testing. The cluster's configs
     5  are also included here. For ease of testing, the configs and node names use names like
     6  `"server1"` and `"client1"` and the data directories are in `"/tmp/server1"`, "/tmp/client1"`, etc
     7  
     8  Start a cluster
     9  ===============
    10  Use `run_cluster.sh` to start a 3 server, 2 client cluster locally.
    11  The script takes the path to the Nomad binary. For example, to run a
    12  0.8.7 Nomad cluster do:
    13  
    14  ```
    15  $ ./run_cluster.sh /path/to/Nomad0.8.7
    16  ```
    17  Run cluster also assumes that `consul` exists in your path and runs a dev agent
    18  
    19  Stop nodes
    20  ==========
    21  Use the `kill_node` script to stop nodes. Note that for quorum, you can only
    22  stop one server at a time. For example, to stop server1 do :
    23  ```
    24  $ ./kill_node.sh server1
    25  ```
    26  This does `kill -9` and is not meant to test graceful shutdowns.
    27  
    28  To stop client1 do :
    29  ```
    30  $ ./kill_node.sh client1
    31  ```
    32  
    33  Start nodes
    34  ===========
    35  Use the `run_node` script to start nodes. In general, upgrade testing involves
    36  shutting down a node that's running an older version of nomad and starting it
    37  back up with a newer binary. For example, to run Nomad 0.9 as server1 do:
    38  ```
    39  $ ./run_node.sh /path/to/Nomad0.9 server1
    40  ```
    41  This will use the same data directory, and should rejoin the quorum
    42  
    43  Another example - to start client1 do :
    44  ```
    45  $ ./run_node.sh /path/to/Nomad0.9 client1
    46  ```