Tags:
create new tag
,
view all tags
---+!! CEMon Functional Description The CEMon service is responsible for providing information coming from the Computing Element (CE). The "type" of information managed by CEMon is defined by =plugins= (also known as =sensors=) that can be plugged into the CEMon core engine. Each plugin is basically responsible to deal with a specific "type" of information. For each plugin (identified by a =topic= name), one or more =dialects= (representing how the relevant information is rendered) are available. Existing CEMon sensors are: * *CE_MONITOR*. Returns CE information, according to the Glue Schema. * Topic name: =CE_MONITOR= * Dialects: * =ISM_LDIF=: to get information in LDIF format Glue Schema v. 1.1 compliant * =ISM_CLASSAD=: to get information in classad format Glue Schema v. 1.1 compliant * =ISM_LDIF_GLUE_1.2=: to get information in LDIF format Glue Schema v. 1.2 compliant * =ISM_CLASSAD_GLUE_1.2=: to get information in classad format Glue Schema v. 1.2 compliant * *OSG_CE* Returns CE information, according to the Glue Schema, suitable for OSG needs. * Topic name: =OSG_CE= * Dialects: * =LDIF=: to get information in LDIF format * =OLD_CLASSAD=: to get information in classad format, formatted according the needs of OSG * =NEW_CLASSAD=: to get information in classad format,formatted according the needs of the gLite * =RAW=: to get information as returned by the called script (i.e. unfiltered) * *GridICE* Returns !GridICE information * Topic name: =org.gridice.extended= * Dialects: * =LDIF=: to get information in LDIF format * *CREAM job* Returns CREAM job state information * Topic name: =CREAM_JOBS= * Dialects: * =CLASSAD=: to get information in classad format By implementing specific sensors, the CEMon service can also be configured to collect and provide other information types. It is possible to interact with the CEMon service in a synchronous way (i.e. the client queries the CEMon service to get the required info) or asynchronously (i.e. the client can subscribe to get asynchronous notifications coming from the CEMon service). Moreover the CEMon administrator can configure predefined subscriptions, so the specified clients are automatically notified with asynchronous events, without the need of an explicit subscription. Specific policies and specific actions can be set on CEMon subscriptions. For example if is possible to define a subscriptions so that the client is notified only when certain conditions are satisfied (e.g. when the CE queue is empty or the number of queued jobs is less than a certain value). -- Main.MassimoSgaravatto - 2011-04-20
E
dit
|
A
ttach
|
PDF
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
M
ore topic actions
Topic revision: r2 - 2011-04-20
-
MassimoSgaravatto
Home
Site map
CEMon web
CREAM web
Cloud web
Cyclops web
DGAS web
EgeeJra1It web
Gows web
GridOversight web
IGIPortal web
IGIRelease web
MPI web
Main web
MarcheCloud web
MarcheCloudPilotaCNAF web
Middleware web
Operations web
Sandbox web
Security web
SiteAdminCorner web
TWiki web
Training web
UserSupport web
VOMS web
WMS web
WMSMonitor web
WeNMR web
General Doc
Functional Description
Architecture
Known Issues
User Doc
CEMon CLI User Guide
System Administrator Doc
System Administrator Guide for CEMon for EMI-1
System Administrator Guide for CEMon for EMI-2
System Administrator Guide for CEMon for EMI-3
CEMon Service Reference Card for EMI-1
CEMon Service Reference Card for EMI-2
CEMon Service Reference Card for EMI-3
Other Doc
Testing
Credits
CEMon Web utilities
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback