2020-01-08 AAI Meeting Notes

Attachments (including meeting recording):

Attendees:

@James Forsyth

@William LaMont

@Ondrej F

@Giulio Graziani

@guochuyi

@Zhang Qingjie

@Chuanyu Chen

@shashikanth.vh

@Shirley Morgan

Status	OPEN	IN PROGRESS	ON HOLD	DONE	CANCELLED

Status	OPEN	IN PROGRESS	ON HOLD	DONE	CANCELLED

START RECORDING

1	Discuss developers call time	@James Forsyth	OPEN
2	SO query in AAI	@shashikanth.vh	IN PROGRESS	NNI Use Case - discovering 2 topologies from the network Use case is asking for the ability in AAI to link an underlay and overlay together by having a cousin relationship between 2 PNFs. Asking @Chandra Cinthalato verify if that edge rule can be added for the Frankfurt release. 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 I agree but in case of network hierarchy traversing is not possible because p-interface of underlay node and p-interface overlay node are not same. cannot traverse to underlay node referring to p-interface of overlay node. overlay node has to maintain relationship with underlay node. for ref: https://www.rfc-editor.org/rfc/rfc8345.html#page-14 section 4.1
3	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
4	E2E Network Slicing	@LIN MENG	OPEN	For the E2E Network Slicing use case for Frankfurt Release, we intend to leverage the nested service model work that has been going on since Dublin release. From A&AI perspective, we foresee that the schemas would have to be enhanced to cover network slicing models. We have considered A&AI to be a stretch goal for Frankfurt, though we are committing resources. So, we would like to start the discussion in the coming weeks, and subsequently implementation work to try our best to complete the implementation for Frankfurt. AAI-2600 has been created just to indicate the SDC impacts, we will update it with more details, and also join the A&AI weekly call during the next 1-2 weeks to discuss further.
5	Portal SDK Upgrade	@James Forsyth	OPEN	https://lf-onap.atlassian.net/browse/AAI-2726 @Francis Paquette need evaluation of feasibility in Frankfurt for sparky
6	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? Graphgraph was removed from the default helm chart, but we still need to get these jobs fixed. @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. @Ondrej F will reach out to Pavel and see if we can figure out why the build and stage jobs are failing.