Versions Compared

Old Version 1

changes.mady.by.user Trevor Lovett

Saved on

compared with

New Version Current

changes.mady.by.user Trevor Lovett

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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


Recording: https://wiki.onap.org/download/attachments/79202767/VNFRQTS%20Weekly%20Meeting%202020-02-05.mp4?api=v2


4

#

Objective

How Achieved

Participant Preparation required

Action items out

1Assemble/Welcome (5 min)


2Revised M4 CriteriaReview proposal

Proposed Changes:



  • New 3rd party dependencies, new FOSS (final confirmation)
  • License scan issues addressed
  • Address all security issues (I’m not opposed to leaving this, but I’m not aware of any security scans on VNFRQTS though.  If something was raised we would certainly address it)
  • All high/highest priority jira tickets addressed
  • Update Frankfurt Release Platform Maturity, CII badging update - update M4 Result (Doesn’t seem applicable to VNFRQTS)
  • Test coverage goals complete (Not applicable)
  • No Gerrit requests older than 36 hrs. (Given we are often getting documentation of things in the release, it’s common for us to receive updates up to the RC0 milestone.  I don’t know if there is a large benefit to this milestone or forcing all contributions in by M4 in our case)
    • NOTE we will leave this to drive behavior to have requiremennts in by M4
  • Integration weather board update  (We’re not part of integration testing)
  • Update Frankfurt Risks


Any changes or additions?


3

Review Old JIRA Tickets for Updated Disposition:


Walkthrough JIRA tickets labelled UNDER-REVIEW and determine next stepsPlease review this list of issues
34

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


Walk through the JIRA backlog to check for completeness


review:  docs.onap.org ( latest)

vnf guidelines open gerritt

vnf requirments open gerritt

vnf test open gerrit

vnf use cases open gerritt

vnfrqts bugs

Recommend Mark Scott participate in the VES spec reviews:


https://gerrit.onap.org/r/q/project:%2522%255Evnfrqts/.*%2522+status:open

5

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


Walk through the JIRA backlog





56Relationships with other projects (10 min)review project handoffs

review handoffs with

DOCS

VVP

VNF SDK

Modelling

LFN C&V

others?

6 


New review created for upcoming ONAP badge on OVP portal.  This includes documentation updates for how to acquire the badge and execute the testing.  Review an feedback welcome: https://gerrit.opnfv.org/gerrit/c/dovetail/+/69635

7

Release Planning:

Frankfurt (new features)

M1 : 11/7/19

M2/3: 1/9/20 - Closed


 


Frankfurt Epics 



 

vnfrqts Project charter

vnfrqts Epics

vnfrqts User Stories



   7.   Any other Business? (5 min) 

...