Recordings

Recordings require host password

Attendees - 

Goals

  • Get status on AAI lab resources
  • Discuss MSB/AAF and establish clear direction on approach for Beijing
  • Status on Cassandra clustering
  • AAI Administrivia

Discussion items


New contributor to the AAI Portal project

Kang would like to introduce a new developer, XiaoCheng, to contribute to the AAI Portal project

XiaoCheng is interested in improving the A&AI portal to show the logical relationship among instances. Service to models, instances etc.

Has done code analysis of AAI

No impact to other components

Liaise with Arul Nambi

Arul Nambi - would like to be included in planning/design/code submission.  Please add as reviewer.


CII Badging

Wiki page with instructions on the process: CII Badging Program


We have two CII Badging submissions currently active on CII Best Practice Badge Program: 1) AAI and 2) Sparky-fe


The team needs to decide how to split up the project - AAI is too big to fit under a single project.  James Forsyth proposes the following breakdown for CII badging:

1) AAI core (REST providers and common code): James Forsyth - Project created, ongoing progress.

  • aai-common
  • aai-resources
  • aai-traversal
  • gizmo
  • champ
  • aai-config
  • aai-data

2) GUI - Arul Nambi - Need to include more repos to the current "front-end" project

  • sparky-fe
  • sparky-be
  • data-router
  • search-data-service
  • router-core


3) Model loader - Tian Lee - Need to create projects

  • model-loader
  • babel

4) Graph utils / eventing / logging - Steven Blimkie - Need to create projects

  • spike
  • gap - Tian Lee
  • graphadmin
  • graphgraph - Stretch for Beijing
  • event-client - Tian Lee
  • rest-client


5) ESR - Zi Li - Project is created, still ongoing process to meet all the requirements

  • esr-gui
  • esr-server


The idea is that we assign one key person who will be responsible for getting the badge on their set of repos.  This is just a suggestion, and I invite discussion, re-categorization, and complete rewrites.



AAI-494 - Improve API Swagger Documentation IN PROGRESS

Issue 1 - Parsing of YAML file into RST format

Richard Epp to send yaml file via email to Pavel and attach to wiki so all can see.

YAML file too large and resulting RST file cannot be read by readmedoc causing it to be unusable.

Issues parsing the YAML file into RST format - structure is not correct - structure of YAML file must follow SWAGGER structure.


Issue 2 - Exposing AAI Swagger through MSB

Suggestion of using MSB portal with link of file to readmedoc.

How to display REST APIs via the swagger UI integrated with MSB: https://wiki.onap.org/display/DW/Microservice+Bus+API+Documentation#MicroserviceBusAPIDocumentation-APIDefinitionandSwagger-UI

Will need to continue as open item until resolved.

Contact Zi Li / HuabingZhao for more information about integration. Just require the swagger JSON file for integration - Richard Epp please provide the JSON to Zi Li -

https://wiki.onap.org/display/DW/2018-02-02+AAI+Weekly+Meeting+notes?preview=%2F25429783%2F25432551%2FNetwork_v13.yaml

Zi Li - please download the yaml file above and see if you can make use of it in MSB


Note: Alternate Swagger UI service already available.


Jenkins

Release jenkins jobs are still failing.  Helpdesk ticket # 52082

Changes to AAI-COMMON not picked up by downstream projects (resources, traversal)

Unable to release aai-common, as cannot release multiple times, without incrementing the version.

Liasing with ONAP helpdesk about whether we can release multiple minor versions of an artifact.


Proposal for Monday PTL meeting to align SNAPSHOT strategy

Venkata Harish Kajur to include Steven Blimkie on email exhange with ONAP Help desk.


HPA

I would like to discuss about the Persistence of HPA related information in A&AI in the weekly meeting call.

I would like to discuss my proposal to capture the HPA capabilities in a generic way in A&AI as

represented here à https://wiki.onap.org/display/DW/Persistence+of+HPA+related+information+in+AAI

I would appreciate if we could include this in tomorrow’s meeting.

Dileep Ranganathan presented   https://wiki.onap.org/display/DW/Persistence+of+HPA+related+information+in+AAI .  General discussion.

Alexander Vul met with OAF team yesterday to determine optimal way to consume info from A&AI, will go back

To OAF with using key value pairs; implementation needs to be agnostic and optimal.

Alex to post on wiki general format and value specifics; will meet with OAF on Mon on how to represent the values.


Alexander Vul to review changes with Christina for specific schema proposal

Functional requirements for HPA : https://wiki.onap.org/display/DW/Hardware+Platform+Enablement+In+ONAP


MSB Integration Status

The MSB AAF auth plugin
Two-way SSL at MSB API Gateway
Any problems in the integration

AAI-671 - Replace HAPROXY with MSB OPEN Opened questions to be answered

Might need a plugin in MSB to achieve stickiness of requests


Huabing asked Jonathan Gathman about AAF API - further details required.


Cassandra Clustering

Goal - provide HA to AAI


Issue 1 - remote storage

Meetings with Michael O'Brien - (deprecated as of 20170508) - use obrienlabs

OOM team should check the video recording of the session

@michaelobrien will arrange further meeting on Monday


Issue 2 - simulating outage

Pavel + Harish will try to simulate on Monday


We have a 3 node replicated cluster configured with local storage; need to discuss if this will be adequate to the purpose of Beijing integration testing.

AAI-539 - Set up Cassandra docker images in 3 node cluster OPEN OOM-591 - AAI needs persistent volumes configured, need help with OS in lab REOPENED

Michael O'Brien from OOM team will assist w/ OOM-591

Michael O'Brien to respond back to Harish’s email and setup meeting on Monday 10 AM; Will put on OAM discussion page so others interested can attend. 

https://lists.onap.org/pipermail/onap-discuss/2018-February/007954.html

https://lists.onap.org/pipermail/onap-discuss/2018-February/007955.html

ONAP on Kubernetes on Windriver Titanium Cloud - Openlab#Openlab-20180205:AAIandOOMworkingsessiononCINDERKubernetesPV

https://wiki.onap.org/download/attachments/25431372/20180205_aai_oom_cinder_kubernetes_pv_work_session_1_of_2_zoom_0.mp4?version=1&modificationDate=1517867225191&api=v2


Event-ClientTian LeeAuto-generated build jobs failing. Tian will investigate - update next week.

11 Comments

  1. James Forsyth Adrian Slavkovsky

    Session sticky is natively supported by MSB, no plugin needed.

    To achieve session sticky for a specific service, we just need to take the following items into consideration when registering the services

    1. Chose IP-Hash LB method in the k8s annotation
    2. Register at k8s Pod level rather than  k8s service(Cluster IP) level so MSB can do LB for the registered services

    The msb registration annotation should be in the Pod part of aai-deployment.yaml file rather than all-services.yaml

    Example:

    apiVersion: extensions/v1beta1
    kind: Deployment
    metadata:
      name: aai-service
      namespace: "{{ .Values.nsPrefix }}-aai"
    spec:
      selector:
        matchLabels:
          app: aai-service
      template:
        metadata:
          annotations:
            msb.onap.org/service-info: '[
            {
                  "serviceName": "aai-cloudInfrastructure",
                  "version": "v11",
                  "url": "/aai/v11/cloud-infrastructure",
                  "protocol": "REST",
                  "port": "8443",
                  "enable_ssl": true,
                  "lb_policy":"ip_hash"
                  "visualRange": "1"
              },
              {
                  "serviceName": "aai-cloudInfrastructure-deprecated",
                  "version": "v11",
                  "url": "/aai/v11/cloud-infrastructure",
                  "protocol": "REST",
                  "port": "8443",
                  "enable_ssl": true,
                  "visualRange": "1",
                  "lb_policy":"ip_hash" 
                  "path": "/aai/v11/cloud-infrastructure"
              }
              ]'
          labels:
            app: aai-service
          name: aai-service
        spec:
          initContainers:
          - command:
            - /root/ready.py
         --- omitted for brevity----
  2. Regarding Auth Plugin:

    AAF support Basic Auth, but they don't provide REST APIs for authentication/authorization right now. We need to wait until the APIs are defined.

  3. Tian Lee and Arul Nambi, by "reviewer" are we suggesting promoting Arul as an AAI committer?

    1. Being a committer is not a necessity for reviewing code, but that is not to say that I'm against the idea.

      What is our current quota for committers under the AAI project?

      1. No specific quotas and I think we should be flexible in adding as needed.  If Arul Nambi wants to be included on code reviews I can include him when I am going through the set of watched changes; assuming he'd want the ones that are related to sparky, or does he want all of them?

        1. I think it was agreed that xing xiaocheng should make sure that Arul is added as a reviewer when he submits his changes. Xiaocheng will also be working closely with Arul in the development process.

          1. Hi James Forsyth & Tian Lee,

            As Tian Lee mentioned, I have asked to be included in the design and implementation of the change that xing xiaocheng will be doing to the AAIUI to make sure that it stays in sync with our current features and future plans for the UI.

            Regarding becoming a committer, I would like to become one. The reason for that is there is a need for a committer with knowledge about sparky in general, react and js to approve the changes. And current committers are waiting on someone with UI expertise to approve(review) the code. This leads to un-necessary delays. I talked with other UI developers and they agree with what I said, and we wanted to see if I can become a committer. I think that will reduce the time taken to approve a change to UI. Also with my involvement in security committee it will be an added benefit.


            1. I agree that we have a deficit in front-end expertise in our committers group, and now that the AAI UI is an integral part of the product offering, I think front-end knowledge would be a welcome addition to the committers team.

      2. I think having Arul as a committer makes a lot of sense.  I think he brings some expertise that is currently missing among our committers, and would be well suited to help drive the evolution of the UI.