Page History

https://gerrit.onap.org/r/c/aai/schema-service/+/102298

https://sonarcloud.io/organizations/onap/projects

1

Network SplicingAAI CNF Modeling

OPEN

Chuyi Guo 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. Chuyi Guo & dhebeha mj have the action items to share the decks with William Reehil who will solicit input from @David Whitney and Chandra Cinthala AAI proposal on E2E Network Slicing for R7-V1.2.pptx

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

AAI ← link to the AAI weekly CNF call. This team will be doing modeling work to decide how CNFs will be modelled in AAI

2

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

DONE

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. William Reehil was voted in as the new PTL.

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.

3

Guilin requirements

OPEN

AAI R7 Guilin Release: TSC must have requirements AAI R7 Guilin Release: Functional Use Cases

4

Requirements for inclusion of GraphGraph in Guilin release

OPEN

List goes here Open Jira tickets as tasks for G 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

6

Guilin non-functional proposals

OPEN

Focus on seccom requirements done first, fixing haproxy No root user in the docker - use integration team guidance for setting a USER in the Dockerfile rather than gosu (see aai-resources) and fix haproxy. We might consider adding aaiadmin to the base image, and then just set USER aaiadmin in Dockerfile Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI- 2822 Move haproxy functionality into k8  2913

5

Document AAI repo and microservice descriptions

Ondrej

OPEN

Move aai/oom chart back to oom Put the link here for the document; we will share with the community and solicit feedback from repo/mS owners about the document. Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI- 2914 Move to Spring boot 2 (aai-parent inherits oparent:2.1.0) Java 11 (oparent 3) - need to consider downstream dependencies on ONAP carrier partners Use AAF certificate manager Remove all hardcoded secrets AAI needs to be able to run without AAF (means no HTTPS) Upgrade to latest versions of 3rd party dependencies - EclipseLink and gremlin Better coverage on javascript repos (graphgraph and sparky-fe) Commit to a % increase in code coverage SONAR bugs / security / code smells Platform maturity - performance testing (Bell Canada has interest; if test suites could be upstreamed there could be resources to help us move our PM metrics up) Security assurance document for CII badging Guilin release - non-functional requirements proposed list 2924

6

Frankfurt Defects

Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = AAI and type = Bug and status != closed and fixVersion = "Frankfurt Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb

7

SOTNNI use case

Shashikanth VH

https://gerrit.onap.org/r/c/aai/schema-service/+/102298

8

Security Requirements for pods

James Forsyth

Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-215

9

Ondrej Frindrich

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.

10

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

11

Looking for volunteer to fix papyrus issue

OPEN

Jira server ONAP

7

Guilin Functional requirements proposals

OPEN

R7 Use Case Realization Meetings 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

List goes here Open Jira tickets as tasks for G 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

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. Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-29242771 Graphgraph doesn't parse the latest AAI schema correctly.  Need someone to investigate

12

sparky and data-router certificate issue

Francis Paquette

IN PROGRESS

10

Frankfurt Defects

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.

Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-2765 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = AAI and type = Bug and status != closed and fixVersion = "Frankfurt Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb

11

SOTNNI use case

Shashikanth VH

12

Service model and schema impact

Benjamin Cheung

13

Security Requirements for pods

James Forsyth

Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-215

14

Ondrej Frindrich

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 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

16

SONAR coverage report

James Forsyth

DONE

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:

• LF does no longer mark warnings in the reports, only pass or fail
• LF is no longer able to manage individual quality profiles per language. Whatever latest support is there, we fetch this automatically in our side.
• Jacoco plugin has changed quite a bit, we need to make sure our reports are now xml based instead of exec. I think this can be the main reason why you are facing coverage drops. Can you please check? This is what Sonar mentioned to me in detail: 
  • https://community.sonarsource.com/t/sonar-coverage-dropping-to-0-for-some-projects/18521/2

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.

 2 Spring beans with the same name is disallowed in Spring boot 2

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.  

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

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"}

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

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."

•  Shashikanth VH will let the AAI team know if that solves the problem

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

SDC wants to move up to Cassandra 3 in the shared db environment.  

https://old-docs.janusgraph.org/0.3.2/version-compat.html

sparky-fe 

graphgraph 

Release 6 (Frankfurt) proposed use cases and functional requirements

Use Case Realization Call: September 25, 2019

•  James Forsyth No status yet, will ask on UCR call today

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.

•  James Forsyth No status yet, will ask on UCR call today.  Followed up, no representation from use case.  Will look for response via email.

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  Image Removed 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

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:

• PNF and VNF models contain status attribute that can indicate when a new instance has been fully instantiated (may still require update to SO workflow)
• AAI will send topology event on AAI-EVENT topic when status attributes are updated

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

•  James Forsyth Follow up on URC call today

Questions regarding how to use the api

AAI Graphical User Interface

Sparky Running on Node Port: 30220

AAI Schema Service

AAI Schema Service Use Case Proposals

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

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.

Consider adding glow root profiling for AAI Microservices 

https://glowroot.org

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"}

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

Need to raise potential risks due to resource constraints on Guilin release on some non-functional requirements Guilin release - non-functional requirements proposed list

Create tickets for G release off of

epics for A&AI impacted areas, assign resources if available, raise risks if not

Open questions on  Image RemovedREQ-361 - Continue hardcoded passwords removal TO DO