Thanks Ben,
I was looking at ovs-vsctl man page,
ovs−vsctl also supports a model in which traffic associated with a given
802.1Q VLAN is segregated into a separate bridge. A special form of theadd−br
command (see below) creates a ‘‘fake bridge’’ within an Open vSwitch bridge to
simulate this behavior. When such a ‘‘fake bridge’’ is active, ovs−vsctl will
treat it much like a bridge separate from its ‘‘parent bridge,’’ but the actual
implementation in Open vSwitch uses only a single bridge, with ports on the
fake bridge assigned the implicit VLAN of the fake bridge of which they are
members
It might be useful to create multiple ofproto and assign each one to a specific
vlan and run each one in a seperate VM,
other question was each ofproto should have corresponding dpif-provider, is
this not the case?
Thanks
Vishnu
________________________________
From: Ben Pfaff <[email protected]>
To: vis reddy <[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: Monday, 17 June 2013 9:29 AM
Subject: Re: [ovs-discuss] multiple ofproto
On Sat, Jun 15, 2013 at 10:08:31AM -0700, vis reddy wrote:
> I am trying to port the code to a new platform, administrator
> creates a new ofproto by binding a vlan to it, each ofproto is
> identified by vlan and the vlan + ports are ofproto ports ,
None of this makes much sense to me.
> in this scheme I am planning different netdev and ofproto
> providers(plan to use dpif-netdev and interact with the hardware)
If you plan to use dpif-netdev, you do not need with write an ofproto
provider.
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss
