Skip to content

Config Application#

Group/Version config.eda.nokia.com/v1
Supported OS Nokia SR Linux: 24.10.*, 25.3.*, 25.7.*, 25.10.*, 26.3.*
Nokia SR OS: 24.10.r4+, 25.3.r2+, 25.7.*, 25.10.*, 26.3.*
Arista EOS: 4.33.2f:beta
Cisco NX-OS: 10.5.2:alpha
Catalog Nokia/catalog/config
Source Code coming soon

Configuration management is one of the core pillars of the EDA network management system. When it comes to configuration, every EDA resource falls into one of four categories:

  1. Resources that do not result in configuration being pushed to a node.
    • Example: an IPAllocationPool.
  2. Resources that create other derived EDA resources.
  3. Resources that are configured on a node only when another resource references them.
  4. Resources whose creation directly results in configuration being pushed to nodes.

The application provides the following components:

Custom configuration#

Not every configuration parameter in every version of each supported operating system is available through an EDA abstraction. To fill this gap while waiting for official EDA support, users are encouraged to write abstraction applications that fulfill their needs.

Although we continuously improve the developer experience, writing an application may seem daunting. It may also be excessive when only one configuration setting needs to change.

This is where the Configlet comes in: it allows the operator to specify which configuration options need to be pushed to which nodes, providing a quick and EDA-managed abstraction that encompasses your network's needs.

Warning

Do not rely on deviations (manual changes through the CLI) for short- or long-lived workarounds. Instead, convert each deviation into a Configlet to track it and ensure that it is retained when a node reboots.