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. 05 Apr, 2021 1 commit
  2. 30 Mar, 2021 1 commit
  3. 29 Mar, 2021 1 commit
  4. 28 Mar, 2021 1 commit
  5. 23 Mar, 2021 2 commits
  6. 18 Mar, 2021 2 commits
    • Tim Gross's avatar
      CSI: unique volume per allocation · 7c756967
      Tim Gross authored
      Add a `PerAlloc` field to volume requests that directs the scheduler to test
      feasibility for volumes with a source ID that includes the allocation index
      suffix (ex. `[0]`), rather than the exact source ID.
      
      Read the `PerAlloc` field when making the volume claim at the client to
      determine if the allocation index suffix (ex. `[0]`) should be added to the
      volume source ID.
      7c756967
    • Tim Gross's avatar
      CSI: remove prefix matching from CSIVolumeByID and fix CLI prefix matching (#10158) · a1eaad9c
      Tim Gross authored
      Callers of `CSIVolumeByID` are generally assuming they should receive a single
      volume. This potentially results in feasibility checking being performed
      against the wrong volume if a volume's ID is a prefix substring of other
      volume (for example: "test" and "testing").
      
      Removing the incorrect prefix matching from `CSIVolumeByID` breaks prefix
      matching in the command line client. Add the required elements for prefix
      matching to the commands and API.
      a1eaad9c
  7. 15 Mar, 2021 1 commit
  8. 12 Mar, 2021 1 commit
  9. 10 Mar, 2021 1 commit
    • Tim Gross's avatar
      scheduler/csi: fix early return when multiple volumes are requested · b66a3415
      Tim Gross authored
      When multiple CSI volumes are requested, the feasibility check could return
      early for read/write volumes with free claims, even if a later volume in the
      request was not feasible for any other reason (including not existing at
      all). This can result in random failure to fail feasibility checking,
      depending on how the map of volumes was being ordered at runtime.
      
      Remove the early return from the feasibility check. Add a test to verify that
      missing volumes in the map will cause a failure; this test will not catch a
      regression every test run because of the random map ordering, but any failure
      will be caught over the course of several CI runs.
      b66a3415
  10. 09 Mar, 2021 3 commits
  11. 08 Mar, 2021 2 commits
  12. 01 Mar, 2021 1 commit
    • Buck Doyle's avatar
      Fix rendering of DAS interstitial components (#10094) · 7832e069
      Buck Doyle authored
      With the Ember update, when the will-destroy action is called
      to check the element height, its height is already zero. That
      seems strange but I didn’t look into it any further, as
      using did-insert to store the element lets us check its height
      before any other actions when a processing button is pressed.
      7832e069
  13. 26 Feb, 2021 1 commit
  14. 25 Feb, 2021 1 commit
  15. 24 Feb, 2021 2 commits
  16. 23 Feb, 2021 3 commits
  17. 22 Feb, 2021 2 commits
    • Tim Gross's avatar
      deploymentwatcher: reset progress deadline on promotion (#10042) · 174c206b
      Tim Gross authored
      In a deployment with two groups (ex. A and B), if group A's canary becomes
      healthy before group B's, the deadline for the overall deployment will be set
      to that of group A. When the deployment is promoted, if group A is done it
      will not contribute to the next deadline cutoff. Group B's old deadline will
      be used instead, which will be in the past and immediately trigger a
      deployment progress failure. Reset the progress deadline when the job is
      promotion to avoid this bug, and to better conform with implicit user
      expectations around how the progress deadline should interact with promotions.
      174c206b
    • Seth Hoenig's avatar
      consul/connect: Fix bug where connect sidecar services would be unnecessarily re-registered · e3af4695
      Seth Hoenig authored
      This PR fixes a bug where sidecar services would be re-registered into Consul every ~30
      seconds, caused by the parent service having its tags field set and the sidecar_service
      tags unset. Nomad would directly compare the tags between its copy of the sidecar service
      definition and the tags of the sidecar service reported by Consul. This does not work,
      because Consul will under-the-hood set the sidecar service tags to inherit the parent
      service tags if the sidecar service tags are unset. The comparison then done by Nomad
      would not match, if the parent sidecar tags are set.
      
      Fixes #10025
      e3af4695
  18. 18 Feb, 2021 2 commits
  19. 16 Feb, 2021 1 commit
  20. 09 Feb, 2021 2 commits
    • Seth Hoenig's avatar
      docs: fix egregious changelog ordering · bc710d8f
      Seth Hoenig authored
      bc710d8f
    • Seth Hoenig's avatar
      consul/connect: enable custom sidecars to use expose checks · af48777d
      Seth Hoenig authored
      This PR enables jobs configured with a custom sidecar_task to make
      use of the `service.expose` feature for creating checks on services
      in the service mesh. Before we would check that sidecar_task had not
      been set (indicating that something other than envoy may be in use,
      which would not support envoy's expose feature). However Consul has
      not added support for anything other than envoy and probably never
      will, so having the restriction in place seems like an unnecessary
      hindrance. If Consul ever does support something other than Envoy,
      they will likely find a way to provide the expose feature anyway.
      
      Fixes #9854
      af48777d
  21. 08 Feb, 2021 2 commits
  22. 05 Feb, 2021 1 commit
  23. 04 Feb, 2021 2 commits
  24. 03 Feb, 2021 1 commit
  25. 02 Feb, 2021 3 commits