BRUW Bandwidth Reservation for User Work

1
BRUW Bandwidth Reservation for User Work

• Bob Riddle Technologist

2
What is BRUW?

• Bandwidth Reservation for User Work
• is a part of Internet2s Hybrid Optical and
  Packet Infrastructure (HOPI) project
• will allow authorized users to reserve bandwidth
  across packet switched backbone networks
• uses a Web-based interface for end-users to place
  reservations and the MPLS protocol to set up
  dedicated paths on packet switched networks, such
  as Abilene

3
Why BRUW?

• Need for bandwidth Cal Tech - CERN
• currently email process, personal
  authentication
• Need to know every network engineer in the world
• Network equipment is manually configured
• User with need is far removed from the process

4
Purpose of BRUW

• minimize human efforts in this process
• streamline/automate this process
• allow bandwidth reservations to be made with
  minimal human intervention
• allow end-users to send large amounts of data
  reliably across packet switched networks
• simplify the reservation process for both
  end-users and network managers

5
BRUW Design Criteria

• End Users not Network Engineers so
• front-end user interface must be usable to the
  Researcher, Faculty, etc.
• back-end network interface must be trusted by
  the NOC
• Credible bandwidth reservation requests can be
  made across administrative domains (networks )

6
BRUW Design Criteria (part 2)

• Web Browser chosen for user interface
• users are familiar with this interface
• Web server are a commodity service
• Separate back-end network component from
  front-end user interface
• User required to authenticate and can have
  different capabilities
• Shibboleth inter-institutional middleware
  service

7
(No Transcript)
8
How does BRUW work?

• Bandwidth Reservation
• User must register for ID
• Human intervention required
• Approved user permitted to make a bandwidth
  request
• User request is either accepted or refused
• Depends upon who you are!
• Attributes are assigned to users
• Accept request queued in Database

9
How does BRUW work? (part 2)

• Edge node discovery

10
How does BRUW work? (part 3)

• every hour checks the Scheduler DB
• BRUW configures each edge router to build a
  bi-directional MPLS tunnel between the two
  end-points
• BRUW communicates with the Abilene edge routers
  using JUNOScript, the communication API for
  Juniper Networks routers.
• BRUW connects to each edge router using
  JUNOScript API, makes necessary changes to the
  configuration to build and/or delete MPLS
  tunnels, commits the configuration changes, and
  closes the connection.

11
BRUW work to be done

• Policy issues who decides?
• Last mile
• MPLS tunnel across the backbone, but what about
  your packet switched network?
• non-packet switched networks
• CANET4, NLR, new Surfnet
• other BRUWs DRAC, UCLP, DRAGON, etc.
• Non-academic networks
• ESNET collaboration at LBL

12

• ?

13
If you want to know more

• Email me bdr_at_internet2.edu
• BRUW Notes on the Web
• HOPI Project
• UCLP Project
• Dragon Project

14
(No Transcript)