Open Stack

Thanks Salvatore. I think i should use Neutron to do all the stuffs first, because Neutron is the primary network component of openstack. If it doesn't support some functions, i just direct control the openvswitch, I hope i won't break the neutron.
Thanksfrom Peter

Date: Mon, 24 Jun 2013 15:06:25 +0100
Subject: Re: [Openstack] OVS and quantum
From: sorlando at nicira.com
To: mcheung63 at hotmail.com
CC: kmestery at cisco.com; openstack at lists.launchpad.net

A few comments inline from my side.

On 24 June 2013 14:53, Peter Cheung <mcheung63 at hotmail.com> wrote:




Hi Kyle    Is Neutron support this1) create vlan, adding a port(tap) for a vm?
I think this is one of Neutron's basic use cases, unless I'm missing something.
 2) create vlan tag and assign to tap http://openvswitch.org/support/config-cookbooks/vlan-configuration-cookbook/   ?

I'm not sure I see the difference with the previous case.Are you referring to the ability of tagging a port which was not tagged before? 
3) control the netflow of openvswitch

Nope, this is not supported by Neutron at the moment.However, you can add an extension for it, if you wish.
 
4) control the QOS of openvswitch
This feature is not supported by the 'reference' open source plugin (Open vSwitch, Linux Bridge).
From what I gather now even the new ML2 plugin will have this capability.
Approaches for QoS in open source Quantum plugin have been recently debated, but this feature is not on the roadmap for Havana.

 5) does it provide an API to do the avobe things instead of command line?

Neutron does *everything* through an API. 

I think commercial user need to above things, so we want to support those actions in pandora.
Thanksfrom Peter

> From: kmestery at cisco.com

> To: mcheung63 at hotmail.com
> CC: openstack at lists.launchpad.net
> Subject: Re: [Openstack] OVS and quantum

> Date: Mon, 24 Jun 2013 13:42:43 +0000
> 
> On Jun 24, 2013, at 12:01 AM, Peter Cheung <mcheung63 at hotmail.com> wrote:
> > 

> > Dear All
> >     I want to use OVS for my VMs. So which one i should do
> > 1) i use alway use quantum to control OVS. I believe quantum cannot 100% control the OVS, so i can use ovs command line to control the additional features.

> 
> Which features of OVS are you interested in which are currently not exposed through Neutron (formerly Quantum)?
> 
> > 2) i shouldn't use quantum, i should leave quantum and use OVS directly. But which parameter of "nova boot" can specific the OVS tap to a VM?

> > 
> nova-networking is planned to be deprecated in the near future, FYI. It may be better to address your concerns in Neutron. Can you let us know what you're looking for in particular in OVS which is not exposed in Neutron yet?

> 
> Thanks,
> Kyle
> 
> > Thanks
> > from Peter
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack

> > Post to     : openstack at lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~openstack

> > More help   : https://help.launchpad.net/ListHelp
> 
> 
 		 	   		  

_______________________________________________

Mailing list: https://launchpad.net/~openstack

Post to     : openstack at lists.launchpad.net

Unsubscribe : https://launchpad.net/~openstack

More help   : https://help.launchpad.net/ListHelp



 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130625/cd60383e/attachment.html>