Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

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

Duration 60 minutes


DurationAgenda ItemRequested byNotes / Links
START RECORDING
10min

Dublin M2 Review

  • Review the outcome of the 2019-02-21 M2 milestone
  • Quick review of remaining work items for M2 approval on Thursday
  • M3 reminder
  • Plan your project review with the Architecture Team


Dublin risks review

Walk the release related risks and understand likelihood and impact.

Please update your risks as new information comes to light. Select risks will be reviewed next week at the PTL meeting.


15minLFN infrastructure roadmap proposal

Missing items from TSC-58

10min

Vulnerability identified from pen testing procedure overview

Java upgrade to eliminate vulnerability - proposal of upgrade from Rel 8 to Rel.11 to be discussed.

ODL not moving to Java 11 until Sodium release (Frankfurt for ONAP).

Deferring this topic until El Alto or beyond.

5minIntegration sanity test

Give details on integration sanity test and its impact on Dublin

Propose M3/M4 checklist modifications

Action Items

  • Revise LF infrastructure roadmap to include the TSC-58 content  in advance of TSC meeting Kenny Paul Former user (Deleted)
  •  Krzysztof Opasiakto provide vulnerability procedure overview next week 2019-02-25
    /* Vulnerability Management Procedure is being updated so I'd like to delay this till the procedure is approved by TSC to avoid confusion. Hopefully the overview will be delivered next week. */
  • Yang Xu add integration sanity passing in milestone checklist
  • (PTLs): Review ONAP codebase license scan, Feb. 2019 sent by Steve Winslow on 2/18. (reminder)

  • 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
  • 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

    <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
  • 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>
  • What is the plan for the June ONAP Developers Forum - dates/location/etc  Kenny Paul Former user (Deleted)
  • No labels