140 likes | 278 Views
UCLP Roadmap. Bill St. Arnaud CANARIE Inc – www.canarie.ca Bill.st.arnaud@canarie.ca. UCLP Objectives. Allow institutions to integrate wavelengths and fiber from different suppliers and integrate with institution's network management domain And offer VPNs to users
E N D
UCLP Roadmap Bill St. Arnaud CANARIE Inc – www.canarie.ca Bill.st.arnaud@canarie.ca
UCLP Objectives • Allow institutions to integrate wavelengths and fiber from different suppliers and integrate with institution's network management domain • And offer VPNs to users • Create discipline specific re-configurable IP networks • Multihomed network which bypasses firewalls with direct connect to servers and routers • User controlled traffic engineering • Active replacement for Sockeye and Route Science • Alternative to MPLS • Primary purpose is NOT reservation and leasing of wavelength resources • Primary purpose is NOT switched optical networks • Primary purpose is NOT end-to-end optical VPNs • Primary purpose is NOT inter-domain connection of lightpaths
CAVEwave acquires a separate wavelength between Seattle and Chicago and wants to manage it as part of its network including add/drop, routing, partition etc NLR Condominium lambda network Original CAVEwave UCLP intended for projects like Optiputer and CaveWave
Recent UCLP examples • Over 20 UCLP lightpaths setup across CA*net 4 • Need to purchase additional wavelength in 2005 • AARnet used UCLP to setup lightpath for Huygens-Cassini data transfer • 5 HDTV streams to be switched and controlled through UCLP at APAN in Bangkok • 3 UCLP lightpaths for restoral/protection by regional networks • 2 UCLP lightpaths for distributed backplane – e.g. mini TeraGrid • 7 international UCLP lightpaths – 1G to 2.5 G • 10G UCLP lightpath shared between Tokyo Data reservoir and HEPnet
UCLPv2 • UCLPv2 • Graphical interface to allow users to create “on demand” lightpaths or APNs • All lightpaths represented as web services that are consumed by user by linking through portal on workflow engine • will create a priori “articulated private networks” (APNs) represented as a web service • CAVEwave excellent example of an APN • Change add/drop configuration • Change termination networks • Create daughter APNs through partitions • Cross connect to other APNs • BPEL or Keppler to link APNs together to form end to end lightpaths and to link instruments
Campus Border Router End user Standard Ethernet Links VLAN External Lightpath 802.1 p/q VLAN Web Service Lightpath Creation Workflow Service VLAN to LightPath Cross Connect Web Service UCLP for LAN
Third Party Lightpath Bidirectional -1 Gbps Vancouver: Port x/Slot y/Channel z Montreal: Port x/Slot y/Channel z Partitionable Available until 2006 to all Vancouver CA*net 4 peers BCnet Neptune Instrument WS UCLP Lightpath WS Winnipeg CA*net4 Vancouver CA*net4 New York MAN LAN Seattle Pwave Montreal CA*net4 Seattle CA*net4 UCLP Cross Connect WS Chicago CA*net4 Chicago STAR LIGHT
3 2 4 OMNInet Bandwidth Reservation WS Xconnect WS Xconnect WS Lightpath WS Lightpath WS IP Flow QoS WS 1 5 Neptune/ ORION Instrument WS 4 2 3 LightPathConectionPT BandwidthReservationPT LightPathConectionPT Visualization WS InstrumentNetworkServicePT NeptuneInstrumentServicePT 5 1 Neptune admin orchestration End user orchestration Super user orchestration End to end choreography
OMNInet Scenario Neptune Instrument WS Neptune Lightpath Winnipeg Calgary CA*net 4 Seattle NLR Visualization Engine CAVEwave Lightpath Optiputer Chicago
WSDL for instrument Control Port(s) WSDL Interface Java Stub instrumentControlPT dataPathConnectionPT Data Port(s) Data Path A Data Path B Instrument Axis/Apache/Linux Server
WSDL Power & Instrument instrumentControlPT instrumentEnablelPT Control Port(s) Java Stub WSDL Interface Data Port(s) Instrument Axis/Apache/Linux Server Instrument WSDL Power WSDL Proxy Data Path A Data Path B dataPathConnectionPT New Instrument WSDL To user’s WSDL
Neptune Admin Orchestration instrumentControlPT Neptune Instrument WS Instrument WS Proxy Path A Archive & Fork WS LAN WS Data Flow Path 1 archiveForkPT dataPathConnectionPT LANnetworkConnectionPT Path B NeptuneInstrumentServicePT 1
Significance of UCLP v2 • Many power plants, water, sewage and process control SCADA (System Control and Data Acquisition) are moving to TCP/IP so that they can integrate process control with other eBusiness systems • But this makes systems more vulnerable to DOS attacks, viruses, etc • Impossible to fully protect with firewalls etc because too many back doors • Need to build “micro” firewalls around each SCADA sub-system with web services and link them together with web services workflow