Welcome to NetVirt
NetVirt is a network virtualization solution that includes the following components as well as others: Open vSwitch based virtualization for software switches, Hardware VTEP for hardware switches, Service Function Chaining support within a virtualized environment, support for OVS and DPDK-accelerated OVS data paths, L3VPN (BGPVPN), EVPN, ELAN, distributed L2 and L3, NAT and Floating IPs, IPv6, Security Groups, MAC and IP learning.
Netvirt would provide the following modules --
Creates and maintains the VPN information like VpnInstances, VpnInterfaces, VpnMaps, etc.
Creates the L2 forwarding rules based on the ELAN-Instance and ELAN-Interface details.
Creates and maintains the Vpn Operational Information like VpnFootPrint, VpnInstanceOpData, VpnInterfaceOpData, etc.
Creates the L3 Forwarding Information Base (FIB) rules which is understandable by OFPlugin module and write all the populated data into FRM data store (Config-Inventory-DS)
It is used for communicating between ODL Application to Quagga(Routing Engine) via Thrift Protocol. Also it provides the support for Quagga Advertised routes from DC-GW to ODL FIB Engine.
It is used for providing DHCPv4 Server functionality as same as Openstack QDHCP Agent service.
It provides the ACL (Access Control List) in both INGRESS and EGRESS mode to VM booted neutron port.
It provides the NATing service to openstack tenant VMs in the flavor of SNAT/Floating-IP(DNAT) for Internet Connectivity purpose.
Getting Started for Users
Getting Started for Developers
Committers typically do not review changes with build failures; it is the Gerrit Owner's responsibility to get them to build. If you're facing build issues you don't know how to solve, email the app-dev list asking for help (don't just wait and expect committers to notice your proposed change and help you fix its build).
Feel free to email the app-dev list after 1 week of no movement on a (green ticked build passing) Gerrit.
Getting Started for Committers
We do not "self merge" our own changes, but add other committers as reviewers. The first reviewing committer will +1, the second reviewing committer will +2. Any other committers can merge proposed changes with at least x2 +1 from contributors.
The one exception to the rule is that we allow self merging critical changes required to unblock broken builds.
If you've been added as a Reviewer to a change you don't feel comfortable reviewing, or don't anticipate to have the time to review within say 1 week, then you may want to remove yourself from the review, ideally with a short comment, to signal that to the owner, so that he can find others willing to review (or make changes to significantly simplify or further extensively document and re-add), instead of "doing nothing" and letting reviews "linger" for too long with no action.
We aim to review all pending Gerrits which have passed Verify and have no merge conflicts and no -1/-2 (and only those) in the weekly meeting. We ignore pending Gerrits which are not Verify. (Here are those with -1/-2 reviews.)
We occasionally review the list of all pending very old Gerrits which may be should and can be abandoned (or need to poke people).
Release Planning and Release Notes
|Release||Planning||Release Plan||Release Notes||Release Review|
|Hydrogen||Release Plan||Release Review|
|Helium||Planning||Release Plan||Release Notes||Release Review|
|Lithium||Planning||Release Plan||Release Notes||Release Review|
|Beryllium||Planning||Release Plan||Release Notes||Release Review|
|Boron||Planning||Release Plan||Release Notes||Release Review|
|Carbon||Planning||Release Plan||Release Notes||Release Review|
|Nitrogen||Planning||Release Plan||Release Notes||Release Review|
|Oxygen||Planning||Release Plan||Release Notes||Release Review|
|Sodium||TBD||TBD||Release Notes||Release Review|
|Magnesium||TBD||TBD||Release Notes||Release Review|
|Aluminium||TBD||TBD||TBD||TBD (Current Development Release)|
Project Creation Date: April 7,2016
Lifecycle State: Incubation
Primary Contact: karthikeyan Krishnan <firstname.lastname@example.org> (#karthikeyan)
Project Lead: karthikeyan Krishnan <email@example.com>
Karthikeyan Krishnan <firstname.lastname@example.org> #karthikeyan
Chetan Arakere Gowdru <email@example.com>
Shashidhar Raja <firstname.lastname@example.org>
Manu B <email@example.com>
Stephen Kitt <firstname.lastname@example.org> #skitt
Faseela K <email@example.com> #faseelak
HANAMANTAGOUD V Kandagal <firstname.lastname@example.org>
Vivekanandan Narasimhan <email@example.com>
Aswin Suryanarayanan <firstname.lastname@example.org>
Sridhar Gaddam <email@example.com>
Sam Hague <firstname.lastname@example.org> #shague
Anil Vishnoi <email@example.com> #vishnoianil or #avishnoi
Andre Fredette <firstname.lastname@example.org> #afredette
Tali Ben-Meir <email@example.com>
Flavio Fernandes <firstname.lastname@example.org> #flaviof
Alon Kochba <email@example.com> #alonko
Kyle Mestery <firstname.lastname@example.org>
Ashwin Raveendran <email@example.com, firstname.lastname@example.org>
Brent Salisbury <email@example.com>
Dave Tucker <firstname.lastname@example.org>
Madhu Venugopal <email@example.com>
Evan Zeller <firstname.lastname@example.org>
Vishal Thapar <email@example.com> #vthapar