Transcript JRAX/SA3: Title of Activity

Connect. Communicate. Collaborate
Stitching framework for
AutoBAHN
Victor Reijs, HEAnet
TNC2007, May 23rd, 2007
[email protected]
<Insert your
organization’s
logo here>
Outline
•
•
•
•
•
•
•
Connect. Communicate. Collaborate
Stitching framework for AutoBAHN…
Three parts to stitch…
Stitching Data model…
The stitching engine…
Sample parameters, attributes and values…
AutoBAHN resource scheduling process…
Warp up…
Stitching framework
Connect. Communicate. Collaborate
- A general stitching Framework and Data model to describe
how to stitch technology domains
- It is an inter-domain framework
- Should work in manual (NOC) and automated environment
(e.g. AutoBAHN)
- A definition of the offered service should exist for the initial
AutoBAHN service :
1 Gbit/s framed service, 98% throughput, VLAN/port based
- It is assumed that individual domains have full autonomy
so they can determine their own policy, technology, topology, etc. and
they don’t have knowledge about their neighboring domains
Three parts to stitch
Connect. Communicate. Collaborate
1. The Domain Core will expose certain parameters to make sure that
path and peering negotiations can be undertaken by a higher entity
(such as a human or IDM).
2. Left Logical interfaces require parameters to be configured to
communicate with peering domains which want to connect to this
domain.
3. Right Logical interfaces also require parameters to setup
communications with other domains.
Some Logical interfaces
Connect. Communicate. Collaborate
Scenario with two
SDH - SDH networks
Connect. Communicate. Collaborate
SDH - SDH scenario
Connect. Communicate. Collaborate
Stitching Data model
Connect. Communicate. Collaborate
• Objects
– Domains…
– Parameters…
• Attributes
– Each object has several attributes (meta data in
most cases)
– Attributes for Parameters have been defined
• Inheritance
– Attributes can inherit their value from the base
definition.
Domains
Connect. Communicate. Collaborate
• Administrative domain
a domain belonging to a certain operational management entity, like a NREN
– Terminating domain
a user domain; can be a full blown network or a single machine
• User domain
a domain that represent an end user
– Linking domain
domain(s) which makes up the path and controlled by the AutoBAHN JRA3
• Source domain
the domain where the path starts
• Destination domain
the domain where the path stops
– Provisioning domain
a domain which is characterised by its provisioning tool (BLUEnet, etc.)
– Technology domain
a domain using a specific technology; like SDH/SONET, Ethernet, IP, OOO
Parameter
•
•
Connect. Communicate. Collaborate
All stitching parameter (s) have the same attributes (meta data):
– Name
– Data
– Dimension ( representation of the data)
– Type ( which logical interface the parameter belongs to)
– Intervention (indicates ways a parameter can be changed)
human, remote, auto, pass
– Involved (which part of the domain is involved in determining the parameter value)
interface, whole domain
– Dependency (dependency on other parameters that determine the data value of the
parameter)
– Logic (how other domains/interfaces take part in determining parameter values)
peering, none, contiguous, path
– Method (of Logic used to compare parameter values)
same, different, min, max, sum, function
– Default
if a parameter value is not specified, this default value should be assigned.
The attribute value can be a single value, a list, a range or a function
Sample parameters, attributes and
values
Connect. Communicate. Collaborate
The stitching engine
Connect. Communicate. Collaborate
• Parameters are grouped for convenience in Logical
interfaces
e.g. Identity, Performance, Physical, Ethernet, SDH/SONET, VCG,
MPLS, IP.
• New parameters can be defined easily
there are no boundaries to the number of parameters provided its
attributes are covered by the Data model
• The stitching engine must be able to handle any number of
parameters
• The stitching engine must be able to properly evaluate all
attributes (metadata) of the parameters in any path
chosen.
Stitching in AutoBAHN
Connect. Communicate. Collaborate
• All relevant domain parameters in the path are gathered from source to
destination domain
• The stitching engine runs in the destination domain of AutoBAHN
system
• The stitching engine proposes possible parameter values for each
domain (semantic web) and a feasibility/schedule check process runs
in each of the domains from destination to source.
• Failure of feasibility/schedule in a domain:
– go back to the source domain (like in RSVP) and try a new path
• The stitching Data model is incorporated in the abstract topology model
(including all attributes)
AutoBAHN reservation
scheduling process
Connect. Communicate. Collaborate
Wrap up…
Connect. Communicate. Collaborate
• Checks have been done on:
– GMPLS/ASON parameters
– GN2-cNIS (common Network Information System)
which holds network/path/etc related schema
– Support on manual building of paths over GEANT+
• The Data model is extendable, flexible and not predetermined
• The parameter attributes (meta data) define how the
parameters are evaluated
• Versitile framework to stitch different domains together, so
thus not only AutoBAHN…
Questions?
Connect. Communicate. Collaborate