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:

• server; configuration for the WEB server

  • used port for HTTP/HTTPS, this is however not the port numbers visible outside the container

  • SSL parameters for setting up using of key store and trust store databases.

• webclient; configuration parameters for a web client used by the component
  
  

  • SSL parameters for setting up using of key store and trust store databases.

  • Usage of HTTP Proxy; if configured, the proxy will be used for accessing the NearRT-RICs

• logging; setting of of which information that is logged.

• filepath; the local path to a file used for dynamic configuration (if used). See next chapter.

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

See also Honolulu - Configuration of Certs

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, e.g. an SDNC instance (with A1-Adapter)

• One entry for each near-RT-RIC, which includes:

  • The base URL of the near-RT-RIC

  • A optional list of O1 identifiers that near-RT-RIC is controlling. An application can query this service which near-RT-RIC should be addressed for which component (e.g. cells, sectors, locations, etc.) .

  • An optional reference to the controller to use, or excluded if the near-RT-RIC can be accessed directly from this A1 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.

For details about the syntax of the file, there is an example in source code repository/config/application_configuration.json. This file is also included in the docker container /opt/app/policy-agent/data/application_configuration.json_example.

Using CBS/Consul database for dynamic configuration

The access of CBS is setup by means of environment variables. There is currently no support for setting these at on boarding.

The following variables are required by the CBS:

• CONSUL_HOST

• CONSUL_PORT

• CONFIG_BINDING_SERVICE

• SERVICE_NAME