Attachments (including meeting recording):
Attendees:
| Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
START RECORDING
| 1 | Service model and schema impact | Benjamin Cheung | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | Security Requirements for pods | James Forsyth |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 4 | 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?
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 5 | SONAR coverage report | IN PROGRESSDONE | https://sonarcloud.io/organizations/onap/projects
James 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 6 | Looking for volunteer to fix papyrus issue | OPEN |
Graphgraph doesn't parse the latest AAI schema correctly. Need someone to investigate | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 7 | Spring boot upgrade issue | IN PROGRESSDONE |
2 Spring beans with the same name is disallowed in Spring boot 2 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 8 | sparky and data-router certificate issue | Francis Paquette | IN PROGRESS | Sparky is using the AAF certificate interaction with Portal but a self-signed certificate to talk to search-data-service. The search-data-service key story was removed.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 9 | Collab efforts | IN PROGRESS | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 10 | 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 11 | Discuss developers call time | DONE | Tuesdays @ 9 AM US/Eastern, 19:30 India Standard Time | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 12 | 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 | Search guard issue | Giulio Graziani | ON HOLD | Merged and released yesterday; issue is closed.
Tracking for Frankfurt:
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 | E2E Network Slicing | LIN MENG | DONE | For the E2E Network Slicing use case for Frankfurt Release, we intend to leverage the nested service model work that has been going on since Dublin release. From A&AI perspective, we foresee that the schemas would have to be enhanced to cover network slicing models. We have considered A&AI to be a stretch goal for Frankfurt, though we are committing resources. So, we would like to start the discussion in the coming weeks, and subsequently implementation work to try our best to complete the implementation for Frankfurt. AAI-2600 has been created just to indicate the SDC impacts, we will update it with more details, and also join the A&AI weekly call during the next 1-2 weeks to discuss further. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 15 | Portal SDK Upgrade | IN PROGRESS |
Francis Paquette need evaluation of feasibility in Frankfurt for sparky | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 16 | GraphGraph Image Missing in Nexus | Venkata Harish Kajur | OPEN | Graph Graph Images are missing from nexus and it needs to be resolved in order for elalto deployment to be successful. OOM-2161 How did this docker image get pushed to nexus and why was it removed from nexus? Graphgraph was removed from the default helm chart, but we still need to get these jobs fixed.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 17 | Data-router not starting | IN PROGRESS | Assigned
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 18 | Cassandra 3 | DONE | SDC wants to move up to Cassandra 3 in the shared db environment.
https://old-docs.janusgraph.org/0.3.2/version-compat.html | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 19 | Java 11 | James Forsyth | ON HOLD | Venkata Harish Kajur tried schema service, a couple of dependency changes were required to get it to start. Eclipselink that is currently configured is incompatible. <groupId>javax.activation</groupId> is also incompatible Needs more investigation for other repos Need new common image (which Alpine image would we pick?) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 20 | AAI UI Issue | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 21 | AAI Committers |
Peng He is a potential committer on ESR (currently only Jimmy can commit ESR code) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 22 | Code Test Coverage | Goal for Frankfurt is 55% AAI-Common 58.7
sparky-fe graphgraph | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 23 | Upcoming R6 Functional Requirements | Benjamin Cheung | IN PROGRESS | Release 6 (Frankfurt) proposed use cases and functional requirements Use Case Realization Call: September 25, 2019
We have created REQ-158 -
We are currently reviewing the list of items we found in the BBWF BBS testing and once we sort through them we will communicate the results back to ONAP community. Regarding AAI specifically, we do not foresee any new requirements for Frankfurt, but we would like to conclude the review first before jumping to final conclusions.
We are not expecting any changes at this time. Tech Mahindra is working on populating a&ai with the VNF specific information from K8S. There is a chance that we realize some changes to the schema, but we don’t expect any changes to the code.
During run-time solution there are AAI impacts. Run-time solution is not planned for Frankfurt release. Only Import Service Catalog solution in SDC is targeted for F release. AAI Impact highlights: After Service Order decomposition in SO, CFS Service Instance details will be stored in AAI. After response from 3^rd^ Party Domain, RFS instance details will be updated in AAI. The sequence diagram ReUse in AAI: We plan to leverage the SPPartner model, created for CCVPN, to store the 3^rd^ Party details in AAI. org.onap.aai.domain.yang.SpPartner present in aai-schema v15
Have done some prototyping in Dublin to ingest topology from external controllers and show them in A&AI. Will need more work to act on notifications from controllers and keep the topology in sync
For the 5G Bulk PM use case in R6, I’m attaching a few slides showing how we think AAI can be used as part of the UC realization. We are currently making the following assumptions:
Can you review the slides and the assumptions above and let us know if you see any issue. We can also setup a separate meeting if needed. Note: I will share the same slides on the SO weekly meeting today.
Frankfurt Release Requirements
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 24 | Migration | Ankit Bhatt | IN PROGRESS | What is the purpose of MigrateCloudRegionUpgradeCycle migrator in onap graphadmin migration framework?
From Casablanca to Dublin, should these be run?
Migration will check if it's already been run, and won't run again. Jira task created to track this: AAI-2689 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 25 | API | Former user (Deleted) | Questions regarding how to use the api Sparky Running on Node Port: 30220 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 26 | AAF / AAUI data preload | IN PROGRESS | Status on
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 27 | NexusIQ | IN PROGRESS | Pain, pain, pain. 218 items that must be documented currently across the AAI repos, expanding all the time. 1) We need a repo strategy 2) We need a maintenance strategy 3) We need a versioning strategy 4) We need responsible parties for each repo / component 5) Strategy for oparent dependency management | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 28 | ESR | IN PROGRESS | Need to know if the ZTE team who built ESR intends to continue to support this sub-project in Frankfurt. Multiple Jira issues were not worked in Dublin / El Alto, which leads me to think that the ESR project might need to be deprecated. Inviting Bo Lv and Former user (Deleted)to see what the current status is. Hi, we didn't have resources for ESR in El Alto, and I(Huabing Zhao) and Lv Bo won't be able to contribute to ESR in F release, but Peng He will continue supporting ESR in F release on behalf of ZTE team. Please add him in the loop for the ESR related issues.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 29 | AAI Openlab Tenant Space | IN PROGRESS | A kubernetes cluster is installed in WR using RKE NFS node is 10.12.5.10 Followed these instructions https://docs.onap.org/en/latest/submodules/oom.git/docs/oom_setup_kubernetes_rancher.html? Need to determine what gets installed, testing opportunities, CSIT, distribution flows, etc. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 30 | v17 schema for Frankfurt | ON HOLD | Since the CCVPN SOTN proposal is in progress already, could we have the v17 schema introduced into master branch to receive the updates for Frankfurt release?
See also AAI-CCVPN-Extension-SOTN Proposals for Frankfurt Release and
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 31 | AAI Bugs | IN PROGRESS |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 32 | Docker images not pushing | James Forsyth | DONE | docker pull nexus3.onap.org:10003/onap/babel:1.5.0 - 1.5.1 pushed, will be release version docker pull nexus3.onap.org:10003/onap/aai-gizmo:1.5.0 - 1.5.2 pushed, will be release version docker pull nexus3.onap.org:10003/onap/aai-data-router:1.5.0 - 1.5.1, will be release version docker pull nexus3.onap.org:10003/onap/aai-search-data-service:1.5.0 - 1.5-STAGING-latest available, no tagged images
docker pull nexus3.onap.org:10003/onap/elasticsearch-sg:1.5.0 - same as search data service docker pull nexus3.onap.org:10003/onap/aai-model-loader:1.5.0 - 1.5.1 will be release version docker pull nexus3.onap.org:10003/onap/aai-spike:1.5.0 - 1.5.1 will be release version docker pull nexus3.onap.org:10003/onap/aai-sparky-be:1.5.0 - 1.5-STAGING-latest, no tagged images Want to migrate to an actively support maven docker plugin since Spotify docker plugin. Consider fabric.io - an example is aai/resources | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 33 | Alpine images | Dmitry Puzikov (Deactivated) | DONE | Jenkins jobs needed to create / push the common alpine image that the AAI containers will use, still need this completed before we merge the outstanding commits.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 34 | GlowRoot | OPEN | Consider adding glow root profiling for AAI Microservices | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 35 | Performance Issue | OPEN | FREEMAN, BRIAN D 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"} | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 36 | Spring Boot 2 | James Forsyth | IN PROGRESS |
aai-common:1.5.2 (not released yet) will be the el-alto library for springboot 1.5.x microservices. There needs to be some urgency to migrate the microservices to spring boot 2, since 1.5.3+ will not be backward compatible and so dependent applications might not have security updates if they stay on 1.5.2. 1.6.0 (Frankfort, currently master branch) aai-common will be springboot 2 so microservices must be updated by Frankfurt. Springboot 1.5.21 is the latest (and last) version in the 1.5.x spring boot train. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 37 | Vetting DSL Queries | OPEN | Will discuss strategies AAI will employ to protect itself from rogue queries. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 38 | 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 |
...