-
Notifications
You must be signed in to change notification settings - Fork 229
Configuration
This page provides information about how to configure Gatekeeper using configuration files (static configuration) and at runtime (dynamic configuration).
The network and individual blocks are configured using the configuration files in the lua directory:
- Network
- Control Plane Services (CPS)
- Dynamic Configuration
- GT-GK Unit (GGU)
- Gatekeeper (GK)
- Grantor (GT)
- Link Layer Support (LLS)
- Solicitor (SOL)
Since Gatekeeper is a DPDK application, it can be given EAL parameters from the command line to configure various device, debugging, and memory options.
There are two EAL parameters that may be especially useful when running Gatekeeper:
--log-level <val>
The global log level is the baseline log level for all logs in Gatekeeper (see Network for more information). The global log level defined in the command line is only used for the early Gatekeeper setup, and is overwritten by the global log level defined in lua/net.lua.
--log-level gatekeeper:<val>
The Gatekeeper log level is used for all logs that are not directly related to the individual blocks (see Network for more information). The Gatekeeper log level defined in the command line is only used for the early Gatekeeper setup, and is overwritten by the Gatekeeper log level defined in lua/net.lua.
In addition to the EAL configuration, Gatekeeper can be configured via application parameters.
There are four application parameters that may be especially useful when running Gatekeeper:
--lua-base-dir <val>
The base directory for Gatekeeper Lua files. The default base directory is ./lua.
--gatekeeper-config-file <val>
The Lua configuration file to initialize Gatekeeper. The default lua file is gatekeeper_config.lua.
--log-file-name-format <val>
The name format of log files. The default name format is gatekeeper_%Y_%m_%d_%H_%M.log.
--log-base-dir <val>
The base directory for Gatekeeper log files. The default base directory is ..
At runtime, Gatekeeper can be dynamically configured using the Dynamic Configuration. This allows the user to add, delete, and show routes, neighbors, policies, etc.