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.
- 25 Jan, 2021 9 commits
-
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
Mahmood Ali authored
-
- 21 Jan, 2021 1 commit
-
-
Buck Doyle authored
This will report the names of flaky tests instead of just counting them.
-
- 20 Jan, 2021 7 commits
-
-
Dennis Schön authored
-
Drew Bailey authored
-
Seth Hoenig authored
consul/connect: Enable running multiple ingress gateways per Nomad agent
-
Seth Hoenig authored
Co-authored-by:
Tim Gross <tgross@hashicorp.com>
-
Seth Hoenig authored
-
Seth Hoenig authored
-
Dennis Schön authored
-
- 19 Jan, 2021 5 commits
-
-
Marcus Naughton authored
Fixed Markdown for GCP example.
-
Seth Hoenig authored
Connect ingress gateway services were being registered into Consul without an explicit deterministic service ID. Consul would generate one automatically, but then Nomad would have no way to register a second gateway on the same agent as it would not supply 'proxy-id' during envoy bootstrap. Set the ServiceID for gateways, and supply 'proxy-id' when doing envoy bootstrap. Fixes #9834
-
Seth Hoenig authored
consul/connect: always set gateway proxy default timeout
-
Seth Hoenig authored
If the connect.proxy stanza is left unset, the connection timeout value is not set but is assumed to be, and may cause a non-fatal NPE on job submission.
-
Drew Bailey authored
-
- 15 Jan, 2021 5 commits
-
-
Kris Hicks authored
This has to have been unused because the HasPrefix operation is backwards, meaning a Command.Env that includes PATH= never would have worked; the default path was always used.
-
Drew Bailey authored
* Persist shared allocated ports for inplace update Ports were not copied over when performing inplace updates in the generic scheduler * changelog * drop spew
-
Seth Hoenig authored
Missed improvement regarding IGW task customization
-
leonardobsjr authored
Seems like this was missing from the docs. Was trying to make this work on 1.0.1 (it was on the docs), however, it's only working on 1.0.2.
-
Shishir Mahajan authored
-
- 14 Jan, 2021 10 commits
-
-
Drew Bailey authored
* bump upgrade guide version * drop 1.0.3 until there are upgrade specifics
-
Kris Hicks authored
* Throw away result of multierror.Append When given a *multierror.Error, it is mutated, therefore the return value is not needed. * Simplify MergeMultierrorWarnings, use StringBuilder * Hash.Write() never returns an error * Remove error that was always nil * Remove error from Resources.Add signature When this was originally written it could return an error, but that was refactored away, and callers of it as of today never handle the error. * Throw away results of io.Copy during Bridge * Handle errors when computing node class in test
-
Kris Hicks authored
In this change we'll properly return the error in the CSIPluginTypeMonolith case (which is the type given in DeleteNode()), and also return the error when the given ID is not found. This was found via errcheck.
-
Kris Hicks authored
If one thread calls `Flush()` on a gatedwriter while another thread attempts to `Write()` new data to it, strange things will happen. The test I wrote shows that at the very least you can write _while_ flushing, and the call to `Write()` will happen during the internal writes of the buffered data, which is maybe not what is expected. (i.e. the `Write()`'d data will be inserted somewhere in the middle of the data being `Flush()'d`) It's also the case that, because `Write()` only has a read lock, if you had multiple threads trying to write ("read") at the same time you might have data loss because the `w.buf` that was read would not necessarily be up-to-date by the time `p2` was appended to it and it was re-assigned to `w.buf`. You can see this if you run the new gatedwriter tests with `-race` against the old implementation: ``` WARNING: DATA RACE Read at 0x00c0000c0420 by goroutine 11: runtime.growslice() /usr/lib/go/src/runtime/slice.go:125 +0x0 github.com/hashicorp/nomad/helper/gated-writer.(*Writer).Write() /home/hicks/workspace/nomad/helper/gated-writer/writer.go:41 +0x2b6 github.com/hashicorp/nomad/helper/gated-writer.TestWriter_WithMultipleWriters.func1() /home/hicks/workspace/nomad/helper/gated-writer/writer_test.go:90 +0xea ``` This race condition is fixed in this change.
-
Kris Hicks authored
-
Kris Hicks authored
-
Drew Bailey authored
-
Drew Bailey authored
* changelog for release 1.0.2 * Generate files for 1.0.2 release * Release v1.0.2 * rm generated files, update changelog for next release * checkout bindata_assetfs * bump version Co-authored-by:
Nomad Release bot <nomad@hashicorp.com>
-
Brandon Romano authored
Website StackMenu updates for 1/14
-
Mahmood Ali authored
Only lookup GO_TAGS variable, and avoid the false positives where GO_TAGS is a variable suffix.
-
- 13 Jan, 2021 3 commits
-
-
Drew Bailey authored
-
Seth Hoenig authored
e2e: use jobspec2 Parse for parsing jobfile in e2e utils
-
Seth Hoenig authored
We directly parse job files in e2eutil, but currently using jobspec package. Instead, use the Parse method from the jobspec2 package so we can parse job files with new features.
-