Changes between Version 16 and Version 17 of OpenFlow/SDNInstaGENI


Ignore:
Timestamp:
06/24/16 15:05:46 (5 years ago)
Author:
asydney@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • OpenFlow/SDNInstaGENI

    v16 v17  
     1= InstaGENI SDN VM =
    12----
    2 = Background =
     3== Background ==
    34
    45In 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.
     
    67(See the [wiki:GENIExperimenter Experimenter Support] wiki pages for information about software-only SDNs, which do not use hardware OpenFlow switch resources.)
    78
    8 = Updated SDN Operation at InstaGENI Racks =
     9== Updated SDN Operation at InstaGENI Racks ==
    910As shown in the figure below, the FOAM and FV VMs are being replaced with a new lightweight "SDN" VM. The InstaGENI control software operates in concert with the SDN VM to allocate and connect resources for SDN experiments.
    1011
    1112[[Image(geniSDNUpdate-v1.jpg)]]
    1213
    13 == How are hardware SDN resources provisioned? ==
     14=== How are hardware SDN resources provisioned? ===
    1415
    1516 * GENI experimenters conducting SDN experiments that leverage the "OpenFlow over Stitching" service will add the following line to the regular stitching rspec that they submit to GENI aggregates:
     
    2324 * When the connection has been established, the "SDN" VM continues to forward SDN control traffic between the experimenter's instance at the data plane switch and the experimenter's controller.
    2425
    25 === Notes ===
     26==== Notes ====
    2627 *  A "VLAN" slice implies that the experimenter is unable to conduct SDN experiments that modify the VLAN header. However, other headers such as the IP are supported (assuming the match conditions and actions required by the experimenter, are supported by the switch).
    2728 *  By default, stitched OpenFlow connections connect only two locations.  Please contact help@geni.net for other desired configurations.
    2829
    29 == What SDN administrative tasks are required of the site admin? ==
     30=== What SDN administrative tasks are required of the site admin? ===
    3031Compared to the [http://groups.geni.net/geni/wiki/OpenFlow/FOAM previous requirements], '''none''' are required.  The new "VLAN" model:
    3132
     
    3334 * removes the need for site contacts to administer FOAM and FlowVisor manually (site contacts preferred automated approvals)
    3435
    35 == How do we track the users of GENI SDN resources? ==
     36=== How do we track the users of GENI SDN resources? ===
    3637Mechanisms inherent in the [https://portal.geni.net/ GENI account creation and approval process] and the [http://genimon.uky.edu/ GENI monitoring interface] provide the ability to determine the identity of experimenters who own GENI resources in SDN experiments. These can be used to track traffic by owner, if necessary, as requested by an experimenter, site contact or operations staff.  Please contact the [http://globalnoc.iu.edu/gmoc/index/support.html GMOC] to report any suspected issues with GENI traffic or resources.
    3738
    38 == Software ==
     39=== Software ===
    3940
    4041The software for building the "SDN" VM can be downloaded [http://software.geni.net/local-sw/ here]: sdn-vm-1.0.0.tar.gz