Transcript 20050718-HOPI-Summerhill

Delivering Circuit Services to
Researchers: The HOPI Testbed
Rick Summerhill
Director, Network Research, Architecture, and
Technologies, Internet2
Joint Techs
18 July, 2005
Vancouver, BC, CA
Agenda
• Announcements
• Thoughts about the next generation
Abilene
• The HOPI testbed
• Current status
2
HOPI Project - Summary
•In the near future we will see a richer set of
capabilities available to network designers and end
users
•
•
Core IP packet switched networks
A set of optically switched waves available for dynamic provisioning
•Fundamental Question: How will the core Internet
architecture evolve?
•
Many options being examined
•Examine a hybrid of shared IP packet switching
and dynamically provisioned optical lambdas
•HOPI Project – Hybrid Optical and Packet
Infrastructure
•
•
Dynamic Provisioning - setup and teardown of optical paths
Hybrid Question - how do hosts use the combined packet switched
and circuit switched infrastructures?
3
HOPI Supporters
• Equipment
• Force 10 - Ethernet switches
• HP - control, measurment and support servers
• Glimmerglass - Optical (white light) switches
• Advisory
• The HOPI design team
• The HOPI corporate advisory team
• Soon to be announced HOPI research advisory panel
• Management
• The HOPI TSC - MAX, NCREN, and IU
• The ITECs in the near future
• Internet2
4
HOPI Testbed Support Center
• Call for proposals several months ago
• Received 4 responses, all excellent
• The TSC is a collaboration between MAX,
NCREN, and the GRNOC at IU
• Advanced engineering and design focus
• Implement control plane activities
• The MAX GigaPoP (and Dragon) will focus on these
issues
• Coordinate application activities
• NCREN will focus on these issues
• Manage and engineer the facility
• GRNOC at IU will focus on these issues
5
Abilene Next-Gen
Network Futures
• October 2007 - End of recent 1-year Abilene transport MoU
extension
• Sets next-generation network planning timeline
•
•
•
•
•
Architecture definition: 1/1/2006
Transport selection: 4/1/2006
Equipment selection: 7/1/2006
Backbone deployed: 1/1/2007
Connector transition: 2007
• Concurrently, review overall business plan and management
model
• Network design time frame: 2007-2012
• Note that ESnet transport agreement with Qwest Federal is
on similar time line - December 2007
• HOPI testbed is expected to be in place for 3 years, to
experiment with future protocols
• Refine and evolve next generation architecture
6
Backbone Footprint
• Basic component will be ITU grid waves that
interconnect nodes on a national fiber footprint
• Expected to be anywhere from 10 to 40 waves
• Bandwidth of each wave expected to be 10 Gbps (and
possibly 40 Gbps)
• Switching nodes between segments
• Schematic:
7
Switching Capabilities
• Through an optical
interconnecting
device that serves 3
purposes:
• Provides a client
interface to
connecting network
• Provides access to
waves on the network
• Provides support for
sub channels on a
wave
• i.e. Ethernet VLANS,
SONET paths, or other
suitably framed capacity.
8
Connector Interface
The interface to the
backbone:
• Two or more client
interfaces between optical
interconnects (analogous
to router-to-router
connections today)
• Requirements:
• Support connectivity to IP
Network
• Support multiple sub
channels through
backbone to other RONs
up to capacity of interface
HOPI testbed to help refine
ideas
9
The HOPI Testbed
•Build a national scale testbed to examine
architectural issues
•Use the facilities from Internet2 and NLR
•
•
•
•
The Abilene network
The Internet2 wave on NLR
MAN LAN
An OC-192c circuit to London for connecting to GEANT
testbeds
• The RONs
•Use the testbed to model many of the issues that
arise in the next generation design
•Refine architectural models over the next few years
10
HOPI Questions
•Examine how to build an architecture
• A lot is known about how to do various pieces
• The main question is how would one put it all together into a
network
•Problems to understand
• When does a host use the circuit switched infrastructure and
when does it use the packet infrastructure?
• How are the circuit and packet switched infrastructures
integrated?
• Temporal degree of dynamic provisioning
• Temporal duration of dynamic paths and requirement for
scheduling
• Topological extent of deterministic provisioning
• Examine backbone, RON, campus hierarchy – how will a RON
interface with the core network?
• Understand connectivity to other infrastructures – for example,
international or federal networks?
• Network operations, management, measurement, and control
plane across administrative domains?
11
HOPI General Problem
12
HOPI Topology
13
HOPI Deployment
• Installed node locations
• Los Angeles Equinix facility - same location as NLR node
• Washington, DC MAX/Dragon facility - same location as the
NLR node
• StarLight in Chicago
• The Pacific Northwest GigaPoP in Seattle - Westin Building,
and new location of the NLR node
• Future node locations
• New York City – NYSERNet area in 32 AoA - same location
as NLR node (many thanks to NYSERNet for donating rack
space and power to support the HOPI project).
• Looking at additional possibilities as the southern route of
NLR is installed
• Circuit from NYC to London
• Early October, 2005
14
HOPI Node
15
HOPI Connector Interface
and Basic Service
• Basic Service
• 1 or 10 GigE channels (may add to this list in the future)
• Connector Interface
• A 1 or 10 GigE connection to the fiber cross connect, either
dark fiber or a provisioned service
• An MPLS L2VPN service through Abilene to the Ethernet
switch
• Provides immediate connection to the Internet2 NLR wave from
Abilene
• May add basic services and interface types at later stage
• Current planned connectors/peers
• Ultralight
• Ultrascience net
• ITECs
16
How do you Connect to the
HOPI Testbed?
• Connections
• Bring a 1 GigE or 10 GigE fiber connection directly to a node
for connection to the optical switch
• Create an MPLS Ethernet VPN across the Abilene
connection terminating at the Ethernet switch
• Note:
• Connecting to HOPI is not about obtaining additional
bandwidth
• Rather, it’s about participating in the experiment
• Control plane development and deployment is essential
• Working on integrating particular applications
• Working with the HOPI TSC
17
References
• To request a connection to the HOPI
testbed, send email to
• [email protected]
• HOPI Call Center: 877 472-2419
• Active 9/25/2005
• Additional Information
•
•
•
•
http://abilene.internet2.edu
http://www.nationallambdarail.org
http://hopi.internet2.edu
[email protected]
18
19