2019-06-21 Meeting notes

Date

Jun 21, 2019

Attendees

  • @Adolfo Perez-Duran

  • @cristinapauna

  • @Paul-Ionut Vaduva

  • @Former user (Deleted)

  • @Simon Hrabos (Deactivated)

  • @Brian Hedstrom

Goals

Discussion items

Item

Who

Notes

Item

Who

Notes

AAI

  • Testing

AAI's PTL suggested relying on healthdist to validate our contributions by following this wiki page 

https://lf-onap.atlassian.net/wiki/display/DW/Creating+an+installation+cross+component+health+test

In a nutshell, if healthdist passes, he's ready to accept the patches.

  • CSIT

Although the tests seem old, they are still valid because AAI hasn't changed a lot.

  • Support

Jimmy has offered to help answer questions we may have about interpreting the results of tests.

  • Plan

    • Perform a minimal installation of recent ONAP containers (Martin)

    • Configure and perform a healthdist test (Martin)

    • Test non-minimal AAI containers manually (Dmitry)

    • Compare results to previous attempt (Dmitry)

    • Run CSIT AAI TCs with recent AAI containers and document errors (Martin & Dmitry)

    • Create a issue for the AAI team if needed (Martin & Dmitry)

  • Testing model loader seems promising

  • Minimal ONAP installation was installed

  • Will reproduce healthdist with minimal images

  • Dmitry was able to test manual loader test (wiki was missing a piece of info)

  • Will test minimal container next week – must incorporate latest changes to containers

 CLAMP-OOM



  • Although there is an initiative to move to a common elk stack for all ONAP projects, the initiative relies on the logging project.

  • The logging project uses a standard format, so any other storage and graphing solution could be used.

  • ONAP deployments could use ELK stack alternatives that run on arm.

  • Rather than pursuing a patch within ONAP, we should look for arm-compatible alternatives.

  • @Tina Tsou (Deactivated) has been informed of the need and asked to follow up with the arm team

LCM Proposal



  • Proposal

    • Presented to the TSC and the work was encouraged to proceed (no vote could take place)

    • Team should consider the PoC alternative if it becomes necessary

    • Mirror: LFN infrastructure team not willing to set it up yet

    • Team could consider socializing simpler alternatives such version pinning

  • Support

    • CLAMP and NBI projects will participate in the initiative

  • From images to normative images

    • Adoption of proposed images requires commitment from the community

    • Usage can be 'enforce' during the build process using linting

    • Library has been identified

  • Next steps

    • CIA PTL to engage Sylvain and Christophe

  • Orange will support the use of linting

PTL Election Process



Defined by ONAP Charter

Action items