Re: [controller-dev] Container Mgr question

Luis Gomez <luis.gomez@...>

Thanks Madhu,


For me it looks like adding the VLAN tag to flowspecs and deprecate the existing “staticVlan” will fix everything, as then you can use the VLAN tag to separate traffic regardless whether the port is connected to host or network, and you also avoid writing undesirable vlan tags. I will file a bug for it.




From: Madhu Venguopal [mailto:mavenugo@...]
Sent: Monday, October 28, 2013 6:18 AM
To: Luis Gomez; dev (controller-dev@...); aboch@...
Cc: 'integration-dev@...'
Subject: Re: [controller-dev] Container Mgr question


Hi Luis,

Comments inline.

On 10/28/13, 2:00 AM, Luis Gomez wrote:

Hi controller experts,


I am configuring containers in OpenDaylight controller, and observed the following:


1) Containers using different ports is no problem (no flowspec needed)

2) If containers share one or more host ports, I need flowspecs (different on both containers) to separate traffic

3) If containers share only network ports, it is enough if they have different staticVlan

M# Yes. Your observations are inline with the design intent.


Then my questions:


- In scenario 2) if a host uses VLAN tags for different traffics or a regular switch trunk port is connected to host port, how can I put each VLAN on a different container? the existing implementation does not seem to deal with this situation.

M# Yes. this is a missing item on the Flow-Spec. We need to add the Vlan based isolation. Please open a Bugzilla item.


- In scenario 3) how is the “staticVlan” setting used to separate traffic in the network ports? I have created flows in the containers but I do not see any vlan being automatically applied or enforced on the network ports.

M# This is supposed to work as you expect. But, I think this was disabled some time ago due to a few observed issues.
      Will let the other controller-devs to get the reason. Also, I have a basic concern with this feature. Since OF1.0 doesnt support QinQ, this staticVlan
      addition will overwrite any vlan that is already present in the packet. So, not having this feature right now, is not a problem :-)
      But certainly the above vlan presence in flow-spec is missing.



controller-dev mailing list


Join to automatically receive all group messages.