Candidate release 1 3

[raghavendra-nataraj]

Remote Heath check feature
Static DNS resolution
Refresh configs
OpenSSL 1.0.x version multi-threading locking
Marking host sockets
Mutual TLS health checks
Pub-Sub architecture(Kafka)
Modular Build
Client Socket API(C++ python)

Description

Remote Heath check feature -> Share results between instances of NetCHASM via TCP or TLS sockets
Static DNS resolution -> Socket API to provide IPs the host should resolve to. The DNS resolution will use this address
Refresh configs -> Option to reload only configs without the need to reload the master configs
OpenSSL 1.0.x version multi-threading locking -> Older version of OpenSSL needs a mechanism to handle multithreading locking.
Marking host sockets -> Mark sockets which perform the health checks.
Mutual TLS health checks -> Perform mutual health checks for HTTPS , FTPS, and TCP
Pub-Sub architecture(Kafka) -> Option to push results via Published-Subscriber architecture. Default Kafka Implementation available.
Modular Build -> Build options to enable and disable plugins and third-party libraries.
Client Socket API(C++ python) -> Python and C++ client socket API to communicate with NetCHASM daemon

Motivation and Context

Features implemented as part of internal and open source requirements

How Has This Been Tested?

Unit tests have been written covering the new code. Also, the features have been tested across existing and new functional tests.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.