You are here: TWiki> WMSMonitor Web>WebDownload3 (revision 1)

NEW Installation for emi-WMS/LB, WMSMonitor 3.0

A completely new version of WMSMonitor is made available, for Pre-View testing.
For the moment being we only deploy sensors in a tarball, and you can use the WMSMonitor server Instance available at INFN-CNAF to visualize your instance data.
Notice that this new version can be installed on emiWMS/LB only on SL5/64 platform.

Here some of the novelties introduced with this new version:

  • New web Interface with separate frames for WMS and LB instances
  • Data collection is now asynchronous, in fact a cron job executes sensors on monitored WMS/LB instances and send data to WMSMonitor server consumer
  • Messaging is now based on Active MQ
  • WMS job workload management rates are now derived exploiting LB api
  • Handling of several LB instances for each WMS
  • both globus and emi-cream JSS case is now handled
  • globus JSS error statistics available

SENSORS INSTALLATION ON INSTANCES TO MONITOR

To be part of the preview, please write to wms-support asking for the tarball. Then follow instruction:

  1. Make sure you have your emi WMS / LB instance installed and you have root privileges on it
  2. $> cd /opt
  3. $> tar -xvzf WMSMonitor.tgz (--> untar the tarball we provided you with)
  4. $> cp /opt/WMSMonitor/sensors/bin/WMSMonitor.cron /etc/cron.d/
  5. Edit /etc/cron.d/WMSMonitor.cron uncommenting the WMS or LB line respectively (depending on the service hosted in your instance)
  6. IMPORTANT --> tell us the hostname of instance to be monitored
  7. Wait till first cron job to start and check whether a file like /tmp/WMSLOCKFILE_1312453801.45 exists
  8. go to INFN-CNAF WMSMonitor 3.0 monitor server with a valid user certificate and flash player in your browser and enjoy...

Note: WMSMonitor "user mapping" functionality requires wmproxy loglevel set a 6 in glite_wms.conf file

WMSMonitor SERVER (Not Available for Download YET: WORK IN PROGRESS)

Adding instances to monitor to WMSMonitor server

  1. Given an LB and a WMS instance to monitor:
    1. Enter Mysql database wmsmon:
    2. $> call insertHost('LBHOSTNAME_WITH_DOMAIN');
    3. $> call insertHost('WMSHOSTNAME_WITH_DOMAIN');
    4. $> call insertLBHost('LBHOSTNAME_WITH_DOMAIN');
    5. $> insert into admin_host_labels(idhost,service,vo,vo_group,service_usage,active,host_owner) values ('TOGET_FROM_hosts_TABLE','WMS','VO->MULTI','','GROUP_USAGE(ex. PRODUCTION)','1','SITE_NAME');
    6. $> insert into admin_host_labels(idhost,service,vo,vo_group,service_usage,active,host_owner) values('TOGET_FROM_hosts_TABLE','LB','VO->MULTI','','GROUP_USAGE(ex. PRODUCTION)','1','SITE_NAME');
    7. $> FROM SHELL: python /opt/WMSMonitor/collector/bin/data_collector_daemon.py stop
    8. $> FROM SHELL: python /opt/WMSMonitor/collector/bin/data_collector_daemon.py start

Configuring Load Balancing in WMSMonitor server

-- DaniloDongiovanni - 2011-12-20

Edit | Attach | Print version | History: r20 | r4 < r3 < r2 < r1 | Backlinks | Raw View | More topic actions...
Topic revision: r1 - 2011-12-20 - DaniloDongiovanni
 
Edit Attach

TWIKI.NET
This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback