SG BBmSAM Portal

From EGEE-see WIki

Overview Page

BBmSAM Portal is a part of BBmSAM Platform.

To explain the operations of BBmSAM Portal we will use a sample screen-shot (edited to illustrate some specifics):

Heading text is the name of BBmSAM server, in this case it is BBmSAM located at BA-01-ETFBL site in SEE-GRID-SCI project.

After that there is a list of all monitored services as links to their respective pages, but we will get back to that in Latest results section.

Main part of the front page is a table with summary results (overview table) that contains site name, country, tier, certification status and production type of every listed site. "SERVICE STATUS" column contains list of services, node name for respective service, latest critical test status and time since last critical test status change (uptime). Uptime is in days (d) or hours (h), unless uptime is over 31 days and indicated as 31+.

All test statuses are color-coded as follows:

• Critical test status is: OK - black, ERROR - red, CRITICAL - purple, MAINT - gray, WARNING - brown. If there is no data for over 24 hours, the background is gray
• Uptime value: 7+ days - black, 3+ days - green, 1+ days - blue, less than 1 day - red, less than 6 hours - red with yellow background

If one wants to see history for a specific service/node - click on node name (ie, ce64/c02/n00/...).

Latest Results

Services page show latest results for all instances of a specified service (CE in sample screen-shot). The results table contains node name, site name, critical test status and statuses of individual tests. Tests are ordered by criticality so that critical test come first and they are marked by being bold.

If one clicks on a specific test result, detailed logging information is presented to user, for example:

Overview
Node: grid01.elfak.ni.ac.yu
Test: CE-sft-lcg-rm-rep
Date: 2009-01-14 13:55:02
Detailed data

Checking replication to Central SE (se.phy.bg.ac.yu)

Netork timeout on LFC: LFC_CONNTIMEOUT=10 LFC_CONRETRY=1 LFC_CONRETRYINT=2
Network and search timeouts on BDII set for lcg-utils: LCG_GFAL_BDII_TIMEOUT=10
Connect, send and receive timeouts on SE are set to 120 sec.


Replicate the file from the default SE to se.phy.bg.ac.yu

+ lcg-rep -t 120 -v --vo seegrid -d se.phy.bg.ac.yu lfn:sft-lcg-rm-cr-grid04.elfak.ni.ac.yu.090114135405.5102728
Using grid catalog type: lfc
Using grid catalog : grid02.rcub.bg.ac.yu
grid02.rcub.bg.ac.yu: /grid/seegrid/SAM/sft-lcg-rm-cr-grid04.elfak.ni.ac.yu.090114135405.5102728: No such file or directory
lcg_rep: No such file or directory
+ result=1
+ set +x

List replicas to check if replication was really successful

+ lcg-lr --vo seegrid lfn:sft-lcg-rm-cr-grid04.elfak.ni.ac.yu.090114135405.5102728
grid02.rcub.bg.ac.yu: /grid/seegrid/SAM/sft-lcg-rm-cr-grid04.elfak.ni.ac.yu.090114135405.5102728: No such file or directory
lcg_lr: No such file or directory
+ set +x

Clicking on node name takes user to History page for a chosen node.

History

History page contains historical information for a specified service at specified node and is presented as in this sample:

The information is exactly the same as in Latest results section but allow history for either a specified number of days or a specified time period by choosing Date to date and entering start and end date/time.