With the slicing I would like to set up queues of a specified bandwidth (known in advance) for source IP, destination IP and port tuples, (basically exactly what the Openflow spec says) for certain flows but not all. For flows where slicing would be necessary, I install the flow table entries to all openflow routers on the path manually from a controller I have that controls multiple NOX controllers. All remaining flows are routed using default routing mechanisms such as shortest path routing. I didn't use the routing component to do this previously I had written something similar into my switch component which is the primary file I've altered for all my experiments. Unfortunately I haven't rewritten this shortest path code to work across the multiple controllers so I'm not sure if I could just use the routing component for all flows which I don't manually install entries for and it would work across multiple controllers.
I think any of the options that KK mention might work for my set up. -Holly On Mon, Jan 4, 2010 at 10:46 AM, Martin Casado <[email protected]> wrote: > Supporting slicing in Nox should be fairly straightforward, however > integrating with existing components (e.g. routing) may be a bit more of a > chore. > > Holly, can you say a bit about what you want to do with slicing? > .martin > >> Hi Holly, >> >> AFAIK, the page is up-to-date. You have 3 options if you want to try >> slicing with NOX. >> 1) Use the FlowVisor. There is a version that supports slicing there. >> 2) Use the OpenFlow message event in NOX, that passes up all OpenFlow >> messages in NOX. Yes, this is ugly. The event is more geared for >> those who want to handle raw messages. >> 3) Port slicing into NOX and we would be glad to take a patch. >> >> I personally prefer the third solution for selfish reasons, but >> options one and two are definitely workable. Option one is what we >> used to test slicing in our network before release. >> >> Hope this is helpful. >> >> Regards >> KK >> >> 2010/1/4 Holly Esquivel <[email protected]>: >> >>> >>> Hi All, >>> >>> I've currently grabbed a copy of the NOX branch with Openflow 1.0 from >>> the instructions I found at >>> (http://www.openflowswitch.org/wk/index.php/OpenFlow_1.0_release_notes) >>> git clone git://noxrepo.org/nox >>> cd nox >>> git checkout -b <branch_name> origin/openflow-1.0 >>> >>> At the bottom of the page it says that this does not expose slicing or >>> 64-bit datapath ID. Is this because slicing has not been intragated >>> into the NOX controller yet (or maybe it has but this page hasn't been >>> updated)? Has anyone exposed the slicing functionality on their own? >>> Any advice would be appreciated as I'm wondering about the difficulty >>> of tackling this for a project. >>> >>> Thanks! >>> Holly >>> >>> _______________________________________________ >>> nox-dev mailing list >>> [email protected] >>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org >>> >>> >> >> _______________________________________________ >> nox-dev mailing list >> [email protected] >> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org >> > > _______________________________________________ nox-dev mailing list [email protected] http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
