2020-07-01 AAI Meeting Notes
- Shirley Morgan
- William Reehil
Attachments (including meeting recording): 20200701 AAI Weekly Meeting
Attendees: William Reehil
@ Ondrej Frindrich
| Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
START RECORDING
| 1 | Network Splicing | OPEN | guochuyi and dhebeha mj brought some proposed AAI schema and edge rule changes to the meeting that need to be reviewed by our modeling experts that were not on the call. guochuyi & dhebeha mj have the action items to share the decks with William Reehil who will solicit input from @David Whitney and Chandra Cinthala | ||
| 2 | AAI CNF Modeling | OPEN | aai ← link to the AAI weekly CNF call. This team will be doing modeling work to decide how CNFs will be modelled in AAI | ||
| 3 | aai/oom chart | Currently AAI manages our own helm chart as a submodule of oom, at Frankfurt release sign-off, the oom team will pull the aai charts back into the main repo. We will still have to maintain the aai/oom repo in case a patch is needed for elalto or frankfurt. Jimmy contacted Sylvain on this topic, requesting they (oom team) handle this work and we support, awaiting response. | |||
| 4 | AAI PTL Election | James Forsyth | OPEN | Election season is underway and the AAI team will be accepting nominations for PTL. Eligible votes on PTL are AAI committers. Jimmy is stepping down from ONAP PTL role and will not self nominating. | |
| 5 | New Committer on AAI | DONE | James Forsyth is nominating William Reehil as an A&AI committer. There will be a vote on this by the A&AI committers and then approval from TSC. Bill was approved by the TSC and is officially a committer! Congrats Bill TSC Approved, and William Reehilself promoted to committer. | ||
| 6 | Guilin non-functional proposals | OPEN |
Guilin release - non-functional requirements proposed list | ||
| 7 | Guilin Functional requirements proposals | OPEN | Use Case Realization Meeting Register MoM Guilin release - functional requirements proposed list - pay special attention to the "Documenting ONAP APIs" section by Andy Mayer. The team from Orange might be interested in developing tooling around generating a more user-friendly AAI API documentation section on readthedocs. | ||
| 8 | Requirements for inclusion of GraphGraph in Guilin release | OPEN | |||
| 9 | Document AAI repo and microservice descriptions | Ondrej | OPEN | Put the link here for the document; we will share with the community and solicit feedback from repo/mS owners about the document. | |
| 10 | Frankfurt Defects |
| |||
| 11 | SOTNNI use case | https://gerrit.onap.org/r/c/aai/schema-service/+/102298 | |||
| 12 | Service model and schema impact | Benjamin Cheung | |||
| 13 | Security Requirements for pods | James Forsyth | REQ-215 - Getting issue details... STATUS | ||
| 14 | OPEN | Graphgraph not included in OOM deployment. How can we make it an essential part of the ONAP deployment. Step 0: Make it stable. Fix the docker build Jenkins jobs for graphgraph, may need to upgrade to a version of npm to be acceptable to graphgraph. Needs to fit into the LF global-job jobs. | |||
| 15 | 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
How to accelerate the migration to Unified Database?
| |
| 16 | SONAR coverage report | DONE | https://sonarcloud.io/organizations/onap/projects AAI-2793 - Getting issue details... STATUSJames Forsyth, the main reason behind these discrepancies is the fact that SonarQube is based on version 6.7.1 and SonarCoud is version 8+ After migrating to SonarCloud, we fetch updates they do automatically without the need of doing any manual upgrade. Since we migrated, few things have changed. For example:
You can find more info in the wiki :https://wiki.onap.org/display/DW/SonarCloud+migration+from+SonarQube Update 19 Feb: All Fixed except: aai-sparky-be, aai-esr-server and aai-validation. Jimmy is working on them. | ||
| 17 | Looking for volunteer to fix papyrus issue | OPEN | AAI-2771 - Getting issue details... STATUS Graphgraph doesn't parse the latest AAI schema correctly. Need someone to investigate | ||
| 18 | Spring boot upgrade issue | DONE | |||
| 19 | sparky and data-router certificate issue | Francis Paquette | IN PROGRESS | ||
| 20 | Collab efforts | IN PROGRESS | |||
| 21 | Windriver Lab Change | DONE | The Intel/Wind River lab was relocated into a new data center last week. The only change required to connect to the new location is to update the VPN IP in the .ovpn file. Here is the change: [sgooch@atl-sgooch-lx ~]$ diff -u pod-onap-01.ovpn.org pod-onap-01.ovpn --- pod-onap-01.ovpn.org 2020-01-13 13:03:03.960856010 -0500 +++ pod-onap-01.ovpn 2020-01-09 18:27:03.560549576 -0500 @@ -5,7 +5,7 @@ client dev tun proto tcp -remote 192.55.48.241 443 +remote 146.152.204.133 443 resolv-retry infinite auth-nocache nobind | ||
| 22 | Discuss developers call time | DONE | Tuesdays @ 9 AM US/Eastern, 19:30 India Standard Time | ||
| 23 | SO query in AAI | DONE | NNI Use Case - discovering 2 topologies from the network Use case is asking for the ability in AAI to link an underlay and overlay together by having a cousin relationship between 2 PNFs. Asking Chandra Cinthalato verify if that edge rule can be added for the Frankfurt release. Per Chandra: "I think pnf -> pnf edge is redundant and not needed as we can traverse (thru a logical or physical interface) from pnf -> p-interface/l-interface -> pnf."
Chandra Cinthala please note: According to shashikanth.vh, the team requires a relationship from an overlay topology node to an underlay topology node; by using the p-interface in overlay we cannot traverse to underlay node. Suggest to allow an edge for PNF→PNF, which is consistent with RFC 8345 model | ||
| 24 | Search guard issue | Giulio Graziani | ON HOLD | Merged and released yesterday; issue is closed. AAI-2617 - Getting issue details... STATUS Tracking for Frankfurt: AAI-2677 - Getting issue details... STATUS Search guard container no longer available so elasticsearch-sg won't build. Search guard allows us to secure the elastic communication, which in older versions was not available but newer versions have support for secure communication. https://www.elastic.co/blog/dear-search-guard-users Consider opendistro as replacement for search-guard Can we consider this one: https://docs.search-guard.com/latest/search-guard-community-edition | |
| 25 | E2E Network Slicing | LIN MENG | DONE | For the |
