Re: [controller-dev] Container Mgr question
Luis Gomez <luis.gomez@...>
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@...]
On 10/28/13, 2:00 AM, Luis Gomez wrote:
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.
controller-dev mailing list