User Tools

Site Tools


community:opendaylight

This is an old revision of the document!


OPNFV OpenDavlight community page

Rather than establish a project for OpenDaylight, the OPNFV community has agreed to work on establishing focus community groups where we will describe community engagement practices, identify community leaders, manage our contributions toward those communities and generally get ourselves organised well enough to be a benefit, rather than a burden, to our source communities.

Information we should get up here asap:

OpenDaylight planning process

OpenDaylight is a collection of loosely affiliated projects, under a common project umbrella. Projects commit to a simultaneous release process with a series of milestones. How the projects organise themselves within that release process is a matter for the project developers.

OpenDaylight projects are organised into three groups:

  • Offset 0: Core projects, required by all others: Controller, yangtools, odlparent
  • Offset 1: Key network services required by other projects: OVSDB, OpenFlow, Neutron NB, topology manager, …
  • Offset 2: No projects depend on these to operate. Some examples relevant to OPNFV are SFC, GBP, VPN Service, …

Projects in Offset 1 typically have deadlines set 1 or 2 weeks after Offset 0 projects, and Offset 2 projects are similarly offset from Offset 1.

Key milestones:

  • M0: Release plan is approved (immediately after previous release)
  • 2-4 weeks after M0: New project proposal deadline. New projects require a 2 week discussion period.
  • M1: New project approval deadline. Projects should have a leader and a draft release plan.
  • M2: 6 weeks after M1. Projects should have finalised release plan and completed the project checklist
  • M3: 4 weeks after M2 (+2 weeks for Offset 1, +4 weeks for Offset 2): Functionality freeze, external APIs published, Karaf features defined
  • M4: 4 weeks after M3: API freeze, documentation, integration test plan deliverables
  • M5: 4 weeks after M4: Code freeze, stable branch creation

Release candidates will be made as necessary, starting 6 weeks after M5 (all projects commit to RC dates).

Projects of particular interest to OPNFV

Table with OPNFV-related projects, links to their feature planning, mailing list and other relevant information.

Project Description Mailing list Lithium release plan
ODL Root
Controller
OVSDB integration
OpenFlow
Neutron NB
SFC Service Function Chaining
GBP Group-based Policy
AAA Authentication and authorization
SDNi Interconnection of multiple SDN controllers
Reservation Resource reservation
DLUX User interface project

OpenDaylight in-flight OPNFV features

community/opendaylight.1425575039.txt.gz · Last modified: 2015/03/05 17:03 by Dave Neary