| | 233 | ==== (6/28) ==== |
| | 234 | Not all information used by Flowvisor will be applicable to the Floodlight port. Looking through the Flowvisor configuration file (can be saved to file running `fvctl dumpConfig [filename]` against a running Flowvisor), our initial guesses say that the following do not apply for each component: |
| | 235 | |
| | 236 | * "Slice": controller hostname, port (we are working with modules, not external controllers) |
| | 237 | * "flowvisor": most of the information kept for flowvisor can be taken from Floodlight e.g. API and listen port, versioning, and host. |
| | 238 | * "!FlowSpaceRule": this is probably the only unchanged component. |
| | 239 | |
| | 240 | Config file parsing in Flowvisor happens in FVConfig:readFromFile(). Java reflection is used to then configure each component e.g manipulate database contents relevant to each. |
| | 241 | |
| | 242 | ==== (6/30) ==== |
| | 243 | With the database components removed, we need to re-build the components that parse the Flowvisor configs and initialize everything (!FlowMap definitions, slices, etc.). FVConfSetup.java is intended for this purpose. So far, it uses Jackson (used in Floodlight for the Static Flow Pusher) to parse the Flowvisor configuration file to initialize the !FlowMap (linear for now, since it is simple than the federated). |
| | 244 | |
