| Line 25: | Line 25: | ||
==Benefit to Fedora== | ==Benefit to Fedora== | ||
Fedora users will be able to construct and manage arbitrary independent layer 2 networks for OpenStack clouds or other large-scale virtual machine deployments. These virtual networks are realized | Fedora users will be able to construct and manage arbitrary independent layer 2 networks for OpenStack clouds or other large-scale virtual machine deployments. These virtual networks are realized using any of several included plugins, or a custom plugin. | ||
As Quantum continues to evolve, layer 3 constructs such as routing, VPNs, firewalls, and load balancing will be incorporated. | As Quantum continues to evolve, layer 3 constructs such as routing, VPNs, firewalls, and load balancing will be incorporated. | ||
Revision as of 19:25, 12 January 2012
OpenStack Quantum
Quantum is a virtual networking service for OpenStack.
Owner
- Name: Bob Kukura
- Email: rkukura@redhat.com
Current status
- Targeted release: Fedora 17
Step1:
Step2:
Step3:
Step4:
- Last updated: January 12, 2012
- Percentage of completion: 0%
Detailed Description
Quantum is a virtual networking service developed for the OpenStack cloud computing platform, but also applicable to other advanced virtual machine network deployments. The Diablo release of Quantum has been available for Fedora 16 for several months as a standalone service. Fedora 17 will include the Essex release of Quantum, integrated with the the Essex release of OpenStack Compute (nova). Plugins will be provided supporting Feature/Open vSwitch, Linux bridging, and certain Cisco products for network transport between VMs within and across hosts.
Information on the upstream project is available at Quantum Launchpad and Quantum Wiki.
Benefit to Fedora
Fedora users will be able to construct and manage arbitrary independent layer 2 networks for OpenStack clouds or other large-scale virtual machine deployments. These virtual networks are realized using any of several included plugins, or a custom plugin.
As Quantum continues to evolve, layer 3 constructs such as routing, VPNs, firewalls, and load balancing will be incorporated.
Scope
This is mainly packaging work ...
How To Test
TBD. We have booked a test day.