Bug 1650576

Previously, OpenDaylight packaging used the default OpenDaylight `log_pattern` values and included the PaxOsgi appender. These default values are not always appropriate for every deployment and it is appropriate to configure custom values. With this update, `puppet-opendaylight` has two additional configuration variables: 1) `log_pattern`: Use this variable to configure which log pattern you want to use with the OpenDaylight logger log4j2. 2) `enable_paxosgi_appender`: Use this boolean flag to enable or disable the PaxOsgi appender. `puppet-opendaylight` also modifies the OpenDaylight defaults. Deployments that use `puppet-opendaylight` have new defaults: - `log_pattern`: %d{ISO8601} | %-5p | %-16t | %-60c{6} | %m%n - `enable_paxosgi_appender`: false .New variable configuration options ##### `log_pattern` String that controls the log pattern used for logging. Default: `%d{ISO8601} | %-5p | %-16t | %-60c{6} | %m%n` Valid options: A string that is a valid log4j2 pattern. ##### `enable_paxosgi_logger` Boolean that controls whether the PaxOsgi appender is enabled for logging. If you enable the `enable_paxosgi_logger` variable, you must also modify the log pattern to utilize the additional capabilities. Modify the `log_pattern` variable and include a pattern that contains the PaxOsgi tokens. For example, set the `log_pattern` variable to a string that includes the following values: '%X{bundle.id} - %X{bundle.name} - %X{bundle.version}' If you do not edit the `log_pattern` variable, the PaxOsgi appender is still enabled and continues to run but logging does not utilize the additional functionality. For example, set the `enable_paxosgi_logger` variable to `true` and set the `log_pattern` variable to the following value: '%d{ISO8601} | %-5p | %-16t | %-32c{1} | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n' Default: `false` Valid options: The boolean values `true` and `false`.