This project is mirrored from https://gitee.com/mirrors/nomad.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 04 Dec, 2021 1 commit
    • Michael Schurter's avatar
      core: remove all traces of unused protocol version · b0edca94
      Michael Schurter authored
      Nomad inherited protocol version numbering configuration from Consul and
      Serf, but unlike those projects Nomad has never used it. Nomad's
      `protocol_version` has always been `1`.
      
      While the code is effectively unused and therefore poses no runtime
      risks to leave, I felt like removing it was best because:
      
      1. Nomad's RPC subsystem has been able to evolve extensively without
         needing to increment the version number.
      2. Nomad's HTTP API has evolved extensively without increment
         `API{Major,Minor}Version`. If we want to version the HTTP API in the
         future, I doubt this is the mechanism we would choose.
      3. The presence of the `server.protocol_version` configuration
         parameter is confusing since `server.raft_protocol` *is* an important
         parameter for operators to consider. Even more confusing is that
         there is a distinct Serf protocol version which is included in `nomad
         server members` output under the heading `Protocol`. `raft_protocol`
         is the *only* protocol version relevant to Nomad developers and
         operators. The other protocol versions are either deadcode or have
         never changed (Serf).
      4. If we were to need to version the RPC, HTTP API, or Serf protocols, I
         don't think these configuration parameters and variables are the best
         choice. If we come to that point we should choose a versioning scheme
         based on the use case and modern best practices -- not this 6+ year
         old dead code.
      b0edca94
  2. 01 Dec, 2021 2 commits
  3. 30 Nov, 2021 4 commits
  4. 29 Nov, 2021 3 commits
  5. 26 Nov, 2021 2 commits
  6. 25 Nov, 2021 2 commits
  7. 24 Nov, 2021 18 commits
  8. 23 Nov, 2021 3 commits
    • Luiz Aoqui's avatar
    • James Rasell's avatar
      Merge pull request #11535 from hashicorp/docs-vault-token · 416b14ec
      James Rasell authored
      docs: clarify vault.token only required on servers
      416b14ec
    • James Rasell's avatar
      core: allow setting and propagation of eval priority on job de/registration (#11532) · 80dcae72
      James Rasell authored
      This change modifies the Nomad job register and deregister RPCs to
      accept an updated option set which includes eval priority. This
      param is optional and override the use of the job priority to set
      the eval priority.
      
      In order to ensure all evaluations as a result of the request use
      the same eval priority, the priority is shared to the
      allocReconciler and deploymentWatcher. This creates a new
      distinction between eval priority and job priority.
      
      The Nomad agent HTTP API has been modified to allow setting the
      eval priority on job update and delete. To keep consistency with
      the current v1 API, job update accepts this as a payload param;
      job delete accepts this as a query param.
      
      Any user supplied value is validated within the agent HTTP handler
      removing the need to pass invalid requests to the server.
      
      The register and deregister opts functions now all for setting
      the eval priority on requests.
      
      The chan...
      80dcae72
  9. 22 Nov, 2021 5 commits