This page last changed on May 11, 2011 by prodrigu.
Release: Update-06
Summary
Start Date |
27 Sep 2010 |
End Date |
22 Oct 2010 |
Status |
Released |
Release Date |
27 Oct 2010 |
Release Manager |
James C |
Main Activities |
- Finalize single DB merge
- ATP features for VO feeds
- MyEGI first beta release
- Update Internal version of Nagios to 3.2.3
|
Notes |
Update-06 Kickoff Meeting : 100927-Update-06-Start |
Validation Steps performed
- Outlined in SAM-847
- Announced for Stage Rollout 27/Oct/2010
- Cleared staged rollout 15/Nov/2010 (20 days in Staged Rollout)
List of packages updated in this release
Release Notes
- Note that Update-05 was an internal release, so all the changes that are part of Update-05 will be part of Update-06 (i.e. more RPMs will have changed than just the list above. The additional rpms from Update-05 are:
The following package is upgraded in EPEL:
| Before running NCG to upgrade you must run the following script: myegee-old-create.sh. It will create a myegee instance (at https:NAGIOS_HOST/myegee-old/) to point to the old myegee databases. |
| Update-06 has a major change in the way databases are used on the regional Nagios instances. From this point on a single database schema is used to store the contents of MDDB, ATP and MRS. You neee to specify new parameters in YAIM - These are described in Update-05 Release Notes |
- This update will install MyEGI for the first time, so you need to set several new YAIM variables for MyEGI:
Variable |
Description |
Default / Optional |
Example |
MYEGI_ADMIN_NAME |
System administrator name |
Optional |
David Horat |
MYEGI_ADMIN_EMAIL |
System administrator email |
Optional |
example@example.com |
MYEGI_DEFAULT_PROFILE |
Default nagios profile |
Default: ROC_CRITICAL |
ROC |
MYEGI_REGION |
Default region to show |
Optional |
Italy |
MYEGI_DATABASE_ENGINE |
Type of DB (values: mysql/oracle) |
Default: mysql |
oracle |
MYEGI_DATABASE_USER |
The database username for the MyEGI portal |
Default: myegi |
myegi |
MYEGI_DATABASE_NAME |
The database name to use by the MyEGI portal |
Default: mrs |
mrs |
MYEGI_DATABASE_PASSWORD |
The database password for the MyEGI portal |
MANDATORY |
lemon |
MYEGI_DATABASE_HOST |
The database hostname |
Default: localhost |
localhost |
MYEGI_DATABASE_PORT |
The database port |
Optional |
3306 |
MYEGI_DEBUG |
Turn on/off debug mode for MyEGI (values: True/False) |
Default: False |
True |
- Setting LFC and SE for WN tests from YAIM. Set JOBSUBMIT_WN_LFC and/or JOBSUBMIT_WN_SE_REP variables in site-info.def if you want to point to a specific LFC and/or SE on WN for replica management tests (org.sam.WN-Rep{Cr,Rep}). If set, config_ncg YAIM function creates $NCG_MAIN_DB_DIR/jobsubmit file, which will contain MODIFY_METRIC_PARAMETER definitions for NCG to configure respective Nagios service objects providing --wn-lfc / --wn-se-rep parameters to {CREAM}CE-probe probes. If not set, metrics will use default LFC/SE, which can be checked by running ./CE-probe -h and looking for --wn-lfc --wn-se-rep parameters. The LFC should be writable.
Known Issues
- MyEGI has an issue with rendering services that have been removed and added back again in the case where no new test results are received after they come back - there is a discrepancy between the status and the history views SAM-881@jira
- There is an issue with replica management tests segfaulting in lcg_util in lcg-gt/lcg_gt3() on certain combination of parameters returned by SRM (org.sam.SRM-GetTURLs metric). The issue was investigated with NGI_IT admins (ggus #63399). Bug report #74459 against lcg_util was submitted and confirmed by lcg_util developers. updated on Thursday, October 28 2010 org.sam.SRM-GetTURLs was re-written to use lcg_util CLI lcg-gt to avoid the segfault in lcg_util affecting the metric. If segfault detected - the metric returns WARNING. The issue was tracked in SAM-892@jira.
List of Issues fixed in this release
jiraissues: Unable to determine if sort should be enabled.
Metrics for this release
gadget: Error rendering gadget [ https://tomtools.cern.ch/jira/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:pie-chart-gadget/gadgets/piechart-gadget.xml ] projectOrFilterId=filter-10060&statType=issuetype&isConfigured=true&refresh=false
gadget: Error rendering gadget [ https://tomtools.cern.ch/jira/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:average-age-chart-gadget/gadgets/average-age-gadget.xml ] projectOrFilterId=filter-10060&periodName=daily&daysprevious=90&isConfigured=true&refresh=false |
gadget: Error rendering gadget [ https://tomtools.cern.ch/jira/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:pie-chart-gadget/gadgets/piechart-gadget.xml ] projectOrFilterId=filter-10060&statType=components&isConfigured=true&refresh=false
gadget: Error rendering gadget [ https://tomtools.cern.ch/jira/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:created-vs-resolved-issues-chart-gadget/gadgets/createdvsresolved-gadget.xml ] projectOrFilterId=filter-10060&periodName=daily&daysprevious=30&isCumulative=true&showUnresolvedTrend=false&versionLabel=major&isConfigured=true&refresh=false |
|