2018-11-07 AAI Meeting Notes - open for agenda items

Bell Canada has a requirement to migrate their A&AI Graph DB backend from HBase to Cassandra.

We are enabling this effort.

We have been investigating GraphAdmin code in ONAP, which seems to support the framework.

We would like to make enhancements to this framework and contribute to ONAP.

The initial enhancements we would like to accomplish are:

• Provide option to the end-user to select FROM and TO Version
  • The current code doesn’t have this option
• Support schema migration to V14
  • Current support exists for V11->V13

Our goals:

• AAI backend upgrade from HBase to Cassandra (V11 to V14)
• Seamless upgrade and rollback of AAI DB

Example:

<xml-properties>
<xml-property name="description" value="Logical interfaces, e.g., a vnic."/>
<xml-property name="indexedProps" value="macaddr,interface-id,interface-name,network-name"/>
<xml-property name="dependentOn" value="generic-vnf,newvce,p-interface,vserver,lag-interface,l-interface"/>
<xml-property name="container" value="l-interfaces"/>
<xml-property name="uriTemplate" value="/l-interfaces/l-interface/{interface-name}"/>
<xml-property name="requiredProps" value="interface-name,is-port-mirrored,in-maint,is-ip-unnumbered"/>
</xml-properties>

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 AAI changes in support of 5g use cases.

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

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.

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.