Articulated Private Networks in UCLPEduard GrasaNetwork Engineer

TNC 2007Lingby, May 24th

Agenda

• Introduction

• UCLP Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

2

What is UCLP?• User Controlled LightPaths – a configuration and

provisioning tool built around grid technology using web services

• User can combine together various links, routers and switches to produce a wide are network that is under their control• Articulated Private Network (APN)

• Uses Service Oriented Architecture (SOA) and so network can be integrated with other web service applications

• With SOA instruments, devices, sensors and wireless devices can also be integrated • All under user control and architecture

3

Articulated Private Networks

Domain C

Domain A Domain B

Multi-Domain APN

Partitioned NodePass Through Node

Multi-Domain APN

4

Agenda

• Introduction

• UCLP Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

5

Classification of the UCLP Services

Resource Management

Services

Resource Virtualization

ServicesLP-WS I-WS

XC-WS MPLS-WS LR-WS

APN Scenarios-WS

Higher Level Services /

Applications

. . . 802.1q-WS

Any other service GUI client(s)

. . .

. . .

GMPLS-WS

6

UCLP: Network element partitioning• Provides software tools to allow the network

administrator to partition its network elements into multiple resources, and expose its capabilities through web service interfaces.

Network Element

Slot 1 Port 1GbE

Owner = admin

Slot 2 Port 1OC192, Ch 1-24Owner = admin

Slot 2 Port 1OC192, Ch 25-

48Owner = admin

Slot 1 Port 2GbE

Owner = admin

mak

eXC

un

do

XC

qu

ery

Cross-Connect Web Service

7

UCLP: Resource abstraction• Provides software tools to allow the network

administrator to create logical resources that provide an abstracted view of the network element resources and how are they linked to each other.

Cross-Connect Web Service

Cross-Connect Web Service

Optical Fiber

Logical ResourceWebService

rsID = 001type =

interfaceOwner = admin

Endpoint1 = …

rsID = 002type = lightpathOwner = adminEndpoint1 = …Endpoint2 = …

par

titi

on

bo

nd

qu

ery

8

UCLP: Resource Trading• Provides software tools to allow users (including physical

network administrators) to exchange/acquire/sell “logical resources” of one or more resource providers.

Cross-Connect Web Service

Cross-Connect Web Service

Optical Fiber

Logical ResourceWebService

rsID = 001type =

interfaceOwner =

userAEndpoint1 =

…

rsID = 002type = lightpathOwner = userAEndpoint1 = …Endpoint2 = …

par

titi

on

bo

nd

qu

ery

User A

Resource List Web Service

Owner = userA

Resource 001Resource 002

pu

blis

h

har

vest

9

UCLP: Topology creation/editing• Provides software tools to allow users (including

physical network admins) to create, reconfigure and delete network topologies using the logical resources acquired from different resource providers.

Utility Web Service A

Utility Web Service A creates point to point connections using SONET/SDH resources (withVCAT, LCAS, GFP)

Utility Web Service B

Utility Web Service B creates point to point and point to multipoint connections over Ethernet resorces (using VLANs, Q-inQ, …)

… Other.. (put the service you want here)

10

Agenda

• Introduction

• UCLPv2 Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

11

Use Case Scenario

• A group of partners of an European project need some resources of GÉANT2 and two NRENs: NREN A and NREN B.– Network Providers: GÉANT2, NREN A and NREN B.– User: Network administrator (or testbed WP leader) of the

European project.

GÉANT 2

NREN B

NREN A

12

Agenda

• Introduction

• UCLP Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

13

Network Provider Functionality

• Create the Physical Network– Add network elements and physical links

• Delete / Create connections (on a network element per network element basis)

• Monitor the physical network, see usage statistics.

• Create logical resources (lightpaths and interfaces)

• Use the logical resources himself (directly or through use of high level applications / utility web services)

• Lease logical resource to other users / Get new logical resources from other users

14

GÉANT 2 physical network

15

Create Logical Resources

16

Create a Resource List and Export it

17

Network is partitioned among different users

18

Agenda

• Introduction

• UCLP Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

19

Advanced User Functionality

• Create logical resources (lightpaths)– Can create a lightpath ws out of two adjacent interface ws

• Use the logical resources himself (directly or through use of high level applications / utility web services)

• Lease logical resource to other users / Get new logical resources from other users

20

Get one or more Resource List(s)

21

Merge all the Resource Lists

22

APNs are multidomain…

23

Use the APN..

Advanced user creates connections from the GUI

Advanced user creates an instance of the “APN Scenarios”

service for a regular user

24

Agenda

• Introduction

• UCLP Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

25

Regular User Functionality

• Use the logical resources himself through the use of high level applications / utility web services

26

Agenda

• Introduction

• UCLP Description

• Use Case: Scenario

• Use Case: Network Provider Perspective

• Use Case: Advanced User Perspective

• Use Case: Regular End User Perspective

• Current status and next steps

27

UCLP Product Subscriptions• UCLP Open Source ~ June 2007

– Forge of different modules (forge.uclp.ca)– Not a System– Different Organizations can contribute

• UCLP Community Edition (FREE) ~ June 2007– Software Appliance without commercial features– Updated every 6 months– No support, no maintenance

• UCLP Business Edition (Commercial) ~ September 2007– Software Appliance with commercial features– Frequent updates, monitoring– Standard support

• UCLP Enterprise Edition (Commercial) ~ end 2007– Software Appliance with commercial features– Frequent updates, monitoring– On-line Shopping, Accounting, Branding– Standard support

28

Appliance web interface screenshot

29

Current Status

• Supported technologies:– Untagged Ethernet, SONET with CCAT.

• Supported equipment:– Cisco ONS 15454, Nortel OME 6500, Nortel HDXc.

• Available utility services:– “APN Scenarios” service: You can define a set of

preconfigured network topologies, and set them up / tear them down with a single call.

• Available UCLP releases:– UCLP Community Edition (coming end of June)

30

Future activities

• Add support for more technologies:– MANTICORE project: physical and logical routers, users will

be able to create their own customized IP network.– Add support for SDH, MPLS, tagged Ethernet, Virtual

Concatenation, ROADMs, GMPLS.

• Add more utility web services:– Currently a Network Reservation System for UCLP is under

development. An adapter will be developed under the PHOSPHORUS project so that the UCLP Reservation System is compliant with the PHOSPHORUS project.

• Create a “UCLP Group”, that, together with Inocybe Technologies Inc. can provide professional UCLP solutions: support, training, customized services.

31

More Information

• UCLP Technical information– http://www.uclp.ca– uclp@i2cat.net

• UCLP Collaboration– uclp@i2cat.net

• UCLP Product Information– i2cat booth at TNC 2007– mlemay@inocybe.ca

• See also the i2cat booth at TNC 2007

32