The GlueDomains database implementation is presently
centralized, which limits the scalability of the whole structure to a
few tens of domains (based on a prospective simulation).
However the present solution exhibits several interesting features:
- a monitoring host autonomously downloads the description of
its activity from the GlueDomains server: once the
gluedomains daemon is started, it detects network interfaces and
configures the monitoring sessions without human intervention;
- a monitoring host keeps its activity synchronized with the
content of the database;
- the inability to carry out a certain monitoring task is harmless,
as well as the unreachability of the centralized database.
- the update of the database is semi-automatic: a script helps the
compilation of its content, starting from XML descriptions of the
activity of each monitoring host. In practice this means that the
human interface is O(n).
We plan to shift to a fully distributed database, cached on each
monitoring host, using a gossip based technique.
In this frame, the MySQL technology will be probably dropped: a
new release, not yet distributed, implements a SOAP interface to the
next: Theodolite management
previous: GlueDomains: concepts@work
up: A modular approach to Grid Connectivity Monitoring