View
213
Download
0
Category
Preview:
Citation preview
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
1
A File System Servicefor the Venice Service Grid
33rd Euromicro
28-31August 2007
Lübeck, Germany
Markus HillenbrandUniversity of Kaiserslautern, GermanyIntegrated Communication Systems Lab
email: hillenbr@informatik.uni-kl.de
Markus Hillenbrand, Joachim Götze, Paul Müller
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
2
A Grid Classification
• Compute Gridsprovide access to CPU cycles → e.g. clusters
• Data Gridsprovide access to large data storage → e.g. data bases
• Resource Gridsprovide access to resources → e.g. special hardware
• Service Gridsprovide functionality by combining resources with algorithms
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
3
What is a Lightweight Service Grid?
• A Service Grid …– Abstracts from underlying hard- and software– Hides the complexity of its resources– Focuses on the end-user– Provides intuitive means for access
• A Lightweight Service Grid …– Is easy to deploy
(i.e. quick service creation and deployment)– Is easy to maintain
(i.e. tool support for management, monitoring, and configuration at runtime)
– Is easy to use(i.e. no installation for end-users, GUI for access)
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
4
What is the Venice Service Grid?
• A software infrastructure:– Based on a service-oriented architecture (SOA) – With focus on openness, dependability and security– Service deployment on the Internet
• A set of services:– Service management at runtime– Service information and access– Service collaboration and communication– Services for building applications upon
• A runtime environment– For service development and deployment– For client development and service access
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
5
A Venice Service Provider
• Management Services– User Management– Resource Management– Service Management
• Information Services– User data– Service data– Cross-domain communication
• Application Services– Horizontal:
for all application domains– Vertical:
for a special application domain
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
6
File System Service (Overview)
Related Work• Amazon Simple Storage
Service S3– Store, delete, access from
anywhere– Access Protocols:
• SOAP• REST• Torrent
• Grid Computing:– dCache / OGSA-DAI– Large files and data sets
Venice Service Grid• Web service interface• Meta data
– File information– Access control lists
• Virtual file system– Service local file storage– Mount remote data
stores• (S)FTP• HTTP(S)• Other (Web) services
– Apache commons VFS
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
7
File System Service (Architecture)
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
8
A Presence Servicefor the Venice Service Grid
33rd Euromicro
28-31August 2007
Lübeck, Germany
Markus HillenbrandUniversity of Kaiserslautern, GermanyIntegrated Communication Systems Lab
email: hillenbr@informatik.uni-kl.de
Markus Hillenbrand, Aneta Kabzeva, Paul Müller
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
9
A Venice Service Provider
• Management Services– User Management– Resource Management– Service Management
• Information Services– User data– Service data– Cross-domain communication
• Application Services– Horizontal:
for all application domains– Vertical:
for a special application domain
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
10
What is „Presence“?
• RFC 2778:
“A presence system allows users to subscribe to each other and be notified of changes in state.“
IETF IMPP Working Group
Presence Service
Presentity W atcher
Presentity User Agent W atcher User Agent
Principa l
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
11
Abstract Model
• Presence / Watcher User Agent:– (Graphical) interface of a system
entity for a real system user (“Principal”)
• Presentity:– Provides presence information to
the Presence Service
• Watcher (Subscriber, Fetcher):– Receives presence information
from the Presence Service
• Presence Service:– Communication bridge between
Presentity and Watcher
Presence Service
Presentity W atcher
Presentity User Agent W atcher User Agent
Principa l
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
12
Presence Information Data Format
• Adheres to RFC 3863• Status
– Shows availability– Shows activity– Shows location
• Contact (optional)– Contact address– Contact priority
• Note (optional)– Any textual note
• Timestamp– Last change
• Other Markup (optional)– Any extension
Presence In form ation
Presence Tuple
O ther M arkup
...
N ote
T im estam p
Status
Basic (open, c losed)
Erweiterungselem ente
C ontact
C ontact Address
Extensions
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
13
Functionality• Presentity
– Persistent interface to the Presentity User Agents
• Watcher– Persistent interface to the Watcher
User Agents• Presence Information Manager
– Subscribe to the Presence Service– Unsubscribe from the Presence
Service– Search for users
• Watcher Manager– Management of presentity‘s watchers
• Subscriptions Manager– Management of watcher‘s
subscriptions• Filter Manager (RFC 4660, 4661)
– Manages filters of watchers– Filters data sent to watchers
WatcherPresentity
ConfirmedSubscriptions
Manager
Presence Information
Manager
WatcherManager
OpenSubscriptions
Manager DeniedSubscriptions
Manager
FilterManager
31 August, 2007
ICSY Lab, University of Kaiserslautern, Germany
14
Thank you for your attention.
Recommended