geni current ops workflow connectivity

Sponsored by the National Science Foundation

GENICurrent Ops Workflow

Connectivity

John WilliamsSan Juan, Puerto Rico Mar 16 2011

www.geni.net

Sponsored by the National Science Foundation 2March 16th, 2011

Connecting GENI Resources

• Think outside of the (sand)box– You’ve set up some GENI resources– Connect to other GENI resources

http://groups.geni.net/geni/wiki/ConnectivityOverview

• Why connect?– To make your

resources (aggregates) available

– Experimenters (faculty, students) are asking

– The GPO is askinghttp://groups.geni.net/geni/wiki/ExperimenterPortal


Get Yourself Connected!

1. What are you connecting to?- labs, campuses, backbones, etc- resources, aggregates, etc

2. What type of connections are required?3. Do you require engineering of new

connectivity?- Or, can you use existing connectivity?

4. Are you using connectivity services?1. Backbones2. Aggregate-controlled stitching

5. Does your connectivity work?This is complex! The GPO will help you find a solution that works best

for you and your users. Expect things to get simpler as GENI evolves.


1. What are you connecting to?

• What sites are participating? – What resources are available at other sites?

• Various options listed on the GENI wiki– http://groups.geni.net/geni/wiki/GeniAggregate– http://groups.geni.net/geni/wiki/ConnectivityOptions


2. Types of connections• Layer-3 connectivity (mostly easy)

– Commodity Internet– Backbone layer-3 services– Tunneling (including layer-2 over layer-3+)

• Layer-2 connectivity (focus of this talk)– Static connections (where we are)

• Intra-campus connections • Regional VLANs• Backbone VLANs

– Aggregate-controlled stitching (where we’re going)• OpenFlow• ProtoGENI• ORCA

http://groups.geni.net/geni/wiki/ConnectivityGuidelines


3. Engineering Connections

• What types of connectivity are available?

• Can you use existing connectivity? – Yes, Let’s experiment!– No, Let’s engineer!


3.1 Engineering L2 Connections

1. Intra-campus connectivity– Provide connections between your

resources• different labs, different buildings, etc.

– Connect your resources to the edge– Common options are:

• VLANs• Additional physical connectivity


2. Regional connections– If sites share a regional then the regional

may be able to provide connectivity




3. Backbone connections– Choose your path to

your Backbone endpoint– Other sites will need

connections to their endpoints as well

http://groups.geni.net/geni/wiki/ConnectivityOverviewhttp://groups.geni.net/geni/wiki/ConnectivityGuidelines


4. Connectivity ServicesBackbones

• Focus is layer-2 VLAN connectivity• Provides “dynamic” provisioning of

connectivity between backbone endpoints• Used in a typically static manner• Involves a person

• Current options:• Internet2 ION• National LambdaRail FrameNet


Backbones - Internet2 ION

• Follows a “circuit” model– Point-to-point connections– Supports VLAN translation

• Your ION endpoint– Looks like: bbn.newy.ion.internet2.edu

• Circuit provisioning service: ION– Done by Internet2, your regional, your IT staff, or GPO– http://www.internet2.edu/ion/

• More info on ION and participating organizations:– http://groups.geni.net/geni/wiki/SiteInternet2


Backbones – National LambdaRail FrameNet

• Follows a “VLAN” model – supports multi-point VLANs– VLAN translation via request to NLR.

• Your FrameNet endpoint– Looks like: bost.layer2.nlr.net[Gi9/2]

• VLAN provisioning service: Sherpa– Done by NLR, your regional, your IT staff, or GPO– https://sherpa.nlr.net/

• More info on FrameNet and Sherpa usage:– http://groups.geni.net/geni/wiki/SiteNlr


4. Connectivity ServicesAggregate-Controlled Stitching

• This is where we’re going• Allow for dynamic provisioning of connectivity• Provisioning controlled by aggregates and

resource specifications• Refer to the stitching workshop

• Options• OpenFlow• ProtoGENI• ORCA• Others…


Aggregate-controlled stitching - OpenFlow Core

http://groups.geni.net/geni/wiki/NetworkCore

• Reachable via – Internet2 ION– National LambdaRail FrameNet

• OpenFlow-controlled interconnections.

• Considerations:– There are currently two OpenFlow core VLANs (3715, 3716)– Use two VLANs to participate in both OpenFlow Core VLANs– If you share a path to the OpenFlow core with other sites

your VLAN IDs must be unique on any shared layer-2 devices

OpenFlow Core VLAN 3715

http://www.openflow.org/wp/


Aggregate-controlled stitching - ProtoGENI

• Reachable via Internet2 ION– ProtoGENI.salt.ion.internet2.edu -- Salt Lake City, UT– ProtoGENI.wash.ion.internet2.edu -- Washington D.C.– ProtoGENI.kans.ion.internet2.edu -- Kansas City, MO– More to follow.

• ProtoGENI Component Manager reserves VLANs between core ProtoGENI nodes.

• More information on ProtoGENI connections:– http://groups.geni.net/geni/wiki/Integration– http://www.protogeni.net/trac/protogeni


Aggregate-controlled stitching - ORCA

• Reachable via National LambdaRail• Coordinate with ORCA for connectivity

https://geni-orca.renci.org/trac/


5. Does your connectivity work?

• Testing your connection– Assign static private IP addresses

• VLANs encoded as the subnet• other subnets may be used by

experiments– For multi-site connections, e.g. the

OpenFlow core, ranges of IP addresses are “assigned” per site

http://groups.geni.net/geni/wiki/ConnectivityHome


Summary

• Spiral 3 ops goals:– More interconnected sites with aggregates– Leverage aggregate-controlled stitching

• (current methods do not scale)• Less engineering, more experimenting

• GPO will help– Check out the wiki for GENI participants,

aggregates, experiments, etc• http://groups.geni.net/geni• http://groups.geni.net/geni/wiki/ExperimenterPortal

– Email us with questions!• [email protected]

geni current ops workflow connectivity

Documents