pilot use case 3: bod services over the intercontinental fibre infrastructure
DESCRIPTION
Presentantion about FIBRE's testbed - pilot application n.3. Presented at FIA Meeting - Athens, 18-20 March 2014. By Roberto Monno (NXW)TRANSCRIPT
![Page 1: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/1.jpg)
BoD services over the intercontinental
FIBRE infrastructure
WP5 partners
FIA Meeting
Athens, 18-20 March 2014
1
![Page 2: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/2.jpg)
FIBRE testbed (BR & EU)
Wireless experimental facilityOFELIA Control Framework
OMFProtoGENI Small wireless facility (3 nodes)
UFRJ UFF
RNP
PoP-RJPoP-DF
PoP-GO
PoP-BAPoP-PA PoP-PE
UFPEUFPAUNIFACS
OMFOCF
UFG
OCF
OMFOCF
UFSCar
USP
PoP-SP
i2CAT
U. Bristol
OCF
UTH
OMF
WDM
PoP-i2CAT PoP-UTH
PoP-UB
CPqD
OMFOCF
WDM
OMFOCF
ProtGENI
OMFOCF
OMFOCFOMFOCF
OMFOCF
OMFOCF
OCF
2
![Page 3: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/3.jpg)
Demo setup description
• The OpenFlow resources (physical switches) belongs to the i2CAT FIBRE island
• An enhanced version of the Ofelia Control Framework (OCF) is used to built a dedicated “slice”
• 3 OF-enabled switches (managed by Optin-AM)• 3 Xen-based servers (managed by VT-AM)
• An enhanced version of NOX (e-NOX) controller manages the network resources
• A modified OSCARS platform provides BoD services running on top of the e-NOX
• External application (in a NXW server)
• NXW & i2CAT are physically connected through an encripted tunnel
3
![Page 4: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/4.jpg)
Setup Overview
4
![Page 5: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/5.jpg)
... now go through the demo!
• An administrator uses an enhanced version of the Ofelia Control Framework (OCF) to allocate a physical “slice” in the I2CAT island
• A NOX-based SDN controller is able to• abstract the physical slice details• provide high-level services (topology discovery, path
computation, flow-entry creation, etc…)
• OSCARS platform functionalities• implement BoD services• exposes a web interface for the (VLAN-based)
circuit composition
• Automatic setup provisioning of the physical circuit between two hosts that belong to the same
5
and some boring stuff...
![Page 6: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/6.jpg)
Software components
6
• The e-NOX controller uses OpenFlow protocol to configure the OF physical switches
• The CoreManager component provides a high level APIs• Topology discovery• Path computation (F-PCE)• Route setup & teardown
• The OSCARS tool implements circuits allocation abstraction
• Bandwidth availability• Time constraints• VLAN utilization
![Page 7: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/7.jpg)
Architecture Overview
7
![Page 8: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/8.jpg)
e-NOX functional details
8
• based on Zaku branch of NOX with component dependencies• discovery, pyauthenticator, spanning_tree, etc...
• new elements developed in the FIBRE project• DiscoveryPacket• CoreManeger
• DiscoveryPacket is an event-driven application for topology discovery and packet switch provisioning
• detect datapath status (joint or leave the network)• detect link status (up or down)• discover hosts (association between MAC and IP address)• install and remove flow-entries
• CoreManager is an application developing a RESTful interface• show virtual topology information (switches, ports, links and hosts)• manage path computation request through F-PCE• redirect create/destroy routes to discovery-packet
![Page 9: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/9.jpg)
OSCARS functional details
9
• composed of several subsystem modules• AAA: Authentication, Authorization and Auditing• PSS: Path Setup Subsystem (network interface)• BSS: Bandwidth Scheduling Subsystem• NS: Notification Subsystem• WEB-UI• Core Module: reservation, scheduling, inter-domain communication
• modifications (integration in the OF network control plane)• BSS uses CMPathFinder to call core-manager for the path computation• PSS uses OFPathJob to call core-mananger for setup and teardown to
circuit
• functional recall• allocate circuits in the network topology with BW, time and VLAN
constraints• circuit overlapping based on available link capacity• Bandwidth is shared among circuits (VLAN isolation)
![Page 10: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/10.jpg)
... now come back to the demo!
• Is the ping “up & running”?
• If the default timeout (4 minutes) were elapsed …
• and the circuit were automatically destroyed …
• Then … it works!
10
• Otherwise … “… connectivity problems…”
![Page 11: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/11.jpg)
Thank you / ObrigadoRoberto Monno (NXW)
twitter.com/FIBRE_project
www.facebook.com/fibre.project
www.fibre-ict.eu
![Page 12: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/12.jpg)
BackupSlides & Screenshots
12
![Page 13: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/13.jpg)
13
• Enhanced version of the Expedient module of the OCF• i2CAT island description:
• Optin-AM manages 3 OpenFlow-enabled switches• VT-AM manages 3 Xen-based servers
• Vlan-based flowspace: VLAN-ID = 2
FIBRE island at i2CAT
![Page 14: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/14.jpg)
14
OSCARS at NXW
• OSCARS provides BoD services• Bandwidth: use 200, 300, etc.. [Mb/s]• Time: default timeslot is from start-time=now to end-time=4 minutes later• Vlan-id: use 2
• Connect to the NXW ciscoVPN• OSCARS runs into an internal network (10.0.11.104 address)
![Page 15: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/15.jpg)
Connecting host1 to host2
15
• Enter in the i2CAT island• FIAvm1 (10.1.0.28) = e-NOX slice controller • FIAvm2 (10.1.0.31)• FIAvm3 (10.1.0.32)
• Try to ping host1 (192.2.2.2) from host2 (192.2.2.3): fails
• Insert the values in the OSCARS form (and then click “reserve” button)• Src = urn:ogf:network:domain=cpqd.com.br:node=switch4097:port=10:link=11.2.1.2• Dst = urn:ogf:network:domain=cpqd.com.br:node=switch4099:port=10:link=11.2.2.2• Bandwidth (Mbps) = 300• Src/Dst VLAN = 2• Src/Dst Tagged = true
• Workflow:• OSCARS checks for bandwidth availability and then sends the path-computation
request to the Core-Manager• Core-Manager fowards the request to F-PCE and waits for a response• Core-Manager replays to OSCARS with a path composed of datapath-id and port-
number• OSCARS send a request to install the flow-entries• Core-Manager forward the request to Discovery-Packet• Discovery-Packet uses NOX to configure the flow-entry in to OF-switch
![Page 16: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/16.jpg)
Workflow Overview
1616
CoreManagerOSCARS NOX
(OF-Control) FPCEUser
ask for path in topology
topology topology
ask for circuit
grant circuit
[Time elapses...]
ask for path in topology
calculated path in topology
teardown circuit
[Check bandwidth availability in time and VLAN space]
calculated path in topology
teardown circuit
![Page 17: Pilot Use Case 3: BoD services over the intercontinental FIBRE infrastructure](https://reader038.vdocuments.site/reader038/viewer/2022110303/54c2337a4a795904628b45b4/html5/thumbnails/17.jpg)
17
Connection host 1-2 established
• At the end, you have created a connection between 2 end-points: enjoy!