Attachments (including meeting recording):
| Attachments |
|---|
Attendees:
| Status | OPEN | IN PROGRESS | ON HOLD | DONE | CANCELLED |
|---|
START RECORDING
| 1 | 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 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
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 2 | Search guard issue | Giulio Graziani | OPEN |
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 3 | Use-case modelling | OPEN | How is the heat load-balancer CDS use-case being modeled in A&AI? What is being mapped to the generic-vnf, vnfc and vf-module? What is the relationship between vnfc and vf-module? For example in case of the vFW there are 2 vf-modules being instantiated (one for packet generator and the other for vFW) and they are being modeled as 2 generic-vnfs. Are there any guidelines on modeling heat use-cases? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 24 | ESR | OPEN | 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.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 35 | NexusIQ | OPEN | 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 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 46 | AAI Openlab Tenant Space | OPEN | 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. | 5 | Upcoming R6 Functional Requirements | Benjamin Cheung | IN PROGRESS | Release 6 (Frankfurt) proposed use cases and functional requirements | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 67 | AAF / AAUI data preload | OPEN | Status on
| 7 | Search guard issue | Giulio Graziani | OPEN |
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 8 | 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
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 9 | AAI Bugs | IN PROGRESS |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 10 | 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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 11 | 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.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 12 | GlowRoot | OPEN | Consider adding glow root profiling for AAI Microservices | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 13 | 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"} | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 14 | 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 15 | Vetting DSL Queries | OPEN | Will discuss strategies AAI will employ to protect itself from rogue queries. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 16 | 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 |
...