...
Another prism through which one can view CHAP is that it enables ONAP components to achieve carrier grade requirements of reliability as shown in the following figure:
Current Status:
All three components of CHAP have been open sourced: MUSIC, mdbc, HAL.
OOF-Homing Optimizer (HAS) uses CHAP for its state persistence and as a highly available distributed messaging service. This is currently being run in production within ATT.
Architecture Alignment:
How does this project fit into the rest of the ONAP Architecture?
CHAP will be available as a common service like DMaap or AAF as shown in the red, oblong box below:
What other ONAP projects does this project depend on?
Since OOM is responsible for the life-cycle of ONAP components, it will also need to manage the deployment of CHAP.
How does this align with external standards/specifications?
Among the components of CHAP MUSIC and HAL export a REST API while mdbc is to be used as a jdbc driver.
Are there dependencies with other open source projects?
CHAP depends primarily on Apache Cassandra and Zookeeper.
...