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 ( 5 min)
Walk through the JIRA
& Gerrit
backlog to check for completeness
review: S3P requirements for VVP Beijing
gerrit
parentproject:vvp status:merged
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
propose a minimal "getting started" sprint scope.
ensure that suitable JIRA tasks are already in place to support this scope.
Create / edit
4 Relationships with other projects in Casablanca? (10 min) review project handoffs
review handoffs with
DOCS
VNFRQTS
VNF SDK
Modelling
others?
create any necessary User Stories
5 Planning for next release VVP Dublin Release 6. Any other Business? (5 min)
2 Comments
Margaret Chiosi
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?
Steven Wright
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