...

...

...

...

...

...

...

...

Static configuration - Settings that cannot be changed at runtime (application.yaml)

The file ./config/application.yaml is read by the application at startup. It provides the following configurable features:

...

For details about the parameters in this file, see documentation in the file.

Dynamic configuration - Settings that can be changed at runtime (application_configuration.json or REST or Consul or ConfigMap)

The component has configuration that can be updated in runtime. This configuration can either be loaded from a file (accessible from the container) or from a CBS/Consul database (Cloudify). The configuration is re-read and refreshed at regular intervals.

The configuration includes:

• Optional Controller configuration, which includes information on how to access the a1-adaptere.g. an SDNC instance (with A1-Adapter)
• One entry for each NearRTnear-RT-RIC, which includes:
  • The base URL of the NearRT near-RT-RIC
  • A optional list of O1 identifiers that the NearRT near-RT-RIC is controlling. An application can query this service which NearRT near-RT-RIC should be addressed for controlling (for instance) a given Cellwhich component (e.g. cells, sectors, locations, etc.) .
  • An optional reference to the controller to use, or excluded if the NearRTnear-RT-RIC can be accessed directly from this componentA1 Policy Management Service.
• Optional configuration for using of DMAAP. There can be one stream for requests to the component and an other stream for responses.

...

The following variables are required by the CBS:

• CONSUL_HOST
• CONSUL_PORT
• CONFIG_BINDING_SERVICE
• SERVICE_NAME