...
- Vijay Venkatesh Kumar
- Filling Dublin gaps and focus on model-driven control loop design.
- Continue conversation with Policy Team to iron out a better strategy to handle Policy-DCAE notifications. One proposal is to have Policy keep keeping track of <client, filter> pairs, where the filter is a specific condition that needs to be satisfied so as the client can be notified. When the condition is met, PDP notifies DCAE Policy Handler via DMaaP.
- Improve and extend the microservice onboarding process. Today, it's based on TOSCA. The goal is to include other technologies like Helm. This will require also to understand how Policy can support that in the policy model.
- Gervais-Martial Ngueko
- Microservice blueprint and service model distributions should be decoupled. SDC shall provide service model, while CLAMP shall receive the microservice blueprints in a separate process so as to maintain a catalog of available microservices. This way, users can select which microservice they want for a specific closed loop, with the possibility to reuse microservices that are already deployed (shared microservice vs. stand alone approach).
- To support the previous point, CLAMP should be able to generate deployment artifacts that are then sent to DCAE. In the current approach, SDC is creating and distributing deployment artifacts.
- Can we get more support from the community to the closed loop subcommittee?
...