Quantum basic VLAN plugin
Download as PPTX, PDF2 likes871 views
The document outlines the motivations and goals for developing a 'reference implementation' plugin for OpenStack's Quantum networking service, aiming to ensure compatibility across various hypervisors like Xen, KVM, and ESX. It emphasizes the need for a plugin that operates on multiple platforms without requiring additional hardware or software. The discussion includes implementation strategies and highlights the potential use of VLANs in realizing the plugin's functionality.
Quantum basic VLAN plugin
- 1. Quantum "Reference Implementation" pluginWednesday, October 5 2.00 PMhttp://etherpad.openstack.org/QuantumBasePluginOpenstack “Essex” design summitBoston – October 3-5 2001Netstack track
- 2. AgendaMotivations and goal“reference”, “default” or “whatever” pluginQuantum-vlan-plugin blueprintFollow-up actions
- 3. MotivationsPlugins currently available do not embrace the spectrum of hypervisors supported by OpenstackOpenvswitch: Xen/XenServer/KVM with Open vSwitchCisco UCS: KVM with 802.1qbhIt is important to have a Quantum plugin which:Can run on each hypervisor platform supported by Openstack Can run on ‘vanilla’ hypervisor with little to no changes to sw/hw configuration
- 4. GoalBuild a Quantum plugin satisfying the following requirements:Works on Xen/XenServer/KVM/ESX and possibly Hyper-VDoes not require any additional software or hardware componentCan be used on mixed hypervisor deployments (e.g.: XenServer and ESX)
- 5. TerminologyReferenceThe plugin will become the “reference implementation” of the APIBasicThe plugin adopts very basic technologies (e.g.: VLANs)DefaultThe plugin is the default choice in quantum.confOther proposals?
- 6. Implementation (1/2)Quantum-vlan-plugin blueprinthttps://blueprints.launchpad.net/quantum/+spec/quantum-vlan-pluginPorting of nova-network L2 components to Quantumlibvirt for KVMXenAPI for XenServerVMWareAPI for ESX??? For HyperVVLANs are possibly the only suitable way for implementing this plugin at the moment
- 8. Open discussionAlternative implementation strategiesHypervisor SupportIn particular Hyper-V (compute service work required on networking side)