wiki:GeniAggregate/UCSanDiegoInstaGENI

Version 7 (modified by lnevers@bbn.com, 2 years ago) (diff)

--

InstaGENI Aggregate

University of University of California San Diego

This InstaGENI aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy).

InstaGENI Aggregate Overview

Aggregate Manager URL https://instageni.ucsd.edu:12369/protogeni/xmlrpc/am
Aggregate Manager URN urn:publicid:IDN+instageni.ucsd.edu+authority+cm
Aggregate Manager Common Name ucsd-ig
Aggregate Resources An InstaGENI aggregate includes 5 Hosts (3 VM Servers and 2 dedicated PCs) that can load experimenter specified OS images. Racks also support OpenFlow topologies, usually including extensions onto campus OpenFlow networks. Rack servers are HP ProLiant DL380p Gen8.
Typical Experiments InstaGENI provides a controllable, predictable, and repeatable network environment. Experimenters can get virtual machines or dedicated PCs on which they have full "root" access, run available operating systems of their choice, and connect nodes in an arbitrary topology that can support OpenFlow.
Sample RSpecs Link to RSpecs used successfully for rack site confirmation tests.
Aggregate Status Select "ucsd-ig" at https://genimon.uky.edu/status or login for Operator status/reports
Slice Authorities Recognized GENI Portal (https://portal.geni.net), ProtoGENI (http://www.emulab.net)
Usage Policies A GENI Recommended Use Policy is available. Site should also add links here to their own usage policies.
Layer 2 Connectivity Enter list GENI core networks, if any, or other layer 2 networks that connect to this aggregate.


Aggregate Management

Aggregate Operator Enter Site POC information, enter URL of organization. This can be a person or (preferably) a mailing list that reaches all operators at a site.
Resource Owner Enter person that is responsible for site rack overall. This entry may also be same as POC. This is typically the person who would took responsibility for operating and maintaining the rack on behalf of their site, and who would make the final decision on policy that affects the rack such as usage policies.
Technical POC instageni-ops@flux.utah.edu
Developer Links Software pages: InstaGENI, Project page: InstaGENI Racks Project; Developer mailing list: instageni-design@geni.net


GENI Network Stitching

VLANs Range Link ID URN Next Hop
1720-1739 urn:publicid:IDN+instageni.ucsd.edu+interface+procurve2:1.24.al2s urn:publicid:IDN+al2s.internet2.edu+interface+rtsw.losa.net.internet2.edu:et-2/3/0.0:ucsd-ig


OpenFlow over GENI Network Stitching

This rack supports running hardware OpenFlow experiments over stitched GENI network connections. Please be advised that the following restrictions apply:

  • Network stitching on the InstaGENI rack allocates and enforces link bandwidth, which cannot be modified by OpenFlow.
  • VLANs allocated to stitched connections on the rack cannot be modified, because InstaGENI rack switches operate in hybrid mode, preventing VLAN tag rewriting.

The following is the layout of OpenFlow switch connections for the InstaGENI Aggregate:

  • InstaGENI Switch procurve2: Model: HP J8697A Switch E5406zl


Port List

InstaGENI Rack OF Switch

NameNumberConnects To
E1 1 pc1[eth1]
E2 2 pc1[eth2]
E3 3 pc1[eth3]
E4 4 pc2[eth1]
E5 5 pc2[eth2]
E6 6 pc2[eth3]
E7 7 pc3[eth1]
E8 8 pc3[eth2]
E9 9 pc3[eth3]
E10 10 pc4[eth1]
E11 11 pc4[eth2]
E12 12 pc4[eth3]
E13 13 pc5[eth1]
E14 14 pc5[eth2]
E15 15 pc5[eth3]
A24 24 to GENI network

OpenFlow connection to the GENI core network is via port name="B4" num="24" on the procurve2 switch.

Shared Nodes interfaces (port name/port number) details:

Hosteth1eth2eth3
pc1 E1/1 E2/2 E3/3
pc2 E4/4 E5/5 E6/6
pc3 E7/7 E8/8 E9/9

Dedicated Nodes interfaces (port name/port number) details:

Hosteth1eth2 eth3
pc4 E10/10 E11/11 E12/12
pc5 E13/13 E14/14 E15/15

If you require some other type of dataplane connections for your OpenFlow experiment, please contact geni-users@googlegroups.com.

Attachments (1)

Download all attachments as: .zip