Page Comparison

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

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 ( 15 min)

Walk through the JIRA backlog to check for completeness

review:

Project charter

3

3

ONAP updates and upgrades of VNFs.
Guest Operating Systems for VNFs.

review commit for bug fix VNFRQTS-121

Change 20089 - Merged

ONAP will orchestrate updates and upgrades of VNFs. The One ~~target~~
method for updates and upgrades is to onboard and validate the new
version, then build a new instance with the new version of software,
transfer traffic to that instance and kill the old instance. There
should be no need for the VNF or its components to provide an
update/upgrade mechanism.

{NCSPs could require that VNFs ~~should~~ use the NCSP’s standard set of OS images to enable
compliance with security, audit, regulatory and other needs.} more discussion needed.

Also - Create JIRA task to clarify that scope & purpose of the Guidelines document as general, aspirational, future oriented and not release bound. Conformance requirements are in the requirements document.

4

Develop Sprint definition. Participants should be comfortable with an achievable development sprint scope (

30

10 min)

as a group select a minimum set of functionality to complete within the next two weeks

based on seed contributions

VNF Use cases ?

VNF Test Case Descriptions?

vnfrqts Beijing Release Plan

propose a minimal "getting started" sprint scope.

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

review: