Hello. Question: how are you slicing the flowspace? Fwiw, if you are using ip addresses, apparently recently some bug has crept into the code[1] where the flowvisor deletes more than it should. I should be fixing the problem soon, but it would be ncie to know if this is a known or new issue.
Thanks, - Rob . [1] It's in our bug trac DB as bug #162 (http://www.openflow.org/bugs/flowvisor/ticket/162) On Wed, Aug 11, 2010 at 8:49 AM, kk yap <yap...@stanford.edu> wrote: > Hi Zdravko, > > I think you might want to describe your setup a little more here. I > have cc-ed Rob that can give valuable inputs for the use of FlowVisor. > > Regards > KK > > On 11 August 2010 08:38, Zdravko Bozakov <boza...@gmail.com> wrote: >> Yes, I'm using FlowVisor - however I do need write access. Each controller >> should connect to the datapath, install some flow entries, and after some >> time remove it's flows and disconnect. >> >> Thanks again, >> Zdravko >> >> On 08/11/2010 05:28 PM, kk yap wrote: >>> >>> Are you using the FlowVisor? If so, there is a read-only mode for >>> controllers. >>> >>> Regards >>> KK >>> >>> On 11 August 2010 08:26, Zdravko Bozakov<boza...@gmail.com> wrote: >>>> >>>> Hi KK, >>>> thanks for the fast reply. Actually I'm trying to run the controllers >>>> independently of each other on different machines. The only shared >>>> component >>>> is the datapath, which also runs on a separate machine. My aim is to >>>> allow >>>> controllers to join/leave a specific datapath at any time and I want to >>>> make >>>> sure that they do not overwrite each other's entries (the "flowspaces" >>>> themselves do not overlap) when they are started, which is what currently >>>> happens. I hope this is somewhat clearer... >>>> >>>> Best regards, >>>> Zdravko >>>> >>>> >>>> On 08/11/2010 04:50 PM, kk yap wrote: >>>>> >>>>> Hi Zdravko, >>>>> >>>>> From what I understand, what you want is for the first component to >>>>> get the event and not the second component? If so, the first >>>>> component has to return STOP and not CONTINUE. Also check nox.xml to >>>>> make sure about the ordering of the components for each event. >>>>> >>>>> Regards >>>>> KK >>>>> >>>>> On 11 August 2010 06:14, Zdravko Bozakov<boza...@gmail.com> wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> I am trying to get two simple NOX (python) components running on >>>>>> different >>>>>> VMs to share a NetFPGA datapath using flowvisor. Generally, everything >>>>>> seems >>>>>> to be working fine, however I have the following problem: >>>>>> >>>>>> * When the first components starts, the datapath registers >>>>>> (datapath_join >>>>>> event) and its flows are installed. >>>>>> * When the second component starts and receives a datapath join event, >>>>>> all >>>>>> previously installed flows are removed from the datapath. Afterwards >>>>>> new >>>>>> flow entries are installed as expected. >>>>>> >>>>>> How can I avoid this behaviour, i.e. keep all flows installed? What am >>>>>> I >>>>>> missing? Thanks a lot in advance! >>>>>> >>>>>> Regards, >>>>>> Zdravko >>>>>> >>>>>> PS. I am using the current git source for all software packages >>>>>> >>>>>> _______________________________________________ >>>>>> nox-dev mailing list >>>>>> nox-dev@noxrepo.org >>>>>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org >>>>>> >>>> >>>> >> >> > _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
