neutron

using openstack+openvswitch without quantum

Asked by wallace

hey, guys，I'am using openvswitch + nova,but without quantum,just adding flags:
"--linuxnet_ovs_integration_bridge=ovs-br"
"--linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver"
"--libvirt_vif_type=ethernet"
"--libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver"

to ovs,I wrote a script to add modules(openvswitch_mod.ko & brcompat_mod.ko) and "ovs-vsctl add-br ovs-br"

Then euca-run-instances, it's ok.
So, can someone tell me,why to choose quantum as a ovs plugin in openstack, or it can do something better than I'm doing now?

Thank you

Question information

Language:
English Edit question
Status:
Solved
For:
neutron Edit question
Assignee:
No assignee Edit question
Solved by:
dan wendlandt
Solved:
Last query:
Last reply:
Revision history for this message
Best dan wendlandt (danwent) said : 		#1

Hi Wallace,

If you want to create VMs with a single NIC that are attached to a single OVS bridge shared by all OpenStack VMs, what you did is sufficient. Quantum is not needed for such simple deployments.

Quantum provides:
- An API to define network connectivity, so you can flexibly create private networks and rich multi-tier network topologies.
- A way to leverage different back-end technologies, for example, to isolate VMs on different networks. A quantum plugin might use VLANs for segmentation, or more advanced L2-in-L3 tunneling.
- An API extension mechanism to expose more advanced networking functionality, such as QoS, security policies, etc.

Revision history for this message
wallace (mczhou82) said : 		#2

Thank you , danwent, look forward to your quantumdemo supporting floatdhcp.

Revision history for this message
wallace (mczhou82) said : 		#3

Thanks dan wendlandt, that solved my question.