Page History

...

ID	VVP-Web-3
Title	VNF project 2
Description	A team from a VNF provider develops a VNF for an operator
Primary Actor	Project Manager
Preconditions	VVP-web is set up on a server accessible from all team members local workstations.
Main Success Scenarios	The project manager wants to determine the progress of the project. The project manager navigates to the project overview page The project manager looks at the graph at the very top of the page, showing the number of tests failed, skipped and passed over time/commits
Exception Scenarios
Post Conditions	The project manager has an overview of how the development is progressing.

ID	VVP-Web-4
Title	VNF LFN certification
Description	VVP-web as an LFN certification portal, where VNF providers can certify there VNF as ONAP compliant
Primary Actor	LFN member
Preconditions	VVP-web is implemented as a certification portal like OPNVFs "verified program"
Main Success Scenarios	A member of the Linux foundation developed a VNF that should run with ONAP He wants to provide this VNF to the ONAP community, which requires an ONAP compliant certificate To get this certificate he visits the VVP certification website He logs in with his Linux foundation ID He uploads his HEAT templates and starts the validation If the validation was successful the platform automatically issues a certificate for the VNF he provided and includes into the list of certified VNFs
Exception Scenarios
Post Conditions	Everyone that wants to set up a VNF with ONAP can now visit the portal and search for his desired VNF to check if its ONAP certified and there for compliant with the requirements

ID	VVP-Web-5
Title	VNF LFN live certification
Description	VVP-web as an LFN certification portal, where Operators can check the live status of any open VNF
Primary Actor	LFN member
Preconditions	VVP-web is implemented as a certification portal like OPNVFs "verified program"
Main Success Scenarios	A member of the Linux Foundation wants to check the compliance status of a VNF project He visits the VVP certification portal and logs in to his LFN account He browses the open VNF projects list and clicks on the project he is interested in The project summary with a historical view of the test status and the current state of compliance is shown
Exception Scenarios
Post Conditions	Anyone can check the live status of any open VNF projects that are tracked in the portal

ID	VVP-Web-6
Title	VNF LFN certification collaboration platform 1
Description	VVP-web as a collaboration platform with certification capabilities
Primary Actor	LFN member
Preconditions	VVP-web is implemented as a certification portal like OPNVFs "verified program"
Main Success Scenarios	A member of the Linux Foundation starts a new open source VNF project He creates a repository on any externally accessible Git instance He visits the VVP certification portal and logs in with his Linux Foundation ID He creates the VNF project again and links the repository containing the source code with the VVP certification project He makes the project publically accessible
Exception Scenarios
Post Conditions	Anyone can check the live status of the VNF project.

ID	VVP-Web-7
Title	VNF LFN certification collaboration platform 2
Description	VVP-web as a collaboration platform with certification capabilities
Primary Actor	VNF provider developer team
Preconditions	VVP-web is implemented as a certification portal like OPNVFs "verified program"
Main Success Scenarios	A VNF provider develops a VNF for a single vendor The team sets up the VNf project on an internal Git instance which can be accessed from outside the internal network The team sets up the VNF project on the VVP certification platform as a private project The team gives access rights to all developers and the responsible staff from the operator
Exception Scenarios
Post Conditions	The responsible employees form the operator can check the state of the prroject live on the certifiaction platform. Also the VNF project gets a live certification which indicates whether it is ONAP compliant or not. Noone that is not involved in the project can see or access the project.

Features

A set of seed code has been developed that addresses the majority of features and use cases described. As part of the community process, all aspects can be reviewed and evolved. The following table summarizes the initially proposed features for Dublin and their current status. Some items are addressed as part of the seed code while others will be addressed in Dublin if the proposal is accepted.

FeaureID

Description

Status

F-1

Support Validation of ZIP files

Status

colour	Green
title	Complete

F-2

Support Validation of Git repositories

Status

colour	Green
title	Complete

F-3

Provide results page which concludes the validation

Status

colour	Green
title	Complete

F-4

Provide repository overview page, which provides a history on all ever done changes and validation runs for the Git repository

Status

colour	Green
title	Complete

F-5

Implement GitWeb to allow users to check the changes done to the VNF in a given commit associated with a validation run

Status

colour	Green
title	Complete

F-6

Provide a repository analytics graph to track progress

Status

colour	Green
title	Complete

F-7Extend

Use the reports the application generates by the features provided in the Stand-alone VVP Tool generated by the core scripts (provide a download function for Excel and CSV)

Status

colour	Yellow
title	Dublin

F-8

Brand the web application according to the ONAP standards

Status

colour	Yellow
title	Dublin

F-9

Allow users to link their own Git instance instead of using the built-in one (e.g. company GitLab etc.)

Status

colour	Yellow
title	Dublin

F-10

Extended analytics capabilities for the repository summary page

Status

colour	Yellow
title	Dublin

F-11

Implement an user management using Linux Foundation accounts

Status

colour	Yellow
title	Dublin

Status

colour	Red
title	Critical

F-12

Integrate the web portal as a part of the LFN

Status

colour	Yellow
title	Dublin

F-13

Implement a database that holds certification information for every project created on the platform

Status

colour	Yellow
title	Dublin

F-14

Implement a certification utility, that issues certificates for VNFs that are compliant with the ONAP VNF requirements

Status

colour	Yellow
title	Dublin

F-15

Enable the linkage of multiple repositories to one certification projectUse the reports generated by the core scripts (provide a download function for Excel and CSV)

Status

colour	Yellow
title	Dublin

F-1216

Provide a searchable list of the VNFs that got certified using the portal with commit or version of the VNF that got checked (maybe create a fingerprint of each checked VNF to guarantee the certified code not being changed without knowledge)

Status

colour	Yellow
title	Dublin

F-17

Implement named projects as a new way of collaboration on VNF certification.

Status

colour	Yellow
title	Dublin

F-18

Implement an access rights system, which allows project owners to restrict the visibility of their certification projects to only specific Linux Foundation accounts or the public.

Status

colour	Yellow
title	Dublin

F-19

Introduce a groups feature that can depict companies or organizations. A group should be mapped to the Linux Foundation accounts of the members.

Status

colour	Yellow
title	Dublin

(Proposal) User management?

Status

colour	Blue
title	Proposal

F-20

Provide an open API

Status

colour	Yellow
title	Dublin

Status

colour	Red
title	Critical

Screenshots

The following screenshots are based on the seed code implementation, and subject to further review, feedback, and updates.

...

Space shortcuts

Page tree

Versions Compared

Old Version 3

New Version Current

Key

Features

Screenshots