...
- Security - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning.nodetail&epics=visible&selectedEpic=POLICY-514
Policy components support HTTPS, but there is no clear plan for supporting certificates across components in ONAP. The work involved would only be configuration.
Code coverage >50%
Manageability - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning&selectedIssue=POLICY-595&epics=visible&selectedEpic=POLICY-516
- Logging - Logging is fully supported already but WIP as far as organization of log files.
- Instantiation <1 Hour - currently achievable
- Scalability & Resiliency - WIP
- https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning&selectedIssue=POLICY-595&epics=visible&selectedEpic=POLICY-515
- https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning&selectedIssue=POLICY-595&epics=visible&selectedEpic=POLICY-513
- Working both in conjunction with MSB and OOM teams. Our notes/progress:
- Usability - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning&selectedIssue=POLICY-595&epics=visible&selectedEpic=POLICY-517
- We have updated our Beijing Architecture documentation
- Performance & Stability - No work done yet
- https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning&selectedIssue=POLICY-595&epics=visible&selectedEpic=POLICY-392
- https://jira.onap.org/secure/RapidBoard.jspa?rapidView=15&view=planning&selectedIssue=POLICY-595&epics=visible&selectedEpic=POLICY-512
- We have been addressing scalability and resiliency first - they were the highest priority
- With JUnit coverage being finished, we will re-direct resources to work on this
...
In parallel, we are working with members of the Modeling team to determine what the Policy Model's should look like.
We expect tighter integration with the SDC Project to begin in Cassablanca
API Updates
There are no changes to the current Policy API. Policy API
We are currently re-designing our API's (eg. Policy Lifecycle API's) to further improve our platform. We expect to begin releasing this possibly in Cassablanca/Dublin. When ready we will schedule our current Beijing API for deprecation.