Versions Compared

Key

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


Recordings:

Recorded Session 2018-06-27

Goals

  • Upcoming milestones
  • Release artifacts
  • Documentation

Discussion items

START RECORDING


PTL ElectionJames Forsyth

PTL elections can be held the week of 2 July 2018. AAI Committers are eligible to vote. PTL term is 1 year.

Casablanca Release Developers Forum Session Proposals


PTL VacationJames Forsyth

AAI PTL will be on vacation from 16 July - 27 July 2018. The AAI team will need a delegate to run the Wednesday calls during this time and attend the following calls:

Mondays: [ptls] Group ONAP1, Mon UTC 13:00 / China 21:00 / Eastern 09:00 / Pacific 06:00

Thursdays: [onap-tsc] TSC Meeting ONAP1, Thr UTC 14:00 / China 22:00 / Eastern 10:00 / Pacific 07:00



R3 Casablanca CommitmentsJames ForsythAAI R3 M1 Release Planning

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.


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


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

PROSCONS
  • helm installation with many customizable options
  • easy change and update of routing and config (changing a YAML file)
  • very low maintenance

  • becoming standard in kubernetes

  • easy to expose services outside kubernetes

  • no fine-grained control over different routes within controller
  • might lack some configuration options in comparison with a custom proxy
  • TLS certificates provided through kubernetes

  • obviously not available in docker-only environments
  • current HAproxy adds 14 custom headers - need to look if controller can provide the same headers

Open questions:

  1. Do we need these custom headers in A&AI? They are used only in logging in the resources microservice, no use in code or anything (maybe I missed something?)
  2. Where will we use certificates (proxy/microservices/both)?
  3. Will we use client certificates, if yes who evaluates them (proxy/microservices)?

...