Trone-Aware Application
Download
Report
Transcript Trone-Aware Application
Trone-Aware Application
Bruno Sousa ([email protected])
LCT - Centro de Informática e Sistemas
Universidade de Coimbra
16 March 2012
Coimbra, PT
Summary
2
Introduction
Trone-Aware application
Current
Status
Tests
Conclusion
Coimbra, 16/03/2012
Introduction / Goals
3
Resilience is a key goal of Multihoming.
Detect
network failures and react proactively.
Detect changes in network condictions (e.g., more delay)
and react proactively.
Coimbra, 16/03/2012
Trone-aware Application Architecture
4
Coimbra, 16/03/2012
Trone-aware Application internals
5
Applications
MH
Shim Layer
MH
MeTHODICAL
MH
FIT
MH
Core
MH
OWAMP
SCTP
API
sysctl
API
MH
NetManager
Coimbra, 16/03/2012
Trone-aware Application (cont.)
6
SCTP API functionalities:
Description
Status
Local
Testbed
PT Cloud
Configure SCTP Channel (e.g,
clocking mode)
Yes
Yes
To Be Started
Get SCTP Options (e.g, size of
sender buffer)
Yes
Yes
To Be Started
Set SCTP Options
In Tests
In Tests
Configure Primary Address of
Association
In Tests
In Tests
To be started in
upcoming
weeks.
Shutdown association for non
trust IP
To Be
developed
Coimbra, 16/03/2012
Trone-aware Application (cont.)
7
SCTP API Events:
Description
Status
Local Testbed
AssociationChangeNotification
Yes
Yes
PeerAddressChangeNotification
Yes
Yes
SendFailedNotification
Yes
Yes
ShutdownNotification
Yes
Yes
PT Cloud
To be started
in upcoming
weeks.
Coimbra, 16/03/2012
Trone-aware Application (cont.)
8
MH Shim Layer:
Description
Status
Local
Tested
Yes
Yes
Support Data*
In Development
In Tests
Identification of application
characteristics
In Development
In Tests
Support VoIP
PT Cloud
To be started in
upcoming weeks.
* Using Apache Commons Net
Coimbra, 16/03/2012
Trone-aware Application (cont.)
9
MH MeTHODICAL:
Description
Multiple Attribute
Decision Mechanism
(MADM)*
Status
Yes
Local Tested
PT Cloud
In local testbed; And
To be started in
tested for two papers. upcoming weeks.
* Using Rserve to make the interface to a script in project R.
Coimbra, 16/03/2012
Trone-aware Application (cont.)
10
MH OWAMP:
Description
Status
Local Testbed
PT Cloud
Collect Network
Performance Metrics
per need (e.g.,
event-based)
Yes
Yes
With End-to-End
connectivity issues!
(SOLVED TODAY)
It was developed also a framework to enable
collecting these metrics for a long monitoring period.
* Metrics include One-way delay, jitter, packet loss, reordering flag, duplicates flag, Hops.
Coimbra, 16/03/2012
Trone-aware Application (cont.)
11
MH NetManager:
Description
Monitor interface specific info and
events (e.g., up, down). Support for
wireless and wired interfaces.
Status
Local
Testbed
PT Cloud
Yes
Yes
Yes
Coimbra, 16/03/2012
Trone-aware Application (cont.)
12
Introducing dynamics in the Ethernet interfaces of PT
Cloud (events for MH NetManager):
Description
Framework to change attributes of
Ethernet interfaces that are “too static”!
Status
Local Testbed
PT Cloud
Yes
Yes
Only IP
route2
dynamics
Dynamics include:
Change
of media type (using mii-tool)
Change of delay and packet loss (using ip route2 tools)
Coimbra, 16/03/2012
Trone-aware Application (cont.)
13
MH FIT to be specified:
Description
Status
Interface type (REST, Web-service)
Data we need and can use for SCTP
(see next slide)
Data we can provide to FIT
Coimbra, 16/03/2012
Trone-aware Application (cont.)
14
MH FIT input data to Trone-aware application:
Data
Monetary of other type of
cost of an interface (COST).
Trust of an IP address (TRUST)
Default
Value
Notes
0€
Can not be provided by
FIT.
Should be provided by
FIT to augment security
at transport layer
ANY SUGGESTION?!
Coimbra, 16/03/2012
Conclusion
15
Next-Steps
Continue
testing.
Stabilize current version of development.
Specify MH FIT and SCTP Resource Manager
Coimbra, 16/03/2012
End
16
Thank You
Coimbra, 16/03/2012
DEMO A
17
Goals:
Demonstrate
that TRONE enhances security!
Steps:
Step
1: Demonstrate Standard SCTP behaviour.
Step 2: Introduce failures at network and trust info from
FIT.
Step 3: Demonstrate SCTP behaviour with input data of
FIT.
Coimbra, 16/03/2012
DEMO A – with End-node outside
Cloud
18
Goals:
Demonstrate
that TRONE enhances security!
Steps:
Step
1: Demonstrate Standard SCTP behaviour.
Step 2: Introduce failures at network and trust info from
FIT.
Step 3: Demonstrate SCTP behaviour with input data of
FIT.
Coimbra, 16/03/2012
DEMO B
19
Goals:
Demonstrate
that path selection of SCTP can be
enhanced !
Steps:
Step
1: Demonstrate Standard SCTP behaviour.
Step 2: Introduce failures at network.
Step 3: Demonstrate SCTP behaviour with input data of
monitoring.
Coimbra, 16/03/2012