= Aggregate Name = UtahUEN-OpenFlow Aggregate The UEN/Univ of Utah Regional aggregate supports the [http://groups.geni.net/geni/attachment/wiki/ComprehensiveSecurityPgm/Aggregate%20Provider%20Agreement%20v3.pdf GENI Aggregate Provider Agreement] (10/01/2012). = Aggregate Overview = || Aggregate Resources || As of 10/01/2012, the UtahUEN-OpenFlow Aggregate consists of a single HP switch that supports an InstaGENI implementation and the ProtoGENI implementation via Hybrid mode. This configuration will change in 2013 to include another aggregate HP switch for Data Center connectivity. || || Typical Experiments || The UtahUEN-OpenFlow Aggregate infrastructure will support any experiment on the InstaGENI and ProtoGENI infrastructure (wireless, security, protocol development, driver development, etc.) || || Aggregate Web Page || The [wiki:UtahOverview Univ. of Utah and UEN Overview] page gives more information on the site, design, etc. || || Aggregate Status || Link to monitoring web page with current status (operational status, resources available, etc) -- ''Coming''|| || Layer 2 Connectivity || The UtahUEN-OpenFlow Aggregate connects both to the GENI OpenFlow backbone and the [http://www.protogeni.net/trac/protogeni ProtoGENI] backbone. The Aggregate supports VLANs to both backbones through the use of HP's hybrid mode. A diagram of the design is: [attachment:UtahOverview/Utah_GENI_Rack_connectivity.png UEN GENI network diagram] || [[BR]] == UEN !OpenFlow Switch Port List == || '''Port''' || '''Connects to''' || || 21 || ProtoGENI aggregation switch (to Utah ProtoGENI, to Utah InstaGENI) || || 22 || I2OpenFlow Los Angeles || = Experimenter Support = || Guides and Documents || http://pgeni.gpolab.bbn.com || || Support || Link to experimenter support mailing list. If available, information on mailing lists, newsgroups, blogs, call centers, etc. set up to support experimenters using aggregate resources. || || Compatible Tools || http://www.openflow.org/wp/downloads/ contains links to the OpenFlow Switching Reference System, NOX, FlowVisor, SNAC, etc. || [[BR]] = Using this Aggregate = || Slice Authorities Recognized || Currently in GENI, a slice authority issues the user certificate, the user credential, and the slice credential. List recognized slice authorities in this space such as the GENI Project Office (http://pgeni.gpolab.bbn.com), ProtoGENI (http://www.emulab.net), and/or PlanetLab (http://www.planet-lab.org). || || Usage Policies || Aggregate specific policies on who can use resources, how many resources can be held for how long, etc. || || Aggregate Manager URL || https://foamyflow.chpc.utah.edu:3626/foam/gapi/1 || || Sample RSpecs || Cut-and-paste text RSpecs that work for your resources || [[BR]] = Aggregate Management = || Aggregate Operator || Primary Contact: Emulab Operations group http://www.emulab.net/ will be the first contact for Operations since the device is handling [wiki:GeniAggregate/UtahProtoGeni ProtoGENI] and the GENI OpenFlow resources. [[BR]] mailto:testbed-ops@flux.utah.edu [[BR]] [[BR]] Secondary Contact: Univ. of Utah Center for High Performance Computing (CHPC) http://www.chpc.utah.edu [[BR]] mailto:issues@chpc.utah.edu || || Resource Owner || University of Utah and Utah Education Network - http://groups.geni.net/geni/wiki/UTAHREGIONAL|| || Operation POC || Primary Contact: mailto:testbed-ops@flux.utah.edu [[BR]] Secondary Contact: mailto:issues@chpc.utah.edu || || Technical POC || mailto:issues@chpc.utah.edu || || Developer Links || OpenFlow announcement list: https://mailman.stanford.edu/mailman/listinfo/openflow-announce [[BR]] OpenFlow development list: https://mailman.stanford.edu/mailman/listinfo/openflow-dev [[BR]] OpenFlow discussion list: https://mailman.stanford.edu/mailman/listinfo/openflow-discuss [[BR]] OpenFlow Indigo firmware list: https://mailman.stanford.edu/mailman/listinfo/openflow-indigo [[BR]] OpenFlow announcement list: https://mailman.stanford.edu/mailman/listinfo/openflow-announce ||