2019-12-18 AAI Meeting Notes
- Shirley Morgan
- James Forsyth
fdAttachments (including meeting recording):
Attendees:
Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
START RECORDING
| 1 |
| Portal SDK Upgrade | @James Forsyth | OPEN | AAI-2726: Update to Portal SDK v2.6Closed @Francis Paquette need evaluation of feasibility in Frankfurt for sparky | ||||||||||||
| 2 |
| 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? @James Forsythwill look at it and ask @Former user (Deleted)for guidance on this - looks like some jjbs are missing and configs are probably wrong, too. | ||||||||||||
| 3 |
| Data-router not starting | @James Forsyth | IN PROGRESS | Assigned AAI-2727: aai-data-router not starting after a fresh installationClosed to @Steve Blimkie AAI-2730: Upversion to master staging versions in aai/oomClosed | ||||||||||||
| 4 |
| Cassandra 3 | @James Forsyth @Venkata Harish Kajur | DONE | SDC wants to move up to Cassandra 3 in the shared db environment. AAI-2731: Cassandra 3 UpgradesClosed https://old-docs.janusgraph.org/0.3.2/version-compat.html
| ||||||||||||
| 5 |
| 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?) | ||||||||||||
| 6 |
| AAI UI Issue | @Former user (Deleted) |
|
| ||||||||||||
| 7 |
| AAI Committers |
|
| @James Forsythwill ask @Catherine Lefèvreabout the status of a committer who has left the company (Tian Lee has left Amdocs, do we revoke committer status?) @Peng He is a potential committer on ESR (currently only Jimmy can commit ESR code) | ||||||||||||
| 8 |
| Code Test Coverage | @James Forsyth |
| Goal for Frankfurt is 55% AAI-Common 58.7 @Steve Blimkie will check with architects around the utility of champ and spike in the context of ongoing support in ONAP @James Forsyth will set them to read-only (gizmo, champ, spike) and El Alto will be the final release version of those microservicesAAI-2732: Lock gizmo/champ/spikeClosed @James Forsyth will remove the jenkins jobs on those repos AAI-2733: Remove jjb on gizmo/champ/spikeClosed sparky-fe https://lf-onap.atlassian.net/browse/AAI-2711 graphgraph AAI-2713: Sonar coverage report for graphgraph shows up but showing 0% coverageClosed | ||||||||||||
| 9 |
| Upcoming R6 Functional Requirements | @Benjamin Cheung | IN PROGRESS | Release 6 (Frankfurt) proposed use cases and functional requirements Use Case Realization Call: September 25, 2019 AAI-2600: A&AI support of Network Slicing Demo in FrankfurtClosed We have created REQ-158 -  for this use case. For AAI impacts, we have created AAI-2600 - A&AI support of Network Slicing Demo in Frankfurt.Reg. details of the AAI impacts, this is still being worked out, as there is an alternative proposal, and we are trying to align w.r.to scope & impacts. We will share more details in the coming days. The overall use case will also be presented to the Architecture Sub-committee for approval (based on the f2f discussions that happened in Antwerp 2 weeks ago). AAI-2670: AAI changes in support of 5G/OOF SON (PCI)Closed @James Forsyth No status yet, will ask on UCR call today https://lf-onap.atlassian.net/browse/AAI-2671 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. https://lf-onap.atlassian.net/browse/AAI-2672 @James Forsyth No status yet, will ask on UCR call today. Followed up, no representation from use case. Will look for response via email. https://lf-onap.atlassian.net/browse/AAI-2673 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. https://lf-onap.atlassian.net/browse/AAI-2674 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 depicts the run time view of Third Party Order Activation using the on-boarded service definition and highlights AAI impacts. 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 @James Forsyth Confirm on UCR call that this is object re-use and test only support from AAI https://lf-onap.atlassian.net/browse/AAI-2623 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 https://lf-onap.atlassian.net/browse/AAI-2678 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. | ||||||||||||
| 10 |
| 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 | ||||||||||||
| 11 |
| API | @Former user (Deleted) |
| Questions regarding how to use the api Sparky Running on Node Port: 30220 | ||||||||||||
| 12 |
| AAF / AAUI data preload | @Francis Paquette @Reneal Rogers | IN PROGRESS | Status on | ||||||||||||
| 13 |
| Search guard issue | @Giulio Graziani | ON HOLD | Merged and released yesterday; issue is closed. https://lf-onap.atlassian.net/browse/AAI-2617 Tracking for Frankfurt: https://lf-onap.atlassian.net/browse/AAI-2677 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 |
| NexusIQ | @James Forsyth | 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 | ||||||||||||
| 15 |
| ESR | @James Forsyth @Bo Lv | 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. https://lf-onap.atlassian.net/browse/AAI-2653 https://lf-onap.atlassian.net/browse/AAI-2640
| ||||||||||||
| 16 |
| AAI Openlab Tenant Space | @James Forsyth | 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. | ||||||||||||
| 17 |
| v17 schema for Frankfurt | @shashikanth.vh | 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? https://lf-onap.atlassian.net/browse/AAI-2607 See also AAI-CCVPN-Extension-SOTN Proposals for Frankfurt Release and https://lf-onap.atlassian.net/browse/AAI-2593 https://lf-onap.atlassian.net/browse/AAI-2594 already added some v17 files but needs more work to be complete. | ||||||||||||
| 18 |
| AAI Bugs | @James Forsyth | IN PROGRESS |
| ||||||||||||
| 19 |
| 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 https://lf-onap.atlassian.net/browse/AAI-2595 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 | ||||||||||||
| 20 |
| 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. | ||||||||||||
| 21 |
| GlowRoot | @James Forsyth @Venkata Harish Kajur | OPEN | Consider adding glow root profiling for AAI Microservices | ||||||||||||
| 22 |
| Performance Issue | @James Forsyth | 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"} | ||||||||||||
| 23 |
| Spring Boot 2 | @James Forsyth | IN PROGRESS | https://lf-onap.atlassian.net/browse/AAI-2111 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. | ||||||||||||
| 24 |
| Vetting DSL Queries | @Manisha Aggarwal @William Reehil | OPEN | Will discuss strategies AAI will employ to protect itself from rogue queries. | ||||||||||||
| 25 |
| New UI Features / Historical Tracking | @William Reehil @Manisha Aggarwal | 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 |
Open Action Items
New Action items