Versions Compared

Key

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

...

RC2 is tomorrow. We have 1 remaining high priority defect: Image RemovedAAI-1136 - Babel doesn't start in HEAT due to log directory permissions Submitted


S3P Requirements for CasablancaJames ForsythReviewed recommendations from the ONAP F2F meeting - Jason Hunt's slides are here: Casablanca Release Developers Forum Session Proposals

Open Beijing Bugs

Timeouts in the lab have resulted in a blocking defect assigned to AAI

Image RemovedAAI-1184 - vCPE service distribution to AAI failed in OOM-deployed env Closed

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

Docker Image Release version

James Forsyth intends to request docker image release versions for all services today, 30 May 2018 - done

Release Date

RC2 is tomorrow, release date is 7 Jun 2018 - AAI passed

Update 13 June: Beijing Press Release went out yesterday.

BranchingBeijing branches are cut by LF, need to bump all AAI repos to 1.3.0 and set up jjbs for the beijing stream - once complete, we will open the repos to contributions for Casablanca. Rethink branching for Casablanca code freeze / dublin start.


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.

Model-loader

Update 25 April: James Forsyth will create how to document on wiki.  Instructions to include: access to windRiver lab, logging into system, pulling the dockers from A&A&, how to run OOM and start the mS. - Done Openlab access for AAI devs

Update 2 May: James Forsyth will reach out to Victor and Shankar on access to A&AI lab

Update 16 May: Openlab AAI instance built, new instructions here: Using AAI in Openlab

OOM

Update 25 April: James Forsyth and Venkata Harish Kajur to audit what is currently running then setup multiple nodes that can be used for testing; space defined and coordinated within the team; will work it offline and then share with the team via the wiki. - Done Setting up AAI in Openlab

Developer Setup GuideNext Milestone: RC2Duplicates in DBI have created a script (based on Bill Pezzutis pseudo code) that eventually creates duplicates of entities. Some REST endpoints (GET,DELETE) for the duplicated entity stop working properly. Let's discuss as a team potential mitigation strategies and clean-up tools

.


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

Versioning

Former user (Deleted) made a cool script to compare what's in nexus vs. what's in git - it's very cool, thanks, Pavel!

...