1.4.0: Merge pull request #235 from xtuml/1_4_0_release

This release carries new functionality around Logging and Reporting.

Release notes are found here: https://github.com/xtuml/munin/blob/main/doc/notes/munin1.4.0.adoc

testing CI after domain removal

This is a pre-release to test the CI after AsyncLogger and AEReception have been removed.

logging and reporting

This revision makes changes to logging and reporting as well as architectural changes
in the logging and inter-process communication technologies. 'log4cplus' is now the
fundamental logging technology. This brings a great deal of configurability with directing
logging data to appenders of different types including rolling file appenders and Kafka
appenders.
The benchmarking probe is implemented as a (configurable) logger now. This lets us
turn it on and off as needed.
A back end 'dashboard' application is prototyped (metrics/pvstats.py).

Here is a list of changes in the usage:

• The reception kafka topic is now called: Protocol_Verifier_Reception
• JSON messages written to Protocol_Verifier_Reception no longer need to be prepended with a length. Compliant JSON is now received.
• The logging folder hierarchy has been changed and documented in the 188 implementation note.
• There are 2 new topics to which the Protocol Verifier publishes reporting information.
  • 'Protocol_Verifier_InfoWarn' carries the status of jobs. Job failures are reported as Warnings; job successes are logged as Information. Other errors and failures are reported on this topic. (This was formerly the Verifier.log.) In file-based mode, this information will go to pv.log.
  • 'Protocol_Verifier_Statistics' carries PV statistical information generated by Job Management. A key statistic here is the total number of assigned jobs. In file-based mode, this information will go to pv_jm.log.
• The Benchmarking Probe is now configured as a logger. The contents of the messages are JSON. Only aeordering_event_processed and svdc_*_processed are posted to this topic. It is disabled by default. To enable it:
  • set the pv.benchmark logger to INFO.
  • See benchmark.py for an example of interrogating the probe data.
  • The messages are JSON.
• The docker-compose files now refer to separate log-config files, one for file-based logging and the other for kafka-based logging.

Munin Phase 2 Stage 4

https://github.com/xtuml/munin/blob/main/doc/notes/munin1.3.0.adoc

Munin Phase 2 Stage 3

https://github.com/xtuml/munin/blob/main/doc/notes/munin1.2.0.adoc

v1.1.1

Bump version to 1.1.1

Munin Phase 2 Stage 2

https://github.com/xtuml/munin/blob/main/doc/notes/munin1.1.0.adoc

v1.1.0-beta1

Initial prototyping of inter-domain messaging with Kafka

Munin Phase 2 Stage 1

Merge pull request #92 from xtuml/MUN_1_110_add_default_job_specific_…

…control

Added the ability to specify default timeouts for job expiry, stale e…

Munin Phase 2 Stage 1 (midstage)

https://github.com/xtuml/munin/blob/main/doc/notes/MUN2-89_midstage_release.adoc