2. About Panlab
• Creates a large scale testing and
experimentation facility by integrating
existing and emerging testbeds
• Achieves scale and maintains
independence through federation
• that enables end-to-end interoperability
testing of platforms, networks and services
• that helps reducing the risks and costs of
large-scale network infrastructure testing
• Panlab has build the glue
4. Value proposition
• For the testbed owners and operators
• Help find “customers”
• Increase utilisation
• Compensate for the investments in building
• For the customer (e.g. researcher, application
developer)
• Help find suitable target environment
• Configure a custom experimental environment
• … friendly users
• A win-win-win situation for the
• testbed owner/operator,
• testbed customer and
• testbed broker (Teagle)
• Open to all collaborations that adhere to the principles
for building Federated, Open, and Trusted research
and experimentation environments
5. Testbed and Experimental Facility
Federation
• Heterogeneous resources are offered by
several network domains
• Domains engage in federation and share
resources
• Federation Organization represents the
federation to 3rd parties
• The federation control tool called Teagle
executes management operations via a control
framework
• Supports broad Future Internet research
• Re-use resources across the boundaries of
domains and communities instead of re-building
infrastructure
• Infrastructure as a Service (IaaS)
6. Panlab Mechanisms - Enablers
• Organisational aspects
• Considered in Panlab SSA
• Panlab Organisation
• (Legal) entity “owning” the testbed federation
• Financing (membership model, etc.)
• Panlab Office
• Operational entity of the federation – adopted in PII
• Frameworks in development – PII project
• Concepts defined in Panlab SSA
• Legal
• Operational
• Technical
7. Panlab Legal Framework
• Target
• Regulation of all related legal issues
• Efficient conclusion of contracts
• Applying of contract templates
• Ensuring individual negotiations
• Federation contracts
• For testbed providers and customers
• For individual testbeds and testing sessions
• Addressed issues
• IPR, Confidentiality, Access rights, etc.
8. Operational Panlab Framework
• Testbed specification and integration
• Panlab repository
• Search for testing configuration
• Customers’ requirements
• Set-up of testing sessions
• Execution of tests
• Configuration and validation
• Collection and evaluation of results
• Usage of existing results and configurations
10. Federation Architecture
§ Registry & Repository
TEAGLE
U1 § Creation Environment
End User Customer
§ Request Processor
Domain Domain
§ Orchestration Engine
§ Web Portal
U2 U3
T1
Domain Domain
Manager Manager
RA RA RA RA RA RA
T2 T2
Domain B
Domain A
IGW IGW
T2 I2 T2
B1 A1
I1
11. How does it work?
search,request & describe & configure
configure infrastructure resources
Panlab Customer Panlab Partner
Panlab Office
TEAGLE
install, configure &
manipulate resources
control
Panlab
resources
Repository
3G
Testbed Resources
18. TEAGLE
A deployed VCT
VPN
VOIP user
agent
Customer
Octo
PTM Oulu, Finland
UoP B.CR
PTM 1
Echo
LINUX
IGW
IGW
Asterisk
config
A.RC
1
Dialtone
EICT
PTM
Patras, Greece IGW
C.CR
3
Berlin, Germany
19. Experimental Facility Resource
Federation with Teagle
• We have developed a Resource Federation Framework
• Different administrative domains provide testbed resources
• Administrative domains can be existing and upcoming
testbeds or other organizations that want to offer resources
• Heterogeneous resource federation allows cross-domain
experiments using heterogeneous resources (e.g. sensors,
CPU, memory, services) from different testbeds
• Open Framework
• Any provider
• Any resource
• Recursive domain / federation model
• Easy integration of resources following a generic resource
adaptor (device driver) concept
• Building upon our existing work will speed up the
integration process and leverage previous investments
www.fire-teagle.org/tutorials.jsp
20. What Exists? How to Join?
• Existing Prototypes:
• Federation Portal
http://www.fire-teagle.org/
• Design Environment (access is currently
limited to selected testers)
http://www.fire-teagle.org/tutorials.jsp
• Domain Manager to federate resources
from an administrative domain
http://trac.panlab.net/trac/wiki/CorePTM
• Resource Adaptors (RA) to allow
remote configuration. For specialized
resources RAs need to be developed.
Different implementation options are reg set
available such as Java, OSGI, Python.
Howtows are available. m m
• In addition to the prototypes,
r r r r r r
conceptual work such as a federation
model, resource models, etc. is also Domain A Domain B
available Sebastian Wahle, Thomas Magedanz, and Anastasius Gavras. Towards the
Future Internet - Emerging Trends from European Research, chapter
Conceptual Design and Use Cases for a FIRE Resource Federation
Framework. IOS Press, 2010. To appear.
21. Future directions
• Management and security
• Monitoring, Fault management, Policy based
management
• Reach out to other European and international
testbed communities
• Serve academic communities
• Through easy and free access
• Serve business customers
• Through service guarantees
• Open in various directions