Target loaders

gnmic supports dynamic loading of gNMI targets from external systems.

Two types of target loaders are supported, from file or from a Consul KV store

File target loader#

gnmic is able to watch changes happening to a file carrying the gNMI target configuration.

A file targets loader can be configured in a couple of ways:

• using the --targets-file flag:

gnmic --targets-file ./targets-config.yaml subscribe

• using the main configuration file:

loader:
  type: file
  # path to the file
  file: ./targets-config.yaml
  # watch interval at which the file
  # is read again to determine if a target was added or deleted.
  interval: 5s

The --targets-file flag takes precedence over the loader configuration section.

The targets file can be either a YAML or a JSON file (identified by its extension json, yaml or yml), and follows the same format as the main configuration file targets section. See here

Examples:

10.10.10.10:
    username: admin
    insecure: true
10.10.10.11:
    username: admin
10.10.10.12:
10.10.10.13:
10.10.10.14:

{
    "10.10.10.10": {
        "username": "admin",
        "insecure": true
    },
     "10.10.10.11": {
        "username": "admin",
    },
     "10.10.10.12": {},
     "10.10.10.13": {},
     "10.10.10.14": {}
}

Just like the targets in the main configuration file, the missing configuration fields get filled with the global flags, the ENV variables, the config file main section and then the default values.

Consul target loader#

The consul target loader is basically gnmic watching a KV prefix in a Consul server.

The prefix is expected to hold each gNMI target configuration as multiple Key/Values.

For example, the below YAML file:

10.10.10.10:
    username: admin
    insecure: true
10.10.10.11:
    username: admin
10.10.10.12:
10.10.10.13:
10.10.10.14:

is equivalent to the below set of KVs:

Consul Target loader configuration:

loader:
  type: consul
  # address of the loader server
  address: localhost:8500
  # Consul Data center, defaults to dc1
  datacenter: dc1
  # Consul username, to be used as part of HTTP basicAuth
  username:
  # Consul password, to be used as part of HTTP basicAuth
  password:
  # Consul Token, is used to provide a per-request ACL token which overrides the agent's default token
  token:
  # the key prefix to watch for targets configuration, defaults to "gnmic/config/targets"
  key-prefix: gnmic/config/targets