Hi Jake, The place you would want to do this in is the FVSlicer and override the current behavior for openflow messages.
>From memory, the FVSlicer is spawned in the FVClassifier when flowspace is >added which points to that new slice. The FVClassifier essentially represents >a switch with flowvisor so all packets for a single switch go through that >FVClassifier. The FVClassifier then interrogates the flow map to figure out >which slice is affected by this packet. If the FVSlicer exists then the packet >is sent to it, if the FVSlicer does not exist it is created (and initted) and >the packet is sent to it. Hope this helps. -- Ali Al-Shabibi (sent from handheld) > On 14 oct. 2013, at 10:39, Jake Jameson <jake...@yandex.com> wrote: > > I am loooking in the communication between flowvisor and the controller. > Which classes should I look into if I want to accomodate an extended > controller on top of flowvisor. I am trying to understand how flowvisor > spawns new FVSlicer instances when a new controller gets connected to the FV > and how does it handle new massages received from it. > Can anybody provide me some pointers on that or maybe what classes should I > look into. I would be a great help for me. > > 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
