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.
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
- 18 Mar, 2021 2 commits
-
-
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.
-
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.
-
- 15 Mar, 2021 1 commit
-
-
davemay99 authored
-
- 12 Mar, 2021 1 commit
-
-
Florian Apolloner authored
-
- 10 Mar, 2021 1 commit
-
-
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.
-
- 09 Mar, 2021 3 commits
-
-
Tim Gross authored
-
James Rasell authored
-
Dave May authored
-
- 08 Mar, 2021 2 commits
-
-
Michael Schurter authored
-
Tim Gross authored
-
- 01 Mar, 2021 1 commit
-
-
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.
-
- 26 Feb, 2021 1 commit
-
-
Andre Ilhicas authored
-
- 25 Feb, 2021 1 commit
-
-
Dave May authored
-
- 24 Feb, 2021 2 commits
-
-
Seth Hoenig authored
-
Tim Gross authored
-
- 23 Feb, 2021 3 commits
-
-
Seth Hoenig authored
This PR fixes a bug where tasks with Connect services could be triggered to destructively update (i.e. placed in a new alloc) when no update should be necessary. Fixes #10077
-
Tim Gross authored
-
Michael Lange authored
-
- 22 Feb, 2021 2 commits
-
-
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.
-
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
-
- 18 Feb, 2021 2 commits
-
-
Buck Doyle authored
-
Tim Gross authored
-
- 16 Feb, 2021 1 commit
-
-
Drew Bailey authored
* update changelog * fix changelog order
-
- 09 Feb, 2021 2 commits
-
-
Seth Hoenig authored
-
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
-
- 08 Feb, 2021 2 commits
-
-
Seth Hoenig authored
This PR adds pid_mode and ipc_mode options to the exec and java task driver config options. By default these will defer to the default_pid_mode and default_ipc_mode agent plugin options created in #9969. Setting these values to "host" mode disables isolation for the task. Doing so is not recommended, but may be necessary to support legacy job configurations. Closes #9970
-
Nick Ethier authored
-
- 05 Feb, 2021 1 commit
-
-
Seth Hoenig authored
This PR adds default_pid_mode and default_ipc_mode options to the exec and java task drivers. By default these will default to "private" mode, enabling PID and IPC isolation for tasks. Setting them to "host" mode disables isolation. Doing so is not recommended, but may be necessary to support legacy job configurations. Closes #9969
-
- 04 Feb, 2021 2 commits
-
-
Tim Gross authored
The details of host volume and CSI volume requests do not show up in `nomad plan` outputs, although the updates are detected by the scheduler and result in an update as expected.
-
Chris Baker authored
-
- 03 Feb, 2021 1 commit
-
-
Nick Ethier authored
-
- 02 Feb, 2021 3 commits
-
-
Nick Ethier authored
-
Tim Gross authored
-
Tim Gross authored
-
- 28 Jan, 2021 1 commit
-
-
Chris Baker authored
-
- 25 Jan, 2021 1 commit
-
-
Seth Hoenig authored
This PR implements Nomad built-in support for running Consul Connect terminating gateways. Such a gateway can be used by services running inside the service mesh to access "legacy" services running outside the service mesh while still making use of Consul's service identity based networking and ACL policies. https://www.consul.io/docs/connect/gateways/terminating-gateway These gateways are declared as part of a task group level service definition within the connect stanza. service { connect { gateway { proxy { // envoy proxy configuration } terminating { // terminating-gateway configuration entry } } } } Currently Envoy is the only supported gateway implementation in Consul. The gateay task can be customized by configuring the connect.sidecar_task block. When the gateway.terminating field is set, Nomad will write/update the Configuration Entry into Consul on job submission. Because CEs are global in scope and there may be more than one Nomad cluster communicating with Consul, there is an assumption that any terminating gateway defined in Nomad for a particular service will be the same among Nomad clusters. Gateways require Consul 1.8.0+, checked by a node constraint. Closes #9445
-
- 22 Jan, 2021 3 commits
-
-
Tim Gross authored
-
Tim Gross authored
Most allocation hooks don't need to know when a single task within the allocation is restarted. The check watcher for group services triggers the alloc runner to restart all tasks, but the alloc runner's `Restart` method doesn't trigger any of the alloc hooks, including the group service hook. The result is that after the first time a check triggers a restart, we'll never restart the tasks of an allocation again. This commit adds a `RunnerTaskRestartHook` interface so that alloc runner hooks can act if a task within the alloc is restarted. The only implementation is in the group service hook, which will force a re-registration of the alloc's services and fix check restarts.
-
Drew Bailey authored
-
- 21 Jan, 2021 1 commit
-
-
Charlie Voiselle authored
* Enable network namespaces for QEMU driver * Add CHANGELOG entry
-