Changes between Version 10 and Version 11 of OpenFlow/SDNInstaGENI


Ignore:
Timestamp:
06/24/16 10:25:13 (5 years ago)
Author:
asydney@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/SDNInstaGENI

    v10 v11  
    22= Background =
    33
    4 In the original GENI deployments, InstaGENI racks supported FOAM and FlowVisor software to help manage hardware OpenFlow resources, along with the InstaGENI control software.  The FOAM aggregate manager was used with FlowVisor (FV) to allow experimenters to reserve SDN resources at a rack. A single OpenFlow VLAN instance was manually provisioned at the racks and FV allowed "slicing" of this instance via IP subnets. Hence, each researcher was allocated an IP subnet (a priori) to conduct SDN experiments. FOAM and FV were also used in the GENI Mesoscale network to facilitate network programmability in the GENI core. With the advent of GENI's "OpenFlow over Stitching" service, we are phasing out FOAM and FV, which are no longer actively supported.
     4In the original GENI deployments, InstaGENI racks supported FOAM and FlowVisor software to help manage hardware OpenFlow resources, along with the InstaGENI control software.  The FOAM aggregate manager was used with FlowVisor (FV) to allow experimenters to reserve SDN resources at a rack. In general, a single OpenFlow VLAN instance was manually provisioned at the racks and FV allowed "slicing" of this instance via IP subnets. Hence, each researcher was allocated an IP subnet (a priori) to conduct SDN experiments. FOAM and FV were also used in the GENI Mesoscale network to facilitate network programmability in the GENI core. With the advent of GENI's "OpenFlow over Stitching" service, we are phasing out FOAM and FV, which are no longer actively supported.
    55
    66(See the [wiki:GENIExperimenter Experimenter Support] wiki pages for information about software-only SDNs, which do not use hardware OpenFlow switch resources.)