Deployment and Testing of MaDDash and OMD for WLCG perfSONAR-PS Monitoring

This page documents testing and deploying MaDDash and OMD (Open Monitoring Distribution; see http://omdistro.org/start) for WLCG perfSONAR-PS monitoring. We need to determine how this system might work for WLCG needs.

Initial Deployment

To test the deployment I am using a new SL6.4 64-bit VM created on our AGLT2 VMware system. The system was setup with 1 processor, 4GB of RAM and 64GB of disk. The OS in VMware is CentOS 64-bit (/4/5/6). I used our local provisioning system to do the "bare-metal" install of the OS. Others can use whatever infrastructure they have which does the equivalent.

Once the system is built I add in three yum repositories:

1) Make sure EPEL is installed. rpm -Uvh "http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm"

2) Then to get OMD use rpm -Uvh "http://labs.consol.de/repo/stable/rhel6/i386/labs-consol-stable.rhel6.noarch.rpm"

3) Get the perfSONAR-PS repository in place (I am using 3.3.2 RC): rpm -Uvh  "http://software.internet2.edu/branches/release-3.3.2/rpms/el6/x86_64/RPMS.main/Internet2-repo-0.4-1.noarch.rpm"

It may be a good idea to run yum  update to make sure you are current. FYI my repolist ended up like:

[root@maddash ~]# yum  repolist
Loaded plugins: security
repo id                       repo name                                                           status
Internet2                     Internet2 RPM Repository - software.internet2.edu - main                  230
epel                          Extra Packages for Enterprise Linux 6 - x86_64                      9,709+306
labs_consol_stable            labs_consol_stable                                                         16
rpmforge                      RHEL 6.4 - RPMforge.net (formerly dag)                                  4,650
sl                            Scientific Linux 6.4 - x86_64                                           6,449
sl-security                   SL 6.4 security updates                                                   936
umatlas                       umatlas SL 6.4                                                             69
vmware-tools                  vmware-tools-collection                                                    43
repolist: 22,102

Install MaDDash

To install Maddash I followed the instructions at https://code.google.com/p/perfsonar-ps/wiki/MaDDashInstall.

yum  install  maddash

NOTE: This pulled in 81 packages on my system.

Install OMD

To install OMD : yum  install omd-1.10

NOTE: This pulled in 25 packages on my system.

Next Steps

We eventually need to setup and configure MaDDash and OMD for our use-case.

The idea is to use OMD to monitor the perfSONAR-PS Toolkit nodes and basic services We will setup host-groups based upon cloud and/or VO.

MaDDash will be used to visualize network measurements being made by the perfSONAR-PS Toolkits.

In both cases we need to get the lists of nodes and corresponding metadata for the WLCG perfSONAR-PS monitoring. Fortunately we have the "mesh-configs" already in place which should provide us with the correct information. The list of mesh-configs is stored at https://twiki.cern.ch/twiki/bin/view/LCG/MeshRegionList We need to be able to parse these to extract the relevant details.

Setup OMD

We want to setup OMD and create a new 'site' but first we need to fix a known bug on RHEL-like systems. From http://everyday-tech.com/archives/1999:

"In CentOS 6.4 there is a small issue with pathing in /usr/bin/omd. On line 794 You want to add the following highlighted text….

file(“/etc/fstab”, “a+”).write(“tmpfs */opt*%s tmpfs noauto,user,mode=755,uid=%s,gid=%s 0 0\n” % \"

I edited /usr/bin/omd and added the missing /opt.

Now we can setup omd with omd  setup. This adds and configures some packages. Note it chkconfigs httpd on. If you have some security in place you may need to configure to allow httpd to be accessible as required.

Once OMD is setup we can create a new 'site'. I choose the sitename 'WLCGperfSONAR'. We can run 'omd create' now:

[root@maddash ~]# omd create WLCGperfSONAR Adding /omd/sites/WLCGperfSONAR/tmp to /etc/fstab. Restarting Apache...OK Creating temporary filesystem /omd/sites/WLCGperfSONAR/tmp...OK Created new site WLCGperfSONAR with version 1.10.

The site can be started with omd start WLCGperfSONAR. The default web UI is available at http://maddash.aglt2.org/WLCGperfSONAR/ The admin user for the web applications is omdadmin with password omd. Please do a su - WLCGperfSONAR for administration of this site.

So we are setup and ready to run. We should first start the site, login and change the default password. Here we hit another snag (at least on my system):

[root@maddash ~]# omd start WLCGperfSONAR Starting dedicated Apache for site WLCGperfSONAR...OK Starting rrdcached...OK Starting npcd...OK Starting nagios...OK Initializing Crontab...You (WLCGperfSONAR) are not allowed to use this program (/usr/bin/crontab) See crontab(1) for more information close failed in file object destructor: Error in sys.excepthook:

Original exception was: ERROR

We need to add the new 'WLCGperfSONAR' user to the /etc/cron.allow on this system and retry:

[root@maddash ~]# omd start WLCGperfSONAR Starting dedicated Apache for site WLCGperfSONAR...OK Starting rrdcached...OK Starting npcd...OK Starting nagios...OK Initializing Crontab...OK

Worked! We login via the web page and change the omdadmin password. Easiest way to do this is to open your new site URL http://maddash.aglt2.org/WLCGperfSONAR/ If you have allowed http access via any firewall it should prompt for a user/password. Use 'omdadmin' and 'omd'. It will take you to the main site page showing lots of applications you can use. Click on the "Check_MK" version and go to the 'WATO Configuration' on the left panel. Select 'Users and Contacts' and then you can click on the green pencil icon ("Properties") next to the 'omdadmin' account and setup a new password. It will immediately prompt you to re-login with the new password.

OMD WLCGperfSONAR Configuration

To configure the site you could use the WATO interface on the web or you can login and use command line tools. WATO may be an option we can explore later. For now, login as root on the new system and 'su - WLCGperfSONAR' to become the new site owner/user. The "root" of the site is in /omd/sites/ which is /omd/sites/WLCGperfSONAR in our case.

The easiest way to use/configure OMD is to exploit check_mk. The configuration files are in /omd/sites/WLCGperfSONAR/etc/check_mk. The main file is appropriately called main.mk. A

-- ShawnMcKee - 26 Dec 2013

Edit | Attach | Watch | Print version | History: r8 | r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2013-12-26 - ShawnMcKee
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback