Re: [controller-dev] Container Mgr question
Alessandro Boch (aboch) <aboch@...>
Inline @ A#
From: Madhu Venguopal [mailto:mavenugo@...]
Sent: Monday, October 28, 2013 6:18 AM
To: Luis Gomez; dev (controller-dev@...); Alessandro Boch (aboch)
Subject: Re: [controller-dev] Container Mgr question
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.
In a scenario where containers do not share host-facing ports (but they can share inter-switch links), using the static vlan assures traffic isolation without the need of configuring container flows ( flow specs).
But given the switch interconnections and host attachments are dynamic in nature, given this works only if hosts send untagged frames, and given FRM is not auto-adding the match on the static vlan on the configured flow entries (it cannot, otherwise it would break the logic in the first hop switch, the one matching on the host traffic ingressing the of network), I would not put much effort in testing this.
controller-dev mailing list