Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Recording:


Attendees:

James Forsyth

William LaMont

Tian Lee

Venkata Harish Kajur

CT Paterson

Dileep Ranganathan

Francis Paquette

Michael Arrastia

Ondrej F

Former user (Deleted)

Giulio Graziani

Steve Blimkie

Marek Kukulski

Shirley Morgan



START RECORDING


Support for 2 OOM deployment types

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

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 13 June: Is it necessary to encrypt services behind the reverse proxy (msb/haproxy/kubernetes ingress controller)?

Update 11 July: Yes, it is. AAF is providing a new simplified client and new instructions for setting up AAF in the labs by the end of the week

Currently AAI is using HTTPs w/ Basic Auth. SECCOM is recommending 2-way TLS with CADI. Jonathan Gathman will issue certificates - unsure if all devs can/should request a cert from AAF for dev/test. AAI will evaluate if the new client and documentation is adequate to build a service with AAF + 2way TLS in time to socialize it to clients - if we can't deliver a working system w/ 2 -way TLS by M3 (API Freeze) we'll continue to use Basic Auth and load the existing credentials into AAF.

With HAPROXY, the client cert subject and issuer are placed in HTTP headers and passed along to the service. The service can send the DNs of the subject + issuer to AAF, and AAF will determine if the client is allowed to access the resource.

Update 18 July:  Documentation expected to be available next week, awaiting additional information from AAF.

Update 25 July: Former user (Deleted)will look At HAProxy with AAF; Venkata Harish Kajur will send demo link to Former user (Deleted).

Update for 15 Aug: Blocked by AAF-427 - Unable to create a user with password Open . Sparky-fe might be impacted by changes in the way AAF is used by the portal app. Members of the AAI team who work on the UI will attend the portal calls (Wednesdays @ 1500 UTC) to see if there is code impact due to the portal AAF updates.

Update for 5 Sep:

AAF Integration description


  1. Who creates the roles and permissions during the new release, who and how maintains these AAF scripts? James Forsyth will ask Jonathan Gathman about including role/permission setup script as part of AAF bootstrap or should we have a startup script that calls the AAF REST API to update the roles and permissions.
  2. DNS entries for aaf-onap-beijing-test aaf-onap-beijing-test.osaaf.org aaf-onap-test.osaaf.org
  3. OOM config?


PNF PnP Use Case

CCVPN Use Case


SpringbootCasablanca using 1.5.15

NexusIQIssues need to be remediated or have a plan before M4.

Node Port Exhaustion in OOM

https://wiki.onap.org/display/DW/OOM+NodePort+List


HPA Telemetry

Christina Monteleone suggested the compute node data could be stored in the pserver type instead of creating a new type. Open question about who creates the pserver in ONAP, James Forsyth needs to track down the component that is responsible. Need to add a relationship between flavor and pserver. Add new HPA Telemetry types to the schema and create edges between them and the pserver. Limit on attributes of vertices might be around 2k, Venkata Harish Kajur will check into it. James Forsyth will follow up on https://gerrit.onap.org/r/#/c/58175 with Christina Monteleone


A&AI REST services

Why don’t we use DMAAP to communicate with other systems (inbound and outbound) but we do it through a REST API? If we use DMAAP, we wouldn’t need a proxy, it would be easier to scale services and we would have a looser coupling between

Update 24 Aug

Proposal reviewed by: James Forsyth, Venkata Harish Kajur, Robby Maharajh, Former user (Deleted)

Conclusion: It is better to use REST as opposed to DMAAP in A&AI.

Reasons:

  1. The DMAAPs messaging system is unstable (message loss and duplication observed in the past)
  2. DMAAP is much more complicated compared to REST
  3. It is too costly to change A&AI clients from REST to DMAAP

Checking license headers in automatic build is wrong

Checking license headers in java files is wrong. I get the following message

 Failed to execute goal com.mycila:license-maven-plugin:3.0:check (default) on project aai-resources: Some files do not have the expected license header ....

When I change

* Copyright © 2017-2018 AT&T Intellectual Property. All rights reserved.

to

* Copyright © 2018 Orange Intellectual Property. All rights reserved.

Is only AT&T header allowed or the script that checks it is misconfigured?


HEAT deployment issuesWe think we have all the mS building; once we've proved that a HEAT based deployment works in our local test env, we'll push updates to the test-config for the new versions of the mS

SONAR coverage on new reposLine coverage on graphAdmin is currently at 28%. In the next sprint, the plan is to move the coverage up considerably; goal for Casablanca is 50%.

5G PNF Software upgrade

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


GraphGraph
GraphGraph is an aai schema/model visualization system for which an early prototype has been built as part of ECOMP.

R3 Casablanca Commitments

AAI R3 M1 Release Planning

Update 18 July:  wiki page to reflect Casablanca deliverables.

AAI R3 M2 Deliverables for Functionality Freeze Milestone Checklist

Venkata Harish Kajur working to complete the M2 milestone template


Platform Maturity Requirements for Casablanca

Reviewed recommendations from the ONAP F2F meeting - Jason Hunt's slides are here: Casablanca Release Developers Forum Session Proposals

AAI R3 Platform Maturity


API Versioning

AAI is considering the ONAP API Common Versioning Strategy (CVS) Proposal in Dublin

AAI-1185 - Versioning for ONAP Components with Backward Compatibility Open

Christina Monteleone invited to next week's meeting to discuss the restructuring.

Update 6 June: API Versioning has been moved to 1902 release.

Update 18 July:  Moved to Dublin release


Datagrooming
Andrew Muller and Former user (Deleted)

Champ is coming in Casablanca and will serve as the graph abstraction layer used by resources. Duplicates and other badness happens when multiple nodes are operating on the same objects concurrently. We need to investigate how to use potential locking features or other mechanism to prevent duplicates. Steve Blimkie will look for volunteer inside Amdocs to look for an owner of an Epic that James Forsyth will open in JIRA for Casablanca.

The Datagrooming tool recognizes bad data like duplicates and "phantom nodes"

Venkata Harish Kajur to create a US to document the datagrooming steps/parameters for Beijing.


Casablanca

We'll discuss upcoming Casablanca requirements, get a brief status on the Historical Data Tracking feature.

Update 13 June: Face-2-Face Beijing conference next week; Functional use cases (Schema enhancements), new node types, non-functional requirements and code coverage (70% - 80%) will be output from conference; Evaluate the Kubernetes Ingress Controller as replacement for HAProxy; integrating the services with AAF using Cady.

Update 18 June: Evaluation of Ingress Controller



PNF Plug and Play w/ A&AI in Casablanca

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.

...