Quantum basic VLAN plugin

2,467 views

Published on

Presentation of the proposed "Basic" plugin for the Openstack Quantum service.

From the Openstack Essex Design summit.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,467
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
111
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Quantum basic VLAN plugin

  1. 1. Quantum "Reference Implementation" plugin<br />Wednesday, October 5 2.00 PM<br />http://etherpad.openstack.org/QuantumBasePlugin<br />Openstack “Essex” design summitBoston – October 3-5 2001<br />Netstack track<br />
  2. 2. Agenda<br />Motivations and goal<br />“reference”, “default” or “whatever” plugin<br />Quantum-vlan-plugin blueprint<br />Follow-up actions<br />
  3. 3. Motivations<br />Plugins currently available do not embrace the spectrum of hypervisors supported by Openstack<br />Openvswitch: Xen/XenServer/KVM with Open vSwitch<br />Cisco UCS: KVM with 802.1qbh<br />It is important to have a Quantum plugin which:<br />Can run on each hypervisor platform supported by Openstack <br />Can run on ‘vanilla’ hypervisor with little to no changes to sw/hw configuration<br />
  4. 4. Goal<br />Build a Quantum plugin satisfying the following requirements:<br />Works on Xen/XenServer/KVM/ESX and possibly Hyper-V<br />Does not require any additional software or hardware component<br />Can be used on mixed hypervisor deployments (e.g.: XenServer and ESX)<br />
  5. 5. Terminology<br />Reference<br />The plugin will become the “reference implementation” of the API<br />Basic<br />The plugin adopts very basic technologies (e.g.: VLANs)<br />Default<br />The plugin is the default choice in quantum.conf<br />Other proposals?<br />
  6. 6. Implementation (1/2)<br />Quantum-vlan-plugin blueprinthttps://blueprints.launchpad.net/quantum/+spec/quantum-vlan-plugin<br />Porting of nova-network L2 components to Quantum<br />libvirt for KVM<br />XenAPI for XenServer<br />VMWareAPI for ESX<br />??? For HyperV<br />VLANs are possibly the only suitable way for implementing this plugin at the moment<br />
  7. 7. Implementation (2/2)<br />
  8. 8. Open discussion<br />Alternative implementation strategies<br />Hypervisor Support<br />In particular Hyper-V (compute service work required on networking side)<br />

×