Agenda:

Antitrust Policy Statement:  Meetings of the ONAP Project involve participation by industry competitors,  and it is the intention of the Project to conduct all of its activities in accordance  with applicable antitrust and competition laws. It is therefore extremely  important that attendees adhere to meeting agendas, and be aware of and not  participate in any activities that are prohibited under applicable U.S. state,  federal or foreign antitrust and competition laws. Examples of types of actions  that are prohibited at ONAP Project meetings and in connection with ONAP  Project activities are described in the The Linux Foundation Antitrust Policy. If  you have questions about these matters, please contact your company  counsel or Andrew Updegrove, of the firm of Gesmer Updegrove LLP, which  provides legal counsel to The Linux Foundation. Linux Foundation Antitrust Policy:  https://www.linuxfoundation.org/antitrust-policy

  1. Assemble/Welcome (5 min) 

    #

    Objective

    How Achieved

    Participant Preparation required

    Action items out

    2

    Review JIRA Backlog. Participants should be comfortable that they understand the backlog of tasks for our project ( 5 min)


    Walk through the JIRA 

    VVP Bug Reports

    & Gerrit

    ansible-ice-bootstrap

    cms

    devkit

    documentation

    engagementmgr

    gitlab

    image-scanner

    jenkins

    portal

    postgresql

    test-engine

    validation-scripts

     backlog to check for completeness


    review: S3P requirements for VVP Beijing

    Jenkins/vvp

    gerrit

    parentproject:vvp status:merged

    parentproject:vvp status:OPEN



    create JIRA Tasks

    VVP now integrated into OOM.

    trigger LF to create final release artifact & update manifest - steven stark


    3

    Develop Next Sprint Participants should be comfortable with an achievable development sprint scope ( 30 min)


    walk through Beijing EPICs , User Stories

    VVP Casablanca Release Plan


    propose a minimal "getting started" sprint scope.

    ensure that suitable JIRA tasks are already in place to support this scope.


    Create / edit 

    VVP Casablanca Release Plan


    4Relationships with other projects in Casablanca? (10 min)

    review project handoffs

    M1 checklist

    M2 Checklist

    M3 Checklist

    M4 Checklist

    Project status

    review handoffs with

    DOCS

    VNFRQTS

    VNF SDK

    Modelling

    others?

    create any necessary User Stories


     Planning for next release VVP Dublin Release  

       6. Any other Business? (5 min) 

Meeting Record


 

  • No labels

2 Comments

  1. I can't attend due to conflict with architecture call. But is it possible to discuss expending resources to create a heat template to tosca template given VVP is much further along than VNFSDK to help drive the tosca version of on boarding validations?

  2. SDC already performs a conversion from HEAT→ TOSCA.

    There are other ONAP platform components also impacted for "full" support of TOSCA packaged VNFs ( A&AI and SO come to mind)

    VVP is primarily concerned with validations scripts to verify the VNF HEAT templates.

    An automated  conversion from HEAT validation scripts to TOSCA validation scripts does not seem easily tractable.

    vvp Testing to date is primarily on the heat templates, run time testing of VNF life cycle operations is not supported by VVP