Download Yale FBO Communications

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Airborne Networking wikipedia , lookup

IEEE 1355 wikipedia , lookup

UniPro protocol stack wikipedia , lookup

Transcript
ALTO in ODL:
Creation Review
Initial Committers:
Wendy Roome, X. Shi,
Tony Wang, and Y. Richard Yang
Jan. 8, 2015
Background
• ALTO (RFC 7285) defines higher-level abstractions
and services to provide network information to
applications
–
–
–
–
–
–
The Map Service (network maps and cost maps)
The Map Filtering Service
The Endpoint Properties Service (EPS)
The Endpoint Cost Service (ECS)
The Information Resource Directory Service
Additional services such as network graphs are workin-progress
• RFC7285 is a RESTful design with JSON encoding
2
Goals of the ALTO-ODL Project
• Integrating the ALTO abstractions into ODL
• Facilitating ALTO deployment
• Using the ODL infrastructure to support the
implementation of scalable, reliable ALTO servers
3
Dependency on ODL Components
• Use MD-SAL Data Store to store ALTO data instances
– Define YANG models for ALTO network maps, cost maps,
and endpoint properties (draft-shi-alto-yang-model;
draft-shi-alto-yang-json)
• Derive ALTO data from ODL data whenever possible,
in particular from
– Inventory, Host Tracker, and Topology Manager
• Revise statically provisioned ALTO data with ODL data,
e.g.,
– Update ALTO cost maps upon topology changes, flow rule
updates
4
Example: Yang Model of ALTO Cost Maps
+--ro cost-maps
| +--ro cost-map* [resource-id]
|
+--ro resource-id
alto:resource-id
|
+--ro tag
alto:tag-string
|
+--ro meta
|
| +--ro dependent-vtags*
|
| | +--ro resource-id
resource-id
|
| | +--ro tag
tag-string
|
| +--ro cost-type
|
|
+--ro cost-mode
cost-mode
|
|
+--ro cost-metric
cost-metric
|
|
+--ro description?
string
|
+--ro map* [src]
|
+--ro src
alto:pid-name
|
+--ro dst-costs* [dst]
|
+--ro dst
alto:pid-name
|
+--ro cost
5
North-Bound API to Applications
• Provide the standard ALTO Restful/JSON API
(RFC7285) to ALTO clients
– ALTO server in ODL generates RFC7285 JSON encoding
(e.g., key-value encoding) from Data Store data
• Allows local access through the MD-SAL Data
Store
6
Basic Information Flow
RFC7285
ALTO Client
Configuration
Settings
ODL
ALTO
Protocol
Manager
ALTO
Configuration
Manager
MD-SAL
Data Store
ODL
Components
ALTO
Data
Related
ODL Data
ODL Components
(Host/Inventory/To
pology/BGP-LS)
7
Project Scope (Deliverables)
• Define YANG models for all basic ALTO data
• Provide ALTO Configuration Manager as a provisioning
interface to configure ALTO data instances
• Implement ALTO Protocol Manager to provide RFC7285
access to ALTO clients
• Design initial interactions with basic ODL components to
derive/update ALTO data from ODL data/updates
• Provide an ODL multi-flow scheduling app, in the context of
Yale Science Network (YSN), to demonstrate the use of
ALTO data in ODL
• [Optional] Implement incremental updates (draft-roomeincr) for cost maps
• [Optional] Define and implement ALTO network graphs
8
Project Admin.
• Project Lead: Y. Richard Yang
• Project Contact: Y. Richard Yang
• Test Contact: Xiao Shi
9