wiki:GeniAggregate/StanfordOpenFlow

Version 12 (modified by mkobaya1@stanford.edu, 8 years ago) (diff)

--

THIS PAGE IS UNDER CONSTRUCTION

Overview

The network exposed to experimenters is as shown to the right:

Issues

Aggregate Name

Stanford OpenFlow Aggregate

Aggregate Overview

Aggregate Resources Five OpenFlow switches (NEC x 4 and HP x 1)
Typical Experiments Any kind of experiments that requires OpenFlow. Esp. we have a loop topology
Aggregate Web Page NONE
Aggregate Status NONE
Layer 2 Connectivity Connection to NLR. For the network diagram, refer to the figure on the left


Experimenter Support

Guides and Documents NONE .
Support deployment-help@openflowswitch.org
Compatible Tools FOAM, Any OpenFlow controller compatible with v1.0


Using this Aggregate

Slice Authorities Recognized http://pgeni.gpolab.bbn.com
Usage Policies TBD. Please be considerate to the other users.
Aggregate Manager URL https://openflow4.stanford.edu:3626/foam/gapi/1
Sample RSpecs See below.

Sample Rspec

<resv_rspec type="openflow">

<user affiliation="Stanford" email="mkobaya1@stanford.edu" firstname="Masayoshi" lastname="Kobayashi" password="openflowrocks"/> <project description="Asterix" name="Stanford's Asterix demo"/> <slice controller_url="tcp:controller.stanford.edu:8833" description="The Asterix controller at Stanford." name="stanford-asterix"/>

<flowspace>

<switch urn="urn:publicid:IDN+tulum.gpolab.bbn.com:expedient:openflow+switch:06:b3:00:24:a8:c4:b9:00"/> <dl_type from="35021" to="35021"/>

</flowspace>

<flowspace>

<switch urn="urn:publicid:IDN+tulum.gpolab.bbn.com:expedient:openflow+switch:06:b3:00:24:a8:c4:b9:00"/> <dl_type from="2048" to="2048"/> <nw_proto from="6" to="6"/> <tp_dst from="10001" to="10001"/>

</flowspace>

<flowspace>

<switch urn="urn:publicid:IDN+tulum.gpolab.bbn.com:expedient:openflow+switch:06:b3:00:24:a8:c4:b9:00"/> <dl_type from="2048" to="2048"/> <nw_proto from="6" to="6"/> <tp_src from="10001" to="10001"/>

</flowspace>

</resv_rspec>


Aggregate Management

Aggregate Operator Name of organization that operates the aggregate manager. Link to URL of organization.
Resource Owner Name(s) of the organization(s) that owns the aggregate resources, if different from the operator of the aggregate manager. If this information cannot be provided (such as with aggregates consisting of contributed resources), provide a statement about who provides the resources.
Operation POC Contact information for person or team that operates this aggregate
Technical POC Contact information for the PI or research team that develops/maintains the aggregate
Developer Links Links to aggregate code base, design docs, developer mailing lists, etc.

Attachments (1)

Download all attachments as: .zip