Hi again, Looking at the configuration file and FVConfig.java - what is the purpose of the "switches" filed of the config file? As in, is it intended to store information about the switches expecting the topology to be static, or to make the topology controller's job easier when enabled?
Thanks, Ayaka On Tue, Jun 26, 2012 at 7:41 PM, Ayaka Koshibe <akosh...@gmail.com> wrote: > Thanks Ali, it all makes sense - I was able to get my config file out. > > Ayaka > > On Tue, Jun 26, 2012 at 7:23 PM, Ali Al-Shabibi < > ali.al-shab...@stanford.edu> wrote: > >> Hi Ayaka, >> >> Good question. When configuration is added to FlowVisor it is written to >> the database which persists the data across flowvisor runs. If you would >> like obtain your modified flowvisor config you can run fvctl dump >> config.json and that will export your configuration file. >> >> Hope this makes sense. >> >> >> Cheers. >> >> -- >> Ali >> >> On Jun 26, 2012, at 3:52 PM, Ayaka Koshibe wrote: >> >> > Hi Ali, >> > >> > I have one more question - I realize that the configurations pushed >> using fvctl is saved someplace when flowvisor is shut down - where would >> this be if flowvisor had been started without specifying a configuration >> file? I've tried searching for 'config.json' and similar, but this only >> brings up the original config file with the 'alice' and 'bob' slices. >> > >> > >> > Thanks, >> > >> > Ayaka >> > >> > On Mon, Jun 25, 2012 at 1:08 PM, Ali Al-Shabibi < >> ali.al-shab...@stanford.edu> wrote: >> > Hi Ayaka, >> > >> > The FlowSpace is indeed a collection of of flow entries (which are in >> fact the flow space rules entered into FlowVisor). It's probably worth >> noting here that the set of actions a flow entry contains is not the >> standard OpenFlow actions, but rather a slice name and a permission value. >> The FlowMap provides a standard interface add, remove, and performs >> searches within the defined flowspace. The actual flowmap can be retrieved >> from the configuration via a call to the FVConfig class or FlowSpaceUtil, >> but searches are in the flowspace are performed bby calling FlowMap.match >> and FlowMap.intersect methods. >> > >> > The match method is used to identify which slice a packet in should be >> sent to while the intersect method finds which flow space rules apply to a >> FlowMod to allow flowvisor to perform the appropriate rewriting of the >> flowmod before sending it to the switch. >> > >> > Let me know if this is not clear. >> > >> > >> > Cheers. >> > >> > -- >> > Ali >> > >> > On Jun 23, 2012, at 10:09 PM, Ayaka Koshibe wrote: >> > >> > > Hi all, >> > > >> > > I am trying to understand the inner workings of FlowVisor, >> specifically the FlowMap and how it relates to the rest of the components. >> I'm hoping for a check of what I think I get from the code/docs. >> > > >> > > It seems that the FlowSpace is a collection of flow entries, each >> identified by the DPID they apply to, a FVMatch for a packet to be matched >> against, and a set of actions on a match. The FlowMap looks like it >> provides a structure to hold multiple FlowEntries, as well as to find >> intersections between stored FVMatches and received packets. The primary >> components (FVClassifiers and FVSlicers) seem to access the FlowMap using >> FlowSpaceUtil and FVConfig, and indirectly when messages are handled (by >> ClassifyFromSwitch() and SliceFromController()). >> > > >> > > Am I understanding this correctly? >> > > >> > > >> > > Many thanks, >> > > >> > > Ayaka >> > > >> > > _______________________________________________ >> > > 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
