2018-10-31 AAI Meeting Notes

Daylight Savings Time

Update 31 Oct:

AAI meetings will be adjusted for US daylight savings. @James Forsyth will verify that the community meetings page on the wiki accurately reflects the end of Daylight Savings

Release versions

Update 31 Oct:

@Steve Blimkie and @James Forsyth will release Amdocs microservices today and request casablanca branching.

Weekly Developer's Call

@James Forsyth

@James Forsyth will create a new poll: https://www.timeanddate.com/ and send link to new poll to the onap-discuss list

https://doodle.com/poll/t2c7md2kv9x7cdzx

AAI Developers Meeting

@CT Paterson suggested a chat tool like Slack for asynchronous group communication - Rocketchat is in use by the integration team and might be a good choice (http://onap-integration.eastus.cloudapp.azure.com:3000/group/onap-integration?)

Tomorrow, Oct 25 2018 will be first dev session - zoom id 654 321 5891. @Former user (Deleted) has volunteered his personal zoom until the LF adds the community meeting to the calendar.

5min

AAI UI documentation or user guide

@Keong Lim

Recently updated AAI Graphical User Interface due to colleagues wanting to use the AAI UI.

Is there a more comprehensive and authoritative documentation or user guide for AAI UI?

The main issue is that it is not clear how to get started - @Francis Paquette will look at what's on the readthedocs site, I think we need to port what Keong has put in the wiki to the main docs repo at a minimum.

CII Badging

Open

Fill out CII Silver Badging Template. We have not committed to a silver badge, but the community wants us to fill it out to the best of our ability.

IQ Vulnerabilities

Thank you for providing the feedback for AAI known vulnerabilities.

I do agree with your comments on the wiki, however I would like to encourage you to provide your feedback for the remaining vulnerabilities that are available on the Nexus-IQ  but unfortunately not included on your Wiki.

If needed, we can have a short call together to review remaining vulnerable components (I hope the list is complete):

tomcat-catalina : 8.5.23

tomcat : zip : 8.5.23

tomcat-util : 8.5.23

tomcat-websocket : 8.5.23

netty-all : 4.1.0.CR3

cxf-rt-transports-http : 3.2.2

Update 18th Oct:

• aai\esr-gui\httpserver\pom.xml specifies "<tomcat.version>8.5.23</tomcat.version>"

• aai\esr-gui\pom.xml specifies "<tomcat.version>8.5.23</tomcat.version>"

• netty-all version "4.1.0.CR3" does not appear to be anywhere in the current AAI codebase (old reference?)

Dublin 5G Use Case

@Benjamin Cheung

Dublin AAI changes in support of 5g use cases.

Link for presentation: 5G - PNF Plug and Play (Casablanca carry-over items)

Schema Service

@Venkata Harish Kajur

Discuss about the Schema Microservice

11th Oct: Use Cases for Dynamic AAI Schema Changes

Jackson Replacement

Team

@Keong Lim

@Tian Lee

Security subcommittee has recommended teams move away from jackson, and will be presenting alternatives and asking for an assessment from each project. Our team will need to do an analysis - this would not be trivial, especially given how many of our repos are impacted. As of now, this would be a very high LOE for the team, we need to understand what the recommendation from the SECCOM is before we can provide better details on what the LOE would be.

Updated: Using Google gson vs FasterXML Jackson

10th Oct: Present to Seccom meeting

15th Oct: Present to PTL meeting

24th Oct: Move discussion to AAI Developers Meeting

@James Forsyth

@James Forsyth will add this to the PTL call agenda for Monday 4 Nov

XSD generation

@William LaMont

@James Forsyth

Multi-oxm. There is limited auditing which shows warnings, but we might want to review the requirements around multi-oxm to prevent collisions.

Support for 2 OOM deployment types

@Former user (Deleted)

Motivation: Decrease the resource footprint for A&AI (ONAP) deployments

Idea: we could support 2 different deployments 1. full (normal) deployment and 2. barebones deployment. The point of the "barebone" deployment would be to deploy only the essential services necessary for proper functioning of A&AI (leaving out services like cacher, sparky, graphadmin, having 1 cassandra node instead of 3 or 5 etc).

In order to reduce hardware/cloud costs (mainly the memory footprint) it could be beneficial to support a minimalistic A&AI deployment.

AAF and TLS in Casablanca

@James Forsyth

The AAI team needs a strategy for integrating with AAF and AAF certificate manager, including potentially using 2-way TLS in R3.

AAI-32 - Integrate with AAF Open

Update 6 June: Andy Baxter provided presentation

Update 17 Oct: It works! First successful deployment of the AAI profile in OOM.

Need to make it permanent once AAF is stable.

Update 24 Oct: @Former user (Deleted) will add a feature enhancement request in AAF to provide better logging facilities so we can configure AAF logs rather than logging directly to STDOUT.

AAI-1760 - [resources and traversal] Make the AAF profile active in OOM by default Open

5G PNF Software upgrade

@wangyaoguang

@Benjamin Cheung

We have a 5G related functionality in Change management, 5G PNF Software upgrade. https://wiki.onap.org/display/DW/5G+-+PNF+Software+Upgrade. 

Right now, PNF software version is modeled and accepted in SDC, and also approved in Modeling subcommittee and TSC.https://wiki.onap.org/display/DW/TSC+2018-07-26+Meeting+Agenda. (Modeling report)

We are not familiar with A&AI. The target of this functionality is to  update PNF Sw version when upgrade completion with specified pnfid. Could you and your team give us some help on this?

1)      Is there any available  APIs provided by AAI for this? 

2)      If yes, can you give me some details on it. If not, could you and AAI team provide support in Casablanca? We would like to provide contributions if needed.

@wangyaoguang to follow-up with SDC team and send conclusion results to @James Forsyth

PNF Plug and Play w/ A&AI in Casablanca

@Benjamin Cheung

PLUG AND PLAY USE CASE WIKI: 5G - PNF Plug and Play

A&AI ENTRY FOR PNF PnP: 5G - PNF Plug and Play#5G-PNFPlugandPlay-STAGE2-PNFA&AIENTRYUSEDBYPNP

There are a number of A&AI topics:

1. GEOLOCATION - Suggested from the PNF Modeling discussions. It was counter-suggestion (form A&AI) was to use the COMPLEX Object. Some members of the PNF Modeling group still have questions about how this would work exactly.

2. DETECTED SOFTWARE VERSION LIST - (this is already a tracked item above)

3. CLOUD HOME - CLLI Code for Cloud homing of the PNF. Counter-suggestion (from A&AI) was to use the COMPLEX Object. However, the modeling community was not satisfied with this suggestion.

4. MANAGER IP ADDRESS - Modeling in A&AI parameters for the Manager of the PNF. Counter-suggestion (from A&AI) was to model the NMS as a NF. Modeling community thought that the Manager IP address was more appropriate, simpler, more succinct solution instead of modeling the NMS as a NF.

5. S/W IMAGE REPOSITORY - Location where NF Software repository is. Would be a URL/Web address.

CII Badging

@James Forsyth

Wiki page with instructions on the process: CII Badging Program

Need updates on the CII badging for ESR