...
- Sprint 1
- POLICY-71, POLICY-72, POLICY-73, POLICY-83 - Need to coordinate and help from folks.
- POLICY-40 - MSB Integration
Functional Test Case definition
MSB Integration Guide.pptx Pamela Dragosh
...
POLICY-40 MSB Integration
- Huabing showed that MSB dockers are ready and they can just be pulled out and test.
- Huabing gave a presentation and demo of how to use MSB to register/discover/setup a REST service, especially for registering REST service to MSB, accessing the rest service via internal api gateway.
- Pam described that we are using DMaaP to communicate between Policy and APPC. To this end, we need to set up a topic, controller, AAF, etc.
...
- Pam pointed out that topics can also be advertised via MSB. Currently, CLAMP set up a lot of topics for micro services and it has the need to use MSB.
- Ruan raised the question of how to monitor the services that is used for load balancing if MSB is utilized. Huabing promised to have more offline touch base with Ruan. Huabing also mentioned ngnix can be used for that purpose.
- Xinyuan asked maybe we can still use MSB in drools to trigger action ? We are not using MSB in drools.
- Pam asked if we can just rely on OOM to register service ? Yes at the moment.
- Ruan asked what is OOM ? ONAP Operation Manager.
- Pam pointed out that folks should figure out what is the point of changes needed in Policy for MSB integration. We need some volunteer to contribute. Xinyuan from ZTE volunteers to contribute the changes in Policy for MSB integration.
- Pam mentioned that for sprint 1, we don’t want to change Policy APIs.
- Huabing added that MSB can also help backward compatibility.
Pam suggested to put your name to release contributor table if you want to contribute. For example ZTE for VF-C.For POLICY-49, we still need some volunteer to work with SDC team for SDC Distribution API integration.