Ramesh - you are missing requirement on Policy for Service Assurance. Assuming that there is a common API for the External Controller. Or perhaps not, its not clear from this document. Then Policy team must build that API. I'm not sure.
Regarding federation of service policies, the only work would be for there to be a model for such policies. The Policy team would require Use Case to help to define/build/provide that model. Once done, the work should not be a problem for the Policy team.
Pamela, thanks. I have updated with policy for service assurance requirement. My thought, to be discussed with broader team, is to use the external controller adapter as a common, single proxy for all ONAP components to talk to the external controller. So, policy would need to use that as well.
2 Comments
Pamela Dragosh
Ramesh - you are missing requirement on Policy for Service Assurance. Assuming that there is a common API for the External Controller. Or perhaps not, its not clear from this document. Then Policy team must build that API. I'm not sure.
Regarding federation of service policies, the only work would be for there to be a model for such policies. The Policy team would require Use Case to help to define/build/provide that model. Once done, the work should not be a problem for the Policy team.
Ramesh Nagarajan
Pamela, thanks. I have updated with policy for service assurance requirement. My thought, to be discussed with broader team, is to use the external controller adapter as a common, single proxy for all ONAP components to talk to the external controller. So, policy would need to use that as well.