Cross Grid Workshop - Kraków 2001
1
Krzysztof Zieliński, Sławomir Zieliński
University of Mining and Metallurgy
{kz, slawek}@ics.agh.edu.pl
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
2
Our contribution to the project will include network
infrastructure monitoring tools. What we are especially
interested in is as follows:
• collecting information about network and it’s nodes’ load and
activities
• managing the network architecture
We are not going to concentrate on application monitoring.
The software we are going to develop will support network
management applications (e.g. performance metering), as well as
network-aware computational ones (e.g. task scheduling).
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
DSRG’s
contribution
Applications
Application
Services
DRM
3
Core
Services
Servers, Networks & Node OSes
• Core Services: Grid Environmental services
• Distributed Resource Management (DRM): Management
of work and computing resources
• Application Services: Support those applications
programmed for Grid
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
4
Function
Description
Workload
Management
Work scheduling; load balancing; sharing policies;
resource clustering and access control; resource
reservation; remote execution; fault tolerance for work
Resource
Management
Resource monitoring and alarming; app monitoring,
event automation; system management
Performance
Management
Resource accounting; capacity planning; QoS reporting
Data
Management
Remote data access, transfer, replication and caching
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
5
Event driven system
Publish – subcribe pattern implementation
Asynchronous notification
Event delivery subsystem with in-built QoS
Powerfull filtering mechanisms
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
6
Scalability
Configurability
Manageability
Portablity across different operating system:
Linux, Solaris, Windows, etc.
JMX and Jiro usage
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
7
SNMP – de-facto standard
SNMP Gateway Agent should be constructed
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
8
SNMPDevice
JiroStation
LookupService
SNMPService
EventService
Agent
Deploy
LogService
Lookup Service Browser
Monitor
© DSRG 2001
Agent
Lookup
SNMPService
Lookup Service Browser
Deployer
Agent specific function
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
9
:External
Device
:SNMPService
:Agent
:LogService
:EventService
:Client
SNMPPollData
subsrcibe event
Poll Data
send event
send event
write log
getAgentProxy
Run agent specyfic function
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
10
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
11
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
12
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
13
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
14
Jiro pieces in Common with
Jini
The Jiro implementation takes advantage of Jini by
using some of its interfaces and implementation code
(not a requirement of the FMA).
These parts of Jiro are parts of Jini:
• Leasing
• Lookup Service
• Transaction Service
Valid in Jiro ==> valid in Jini
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
15
Where Jiro extends Jini (I)
Stations include:
• Acceptor-Referent pattern supports:
– Remote static invocation
– Remote constructors
– Context mechanism for security, transactions, controllers
and logical threads
• Remote deployment of services
– Get the jar files into the right locations with the right RMIcodebase property set.
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
16
Where Jiro extends Jini (II)
• Extended Services
– Event Service
• Instead of 1-n source-listeners there is n-1-n sourcesservice-observers/responsibles
• New Services
–
–
–
–
–
© DSRG 2001
Logging of messages
Scheduling of events
Persistence of services
Security (based on JAAS) of method calls
Controllers and Logical Threads
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
17
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
18
System Usage
Prerequisites:
• start Jiro environment
• deploy TeleCons into Jiro-station
• register TeleCons in Lookup Service
Client runs the Lookup Service Browser
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
19
Provides:
• easy usage of service
• user friendly UIs
• displays actual system’s state
Lookup Service Browser is the mean of getting
TeleCons Proxy.
Lookup Service Browser
Client Layer
Jini Layer
© DSRG 2001
TeleCons
Service
download
Jiro Layer
TeleCons
Proxy
Base
Services
TeleCons
Item
Lookup Service
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
20
Lookup Service
Server
Register
Lookup
TeleCon
Proxy
Lookup Service Browser
Browser
TeleCon
Proxy
RMI
Download
Download
MM-stream
Client A
© DSRG 2001
TeleCon.
Lookup
Lookup Service Browser
Browser
TeleCon
Proxy
Client B
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
doctorA
*****
21
doctorB
*****
Client A
Client B
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
22
Clicking Agree means that all
Conference parameters
have been negotiated.
The Multimedia TeleConsulting begins
Client A
Client B
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
23
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
24
How does it work?
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
25
Communication Components
• Connectors
establish a point-to-point connection beetwen an agent and a management
application, each running in a separate JVM.
– Connector Heartbeat
allows both the agent and manager applications to detect when
a connection is lost.
• Proxy MBeans
• Protocol Adaptors
Translation between different protocols.
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
26
The Notification Model
• Local and Remote Listeners
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
27
Security
• Password protection
(Mostly manager applications).
• SNMP Access Control Lists
(e.g. List of authorised managers’ hosts names).
• HTTP/HTTPS
• Context Checking
(The context could be an arbitrary object that your code can use to determine
whether or not to allow the request).
• Secure Dynamic Loading
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
28
SNMP toolkit
• Simple Network Managemet Protocol
– Integrates SNMP managemet into JMX-based
architecture.
– Representing SNMP MIB (Mangement Information
Base) as Mbeans.
© DSRG 2001
www.cs.agh.edu.pl
Cross Grid Workshop - Kraków 2001
© DSRG 2001
29
www.cs.agh.edu.pl