© DSRG 2001 Cross Grid Workshop - Kraków 20011 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 1

Krzysztof Zieliński, Sławomir Zieliński

University of Mining and Metallurgy

{kz, slawek}@ics.agh.edu.pl



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).



Servers, Networks & Node OSes

Application Services Core

ServicesDRM

• Core Services: Grid Environmental services

• Distributed Resource Management (DRM): Management of work and computing resources

• Application Services: Support those applications programmed for Grid

Applications DSRG’s contribution



Remote data access, transfer, replication and caching

Resource accounting; capacity planning; QoS reporting

Resource monitoring and alarming; app monitoring, event automation; system management

Work scheduling; load balancing; sharing policies; resource clustering and access control; resource reservation; remote execution; fault tolerance for work

Description

Workload Management

Data Management

Performance Management

Resource Management

Function



Event driven system

Publish – subcribe pattern implementation

Asynchronous notification

Event delivery subsystem with in-built QoS

Powerfull filtering mechanisms



Portablity across different operating system: Linux, Solaris, Windows, etc.

Configurability

Scalability

Manageability

JMX and Jiro usage



SNMP – de-facto standard

SNMP Gateway Agent should be constructed



Agent

Agent

JiroStation

SNMPService

LogService

EventService

LookupService

Lookup S ervice B rowser


SNMPDevice

Deployer

Monitor

DeployLookupSNMPService

Agent specific function



:SNMPService :Agent :LogService :EventService :Client

write log

send event

subsrcibe event

send event

SNMPPollData

getAgentProxy

Run agent specyfic function

:External Device

Poll Data











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



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 RMI-

codebase property set.



Where Jiro extends Jini (II)

• Extended Services– Event Service

• Instead of 1-n source-listeners there is n-1-n sources-service-observers/responsibles

• New Services– Logging of messages– Scheduling of events– Persistence of services– Security (based on JAAS) of method calls– Controllers and Logical Threads





Client runs the Lookup Service Browser

Prerequisites:• start Jiro environment• deploy TeleCons into Jiro-station• register TeleCons in Lookup Service

System Usage




TeleCons Proxy

dow

nlo

ad

Jini Layer

Jiro Layer

Client Layer

Lookup Service Browser is the mean of getting TeleCons Proxy.

Provides:• easy usage of service• user friendly UIs• displays actual system’s state

Lookup Service

TeleCons Item

Base Services

TeleCons Serviceregister re

gist

er



Client A

ServerLookup Service

Register

RMILookup Service B rowser

Browser

Lookup

Download

TeleCon.

Client B

TeleConProxy

Lookup Service B rowser

BrowserTeleCon

Proxy

TeleConProxy

Download

Lookup

MM-stream



Client B

Client A

doctorA

*****

doctorB

*****



Client B

Client A

Clicking Agree means that all

Conference parameters

have been negotiated.

The Multimedia TeleConsulting begins





How does it work?



Communication Components

• Connectorsestablish 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.



The Notification Model• Local and Remote Listeners



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



SNMP toolkit• Simple Network Managemet Protocol

– Integrates SNMP managemet into JMX-based architecture.

– Representing SNMP MIB (Mangement Information Base) as Mbeans.



Documents

© DSRG 2001 Cross Grid Workshop - Kraków 20011 Krzysztof Zieliński, Sławomir Zieliński University of Mining and Metallurgy {kz, slawek}@ics.agh.edu.pl