It was a very interesting proposal from China Telecom. It would be interesting for us to get a chance to understand the proposal in a little more detail. There were multiple control loops in there, and there is overlap with what is happening in other projects.

From a control loop side, it would be good to work with China Telecom and Huawei so that we can work together and reduce or eliminate any functional overlap and get good alignment with other initiatives. As this is a multi-project initiative, the CL subcommittee would be a good forum to explore this item.

AP: Invite the China Telecom people to come and present the proposal to the Control Loop subcommittee.  The item is here REQ-329 - Getting issue details... STATUS

Ken KANISHIMA informed the meeting that, at the Documentation project meeting, Kenny Paul announced that the LFN has hired a team of technical writers to improve the ONAP documentation. One of the areas that they will be focusing on is Control Loop Design documentation. Amar from Aarna networks is the tech writing team lead.

cl664y@att.com has been running some sessions on operationalization of control loops, Service Assurance Sync-Up calls. There was a proposal to get those discussions to be brought to the Control Loop subcommittee. Scott Blandford pointed out that those discussions would be very valuable to have on the Control Loop subcommittee rather than as a separate series of meetings. The proposal is to unify the calls.

Self service control loops, may be a PoC in Guilin because the main DCAE-MOD work is a PoC. The NiFi approach will be retained in Guilin, with some enhancements such as health check. DCAE-MOD is usable, but it is at "working well but use at your own risk" in Guilin.

Readthedocs is available for DCAE-MOD, explaining the current structure. In Guilin documentation will be improved.

Michela Bevilacqua