kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-03 08:55:43 +03:00
Code Issues Packages Projects Releases Wiki Activity
21,557 Commits 1 Branch 0 Tags
fc3ff8ee13661e80589302a8b1a244081b490ec8
Commit Graph

15 Commits

Author SHA1 Message Date
Seth Hoenig
bcddcc3a98 docs: add agent consul grpc_address docs 
We already supported this configuration, but forgot to document it.
 2021-05-07 09:25:09 -06:00
Nick Ethier
b72928c9cb website: reserved cores docs 2021-05-05 08:11:41 -04:00
Mahmood Ali
de1e91987c Docs memory oversubscription (#10478) 
* update docs

* document memory_oversubscription_enabled scheduler config
 2021-04-30 14:07:56 -04:00
Tim Gross
638a0daa1b docs: Enterprise licensing updates 2021-04-28 14:46:06 -04:00
Buck Doyle
0d058e5110 docs: Fix minor fuzzy search things (#10423) 2021-04-21 14:55:17 -05:00
Charlie Voiselle
19773e469d Enable go-sockaddr templating for network-interface (#10404) 
Add templating to `network-interface` option.
This PR also adds a fast-fail to in the case where an invalid interface is set or produced by the template

* add tests and check for valid interface
* Add documentation
* Incorporate suggestions from code review

Co-authored-by: Luiz Aoqui <luiz@hashicorp.com>
 2021-04-20 13:55:10 -04:00
Seth Hoenig
350d9ebc40 api: implement fuzzy search API 
This PR introduces the /v1/search/fuzzy API endpoint, used for fuzzy
searching objects in Nomad. The fuzzy search endpoint routes requests
to the Nomad Server leader, which implements the Search.FuzzySearch RPC
method.

Requests to the fuzzy search API are based on the api.FuzzySearchRequest
object, e.g.

{
  "Text": "ed",
  "Context": "all"
}

Responses from the fuzzy search API are based on the api.FuzzySearchResponse
object, e.g.

{
  "Index": 27,
  "KnownLeader": true,
  "LastContact": 0,
  "Matches": {
    "tasks": [
      {
        "ID": "redis",
        "Scope": [
          "default",
          "example",
          "cache"
        ]
      }
    ],
    "evals": [],
    "deployment": [],
    "volumes": [],
    "scaling_policy": [],
    "images": [
      {
        "ID": "redis:3.2",
        "Scope": [
          "default",
          "example",
          "cache",
          "redis"
        ]
      }
    ]
  },
  "Truncations": {
    "volumes": false,
    "scaling_policy": false,
    "evals": false,
    "deployment": false
  }
}

The API is tunable using the new server.search stanza, e.g.

server {
  search {
    fuzzy_enabled   = true
    limit_query     = 200
    limit_results   = 1000
    min_term_length = 5
  }
}

These values can be increased or decreased, so as to provide more
search results or to reduce load on the Nomad Server. The fuzzy search
API can be disabled entirely by setting `fuzzy_enabled` to `false`.
 2021-04-16 16:36:07 -06:00
Michael Lange
e99d5a86e6 Fix the broken link in the bootstrapping custom scheduler warning 2021-04-05 14:27:22 -07:00
Bryce Kalow
ee79587a67 feat(website): migrates to new nav data format (#10264) 2021-03-31 08:43:17 -05:00
Taylor Dolezal
554f69394c Change enable to enabled 2021-03-25 14:10:54 -04:00
Drew Bailey
4484d361ee configuration and oss components for licensing (#10216) 
* configuration and oss components for licensing

* vendor sync
 2021-03-23 09:08:14 -04:00
Cathy Chang
a4d99a87f4 docs: clarify log_rotate_max_files 2021-02-19 09:37:55 -05:00
Marcus Naughton
59271739b9 Update server_join.mdx 
Fixed Markdown for GCP example.
 2021-01-19 16:47:12 -05:00
Tim Gross
d8f1e811f7 docs: remove remaining references to network_speed config 2021-01-13 08:52:25 -05:00
Jeff Escalante
0eae603a86 implement mdx remote 2021-01-05 19:02:39 -05:00