This task involves updating the wiki so that the team understands the software architecture and flow diagrams.

The software architecture needs to have base interfaces such that the Policy API used can be configured from the exiting from Beijing vs. the future Policy Lifecycle API deployed at a future date.

Another question to be clarified is how Policy tracks that it has deployed the policies for the service. Service re-distribution can occur, often if another component or the possibly the policy component fails to download/deploy its artifacts. How does policy track this? If there is a failure, how does it recover?

If service re-distribution occurs for a newer version, then the application must be able to identify this and do what is necessary to update policies and at the very least fail with accurate error messages indicating why it could not update and/or re-deploy the policies for the service.

The wiki page being updated is located here:

https://wiki.onap.org/display/DW/Policy+Platform+-+SDC+Service+Distribution+Software+Architecture