| | 1 | = Wimax Aggregate = |
| | 2 | |
| | 3 | '''Enter aggregate name''' |
| | 4 | |
| | 5 | This Wimax aggregate supports the GENI Aggregate Provider Agreement (mm/dd/yyyy). |
| | 6 | |
| | 7 | = InstaGENI Aggregate Overview = |
| | 8 | |
| | 9 | || Aggregate Manager Common Name || Enter site common name || |
| | 10 | || Aggregate Resources || A Wimax aggregate includes one or more Wimax Base station(s), 3 dedicated PCs that can load experimenter specified OS images equipped with Wimax USB dongles and multiple Samsung Galaxy S2 handsets runing Android 4.1. The Wimax Base stations are also connected to the InstaGENI racks to provide dataplane connectivity || |
| | 11 | || 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. || |
| | 12 | || Sample RSpecs || Link to RSpecs used successfully for rack site confirmation tests. || |
| | 13 | || Aggregate Status || Operational monitoring not widely available, restricted access to monitoring at [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl GMOC]|| |
| | 14 | || Slice Authorities Recognized ||GENI Portal (https://portal.geni.net), ProtoGENI (http://www.emulab.net) || |
| | 15 | || Usage Policies || A [http://groups.geni.net/geni/attachment/wiki/RUP/RUP.pdf GENI Recommended Use Policy] is available. Site should also add links here to their own usage policies. || |
| | 16 | || Layer 2 Connectivity || Enter list GENI core networks, if any, or other layer 2 networks that connect to this aggregate. || |
| | 17 | |
| | 18 | For Compute Aggregate or FOAM, <<Insert Site Diagram Here>> Make sure to note firewalls, if any, on both control (layer 3) and data paths. |
| | 19 | |
| | 20 | For FOAM Aggregate only, insert <<Insert !OpenFlow Port List Here>>. Otherwise remove this port list item for compute resource aggregate. |
| | 21 | |
| | 22 | |
| | 23 | [[BR]] |
| | 24 | |
| | 25 | = Aggregate Management = |
| | 26 | |
| | 27 | || 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. || |
| | 28 | || 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.|| |
| | 29 | || Technical POC || [mailto:instageni-ops@flux.utah.edu] || |
| | 30 | || Developer Links || Software pages: [https://wiki.emulab.net/Emulab/wiki/GitRepository InstaGENI], [https://openflow.stanford.edu/display/FOAM/Home FOAM], and [https://github.com/OPENNETWORKINGLAB/flowvisor/wiki FlowVisor]; Project page: [http://groups.geni.net/geni/wiki/GENIRacksHome/InstageniRacks InstaGENI Racks Project]; Developer mailing list: [mailto:instageni-design@geni.net] || |
| | 31 | |
