Hi Su, FlowVisor is not prefectly isolated, there can be tricky and corner situations where isolation breaks and packets can trifle from one slice to another. This is mainly because of the flowspace approach we have for matching and intersection which is n-dimensional in space and there can be possibilities of various intersections and hence one has to be careful while assigning the rules in flowmod. We are working on better isolation in the future versions of flowvisor where the flowspace approach would no longer be used.
Cheers Sumanth On Mon, May 6, 2013 at 6:53 AM, Su <sujz.b...@qq.com> wrote: > Hi, All > > Supporse two Flowspace rules exists in flowvisor: > > Rule1: dpid=9 x=1, y=2, z=3, priority=10 Slice:Bob=4 > Rule2: dpid=9 x=1, y=2 priority=1 Slice:Alice=4 > > In which x,y and z are three different match fields, Now a Packet_In > message with x=1,y=2,z=4 comes, FlowVisor will direct it to Alice's > controller, furthermore, Alice's controller send a FlowMod message not > specifying field z and install a FlowEntry in switch(dpid=9). Once a new > flow with x=1,y=2,z=3 which should belongs to Bob comes, the switch will > forward it according to the previously installed flowentry(x=1,y=2,z=*), > i.e. Slice Alice controls flows of slice Bob, so How to implement flow > isolation in this situation? > > Thanks. > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
