PTL 2019-04-22

Owned by Former user (Deleted)
Last updated: Jul 12, 2019
5 min read

zoom bridge: https://zoom.us/j/283628617

PTL RecordingsZoom Chat Log

Duration 60 minutes

DurationAgenda ItemRequested byNotes / Links
START RECORDING
5minCasablanca maintenance release status

Yang Xu

Mike Elliott

#1 (Yang): Update the Manifest on Readthedoc

#2 (Mike): Tag the release and will add the version in Helm Chart.

Expected sign-off: 2019-04-25

Yang reports that the basic test show 3.0.2 is OK and the manifest is updated - he asks the community to test 3.0.2 RC it as well.

15min

Dublin end game plans

Former user (Deleted)

RC0 date - 2019-05-02

RC0 templates due - 2019-04-30

  • RC0 milestone checklist
  • No "Submitted" state Jira stories related to code development
  • Complete pair-wise testing weather board and create your individual project pair-wise testing page
  • Integration team to flag failing OOM healthcheck/container restart/pair-wise test for review in weather board
  • Expectation of closed out jiras for Documentation 

Yellow status Release Requirements - move to POC by 2019-04-22 COB

Critical defects - please stay on top of the merges

Yang: Community does not get a chance to give feedback in late cycle - basically insuring a maintenance release immediately following the Sign-Off. Would like 2 wks from RC2 to sign-off/GA?

10min

Dublin Vulnerability review - SECCOM

Projects not yet reviewed

Paweł Pawlak

Using Jira tickets for vulnerabilities that need attention. Tracking the release wide vulnerability table review process here: /wiki/spaces/SV/pages/16090768
5minNexusIQ demoPaweł Pawlak

Offline meeting recording: NEXUS-IQ tutorial 17042019.mp4

If you need more help reach out to Amy Zwarico

10minLicense scans review - WinslowSteve Winslow
 <DOWNLOAD the spreadsheet - preview in wiki doesn't work as well>

Process: 

Prior to release the TSC legal subcommittee reviews and approves any license exceptions in dependencies. Steve has reached out to the projects that are using licenses that are not generally accepted. Reach out to swinslow@linuxfoundation.org 

What about binary files in the repo?

Generally not desired - especially a compiled binary as license terms can be obfuscated.

CSAR files for testing? Inside the files there are "proprietary notices" - that's what raises flags.

Zoom Chat Log


Action Items

  • 2/11: Migrate Docker image releases from Nexus3 into Docker Hub (Architecture Independence) by Dublin M4. 
    <2-15-2019> Preparing a preso for review of all known infrastructure change requests for review at PTL meeting 2-25-2019
    <2019-04-08: global-jjb progress report: start on DCAE soon - focus on El Alto delivery (precursor to Dockerhub)<2019-04-22 - Using mvn staging plugins to deploy - unfort many of the changes need to be in the source code to insure the job is running>
  • Oom values.yaml or integration repo manifest ( TSC-86 - Lock down docker image tag name source of truth - oom values.yaml or integration repo manifest - A: both but manifest is the source SUBMITTED ) Michael O'Brien

    if not covered - see TSC 2019-01-10

    Quick discussion on nailing down whether we need a yaml override of the deployable

    docker image tags in the oom repo (understanding is no) - with the integration docker manifest

    (manifest is currently a copy of the oom values.yaml tags - not the reverse)

    If not - then we need a documented procedure wiki/RTD on running a derived values.yaml override for the entire system before deployment

    AAF is only an example here

    https://git.onap.org/oom/tree/kubernetes/aaf/charts/aaf-service/values.yaml?h=casablanca#n28

    image: onap/aaf/aaf_service:2.1.8

    drives

    https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=casablanca#n11

    onap/aaf/aaf_service,2.1.8
    20190318: discussed discrepancy with Orange in OOM call last week - manifest is still in use to manage versions until merges come into OOM from the teams and we finish the architecture of the merged manifest in oom

    OOM Meeting Notes - 2019-03-13

    <1-7/2019> Integration team to document the procedure.<01/13/2019> Answer from Integration team: docker manifest under integration repo is the source of truth, and is used by Integration team to override OOM values.yaml when deploying ONAP in Openlab. See the instructions at the bottom of page https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/onap-oom-heat.html#onap-oom-heat-template
    <1-21/2019> Procedure should include Timers, dependencies, etc.
    just need to define all the --set and -f overrides like the following 

    sudo helm deploy onap local/onap --namespace $ENVIRON -f $DISABLE_CHARTS_YAML  -f $DEV0_YAML $APPENDABLE_ENABLED_FLAGS --verbose

    <1-28-2019>: Document how to handle the latest 3rd party image from github.
    <2019-02-19>: One over-ride that will be shared, parent over-ride for docker versions, Michael O'Brien to modify TSC-86 to reflect process. Still looking at tool to institute changes for all projects (single commit). Mike Elliott FREEMAN, BRIAN D Gary Wu Sylvain Desbureaux to follow up offline. 
    It should also consider the problem identified with the Casablanca Maintenance Release:https://lists.onap.org/g/onap-tsc/message/4641
    <2019-03-01 - Need a date for the delivery of the procedure >

    <2019-04-08 New process defined - needs to be documented on the wiki Brian Freeman


    <2019-04-15>: Wiki pag: Managing Container Image Tags
  • Tlab persistent storage IO architecture Rich Bennett 
    Request from Rich Bennett about Storage/Persistent Data Architecture Plan/PTLs - Single NFS server? 
    <2019-04-22: performance issues with old config - have bare metal cluster - - want to bring in more realistic operational aspects to the testing - network storage vs direct, would like to place modules in isolation into the environment. Evaluating the utility of testing this way. 
  • How to consume Alpine? Adolfo Perez-Duran (Deactivated)
    Meeting organized in May - https://lf-onap.atlassian.net/wiki/display/DW/TSC+2019-05-16
  • What is the plan for the June ONAP Developers Forum - dates/location/etc  Kenny Paul
    <includes outreach to education - looking at universities>
    <Virtual meeting? - still under investigation>
    <2019-04-22: 2 sites under consideration - target date - 2nd week of June - keep the date! Watch the collision with Dublin schedule>
  • Helm Chart Transfer: 4 projects have been identified for trial: A&AI, Log, Policy, APPC, CLAMP and ONAP CLI. Mike Elliott will work with PTL to gather/transfer knowledge and create training materials. Training to be done the week of Jan 14 and PTL to provide their commitment or not by M1 on Jan 24.
    <1-7/2019>: Work in progress. Schedule might shift to another week. Michael will follow-up with Mike. Training will be open to everybody. The objective is that each team will take over the management of their Helm Charts. 
    <1-28/2019>: Meeting is organized on 1/29 with LF. Training will be organized early in February. Additional information on the next PTL call (2/4)
    <2019-2-19: Meeting on this topic today - review the process - develop training material. OOM subcharts complete - A&AI this week>
    <2019-03-04: Ready to do the first project A&AI; after testing on the first project make video on process flow, several others will follow Jessica Gonzalez Mike Elliott>
    <still working out the A&AI details - in progress; once the POC is complete the other repos will follow>
    https://gerrit.onap.org/r/#/c/79580/
    <2019-04-08: LF releng - Pushed a patch to a code transfer (test) branch to test out an approach and testing verify job. Once proved out need to work with down stream CI/CD before wholesale push. ><2019-04-22: Ready to start on A&AI -will kick off today!>
  • AAF calling conventions - followup Jonathan Gathman
  •