Summary

NetVirt requests to join the Fluorine release as a Managed Snapshot Integrated project. NetVirt meets the requirements noted below.

Healthy Community

Since the first ODL release, NetVirt has been one of the more active projects. The main feature is consumed by many different downstreams and is a typical example for SDN use cases in ODL. There are currently 8 committers from three different companies. The project has great diversity with 262 different contributors. The project has regular, weekly meetings.

Responsiveness

NetVirt is very responsive because of it's extensive CSIT that catches any breakages or issues in ODL. The CSIT is also ingrained deeply in the typical development workflow and must be passing. This prompts NetVirt to be responsive to any disruptions. The usage by downstream consumers also requires good responsiveness.

Active Committers:

There are 8 active committers in NetVirt: [https://wiki.opendaylight.org/view/NetVirt|NetVirt Wiki]. The project also has 9 committers that have transitioned from active committers to emeritus committers.

TSC Attendance:

NetVirt is well-represented in the TSC. The PTL is an elected member from the application group. Other committers are on the TSC also, as well as the test lead being a TSC member,

Checkpoints Submitted On-Time:

All deliverables for Oxygen can be seen here:
http://docs.opendaylight.org/en/latest/release-process/milestone-readouts.html

Jobs Required for Managed Projects Running:

All required jobs are in place:
[https://jenkins.opendaylight.org/releng/view/netvirt|NetVirt Jobs]

Depend only on Managed Projects

NetVirt depends on the core projects as well as genius, neutron, ovsdb and openflowplugin.

Documentation

NetVirt has install, user and develoepr guides as well as an OpenStack usage guide at [http://docs.opendaylight.org/projects/netvirt/en/latest/|NetVirt Docs]. Release notes are also included for each release.

CLM

NetVirt acknowledges that is required to handle Component Lifecycle Violations in a timely manner.