TSC Members, I met this afternoon with members of the OOM project and MUSIC team. I confirmed the following
Although on the key common area among both projects is resiliency, OOM’s scope is life cycle management of the ONAP platform itself. Scope is the following https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project MUSIC, on the other hand, is focusing on database resiliency/scalability across sites. MUSIC and OOM are complimentary, and MUSIC is optional and is relevant to only few projects. Per authors, the scope is the following MUSIC is a shared service with recipes that individual ONAP components and micro-service can use for state replication, consistency management and state ownership across geo-distributed sites. MUSIC will make sure that the right service data is available at the right place, and at the right time to enable federated active-active operation of ONAP. The OOM team recommended that MUSIC should be an independent project. My criteria are for architecture input which has been vetted already. OOM to provide recommendation which they have, and finally, the TSC to vote. Kenny will shortly send out a vote for MUSIC. Please go ahead and vote as +1, 0, -1. If you have not been part of the discussions and have questions, then please follow up directly with the OOM and MUSIC teams. Thanks, and appreciate everyone for doing their due diligence. Mazin
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
