1 | Honolulu requirements | OPEN | 2 | Requirements for inclusion of GraphGraph in Honolulu release | OPEN | List goes here Open Jira tickets as tasks for H release Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-2910 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-2911 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-2912 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-2913 |
---|
|
Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | AAI-2713 |
---|
| | 3 | Security Requirements for pods | James Forsyth | Jira |
---|
server | ONAP JIRA |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
key | REQ-215 |
---|
|
| 4 | Brownfield / deployed / embedded inventory systems and AAI | Fred from Verizon | OPEN | How do we accelerate migration using A&AI and the RunTime DB solution Proposed a topic to be explored by AI&I and other ONAP WGs. High impact, common interest among most CSPs
Status Quo: Most operators have multiple, siloed, possibly overlapping topology and inventory (domain specific) databases Goal is to integrate ALL Inventory, and Topology databases into a Unified AI&I Architecture modeled DB which would contain ALL VNFs (VMs/Containers), PNFs, plus support easy expansion for future Inventory & Topology constructs/technologies. May take considerable time/investment (both are short). Targeted Objectives - Fast integration/consolidation time
- Minimize impact to business systems during migration
- Reduce throw away code
- Reduce throw away integration work
- Improve Service/Resource LCM & SA, especially for 5G
How to accelerate the migration to Unified Database? - Phased Externalization of key PNF/VNF/CNF attributes currently stored in multiple inventory and topology silos.
- Simplify the eventual consolidation of Inventory and Topology DBs using proposed automation tools and advanced discovery capabilities supporting the above
- Leverage AI&I and possibly the ONAP Runtime Config DB and other ONAP WGs to help solve the problem
- Proposed topic can be explored by the AI&I and other ONAP WGs.
- Need to expand this preliminary list
| 5 | Papyrus Enhancements | OPEN | Papyrus modeling (reverse engineering) Jacqueline Beaulac AAI Information Model Reverse Engineering Meeting https://jira.onap.org/browse/AAI-2441 Need attribute descriptions story for graphgraph, any other requirements? Is there an automated publishing mechanism we should look into? Kamel Idir has v20 & v21 reverse engineered model representations - AAI Swagger v20 UML AAI Swagger v21 UML | Guilin Maintenance Release |
|
|
8 | 6 | AAI Bugs | | IN PROGRESS | Jira |
---|
server | ONAP JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution,fixversions |
---|
maximumIssues | 30 |
---|
jqlQuery | project = AAI and type = Bug and status != closed |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 7 | Performance Issue | | OPEN | Brian Freeman reported that when there are ~2400 vservers returned in a closed loop custom query, AAI takes minutes to respond. We've discussed paging previously, any other ways to optimize this?
PUT 'https://aai.onap:8443/aai/v16/query?format=resource'
{"query":"query/closed-loop","start":"/cloud-infrastructure/cloud-regions/cloud-region/CloudOwner/RegionOne/tenants/tenant/28481f6939614cfd83e6767a0e039bcc/vservers/vserver/6ad9eb6b-d7fc-46d6-8617-4c9b46e7308b"}
8 | New UI Features / Historical Tracking | | OPEN | The AT&T team has done an exciting POC at a sprint-a-thon event that they would like to share with the community.
ATT wants to contribute additional UI views to ONAP, want to discuss path forward
Link for self repo creation: https://wiki.onap.org/display/DW/Self+Repo+Creation+via+INFO.yaml
William/Jimmy will look into this for creating the new sparky extensions repository |
|
|
|