Figure 10 Links to OSGi artifacts associated with individual applications
Configuration components
The
Configurations
screen enables access to the configurable components in the controller
which are used to manage the controller and application features. Some examples of when you
might want to make configuration changes include:
•
Specify an NTP server or date and time on the controller system using the NTP component
or specify a static IP address using the Network component.
•
Specify hybrid mode for controlling packet forwarding by configuring the ControllerManager
component.
•
Define how long to keep alerts and how to age out alerts by configuring the AlertManager
component.
•
Define how audit log data ages out by configuring the AuditLogManager component.
Adding or removing an SDN application might add or remove additional configuration components.
However, direct addition or removal of configuration components is not supported.
NOTE:
When controllers are operating in a team, configuration changes on one active controller
propagate to the other active controllers in the team.
See also:
•
“Using configuration component keys” (page 38)
•
“Modifying a component configuration” (page 45)
•
“Modifying NTP server or date and time” (page 46)
•
“Modifying Network settings” (page 47)
•
“Modifying Logger settings” (page 48)
Using configuration component keys
Each configuration component contains one or more component keys, each of which identify a
configurable property of the component.
Information about each component key includes the current value, the default value, and a brief
description. Where applicable, the range of suggested values is also included. You can find
information about each component key on the
Configurations
screen of the controller UI. The
controller
Configs
REST API is also available for configuring components, excluding Network
38
Using the SDN controller UI