Version 2 (modified by, 9 years ago) (diff)


Aggregate Name

UtahUEN-OpenFlow Aggregate

The UEN/Univ of Utah Regional aggregate supports the GENI Aggregate Provider Agreement (10/01/2012).

Aggregate Overview

Aggregate Resources The UtahUEN-OpenFlow Aggregate
Typical Experiments Kinds of experiments aggregate might be suited for (wireless, security, etc)
Aggregate Web Page Link to web page with information about the aggregate
Aggregate Status Link to monitoring web page with current status (operational status, resources available, etc)
Layer 2 Connectivity Which GENI core networks, if any, or other layer 2 networks connect to this aggregate? Please include a network diagram of GENI resource connectivity if possible. Make sure to note firewalls, if any, on both control (layer 3) and data paths.

Experimenter Support

Guides and Documents Links to docs/web pages describing how experimenters can request, program/configure and control aggregate resources. If at all possible, help docs should include example experiments that use the aggregate resources.
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 Experiment control tools, instrumentation tools and programming tools that are compatible with this aggregate.

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 (, ProtoGENI (, and/or PlanetLab (
Usage Policies Aggregate specific policies on who can use resources, how many resources can be held for how long, etc.
Aggregate Manager URL URL for AM compatible with GENI AM API e.g.
Sample RSpecs Cut-and-paste text RSpecs that work for your resources

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.