This page last changed on Aug 18, 2011 by prodrigu.

Release: Update-09

Summary

Start Date 29 Nov 2010
End Date 02 Feb 2011
Status Released
Release Date 16 Feb 2011
Release Manager Wojciech Lapka
Main Activities
  • MyEGI standalone central instance (egee-NAGIOS-WEB)
  • MyEGI web services
  • Added SAM release to information provider
  • Support for robot certificates
  • Support for configuration of uncertified sites
  • Support of MPI services in topology
  • Yaim cleanup
  • MRS Central: Load OSG services
  • Messaging plugins
Notes None

Validation Steps performed

List of packages updated in this release

These part includes also packages from SAM-Update-08, which was an internal release:https://tomtools.cern.ch/confluence/display/SAMDOC/Update-08+-+internal+release
atp-1.16.7-2.el5.noarch.rpm
atp-web-1.16.7-2.el5.noarch.rpm
egee-NAGIOS-1.0.0-60.el5
egee-NAGIOS-WEB-0.9.0-3.el5 (Only for central installation)
egee-NRPE-1.0.0-19.el5 (Onle when using Nagios remote probe execution)
egee-SNAGIOS-0.4.0-1.el5 (Only for central "Super" Nagios installation)
glite-yaim-nagios-1.2.9-10.el5.noarch.rpm
grid-monitoring-config-gen-0.77.6-1.el5
grid-monitoring-org.ggus-probes-0.7.1-1.el5
grid-monitoring-org.nagiosexchange-probes-0.12-1.el5.x86_64.rpm
grid-monitoring-probes-hr.srce-0.32.2-1.el5
gstat-validation-2.0.44-1.el5
info-provider-nagios-0.4.1-1.el5
mddb-1.0.11-1.el5
mddb-parser-1.0.11-1.el5
mddb-synchronizer-1.0.11-1.el5
msg-consume2db-1.0.19-1.el5 (Only for central egee-NAGIOS-WEB installation)
msg-nagios-bridge-1.0.58-3.el5
myegi-0.4.5-1.el5.noarch.rpm
nagios-gocdb-downtime-0.23.1-1.el5
nagios-proxy-refresh-1.12.0-0.el5
nagios2metricstore-1.0.32-3.el5
perl-MIG-0.5-1.el5
perl-Net-STOMP-Client-0.9.5-1.el5
perl-TOM-1.3-1.el5
sam-release-1.9.0-1.el5
voms2htpasswd-1.8.0-1.el5

Release Notes

  • Please use ATP as topology provider starting from this release.
  • Starting from Update-09 SAM supports usage of robot certificates, instead of MyProxy credentials. This is an optional feature which can be used only if your CA and VO support robot certificates. If your CA supports robot certificates, we suggest switching to robot certificates, as they are easier to maintain. Also robots provide better availability as SAM doesn't depend on availability of MyProxy server. Find more details in SAM-952. The most important variables are listed in the section "Configuration changes".
  • SAM supports changing notification header for emails sent by Nagios. Find more details in SAM-1130. The most important variables are listed in the section "Configuration changes".
  • Support for defining uncertified sites via Yaim has been implemented. Find more details in SAM-1143. The most important variables are listed in the section "Configuration changes". Setting up uncertified sites is also documented here.
  • VO profile has been changed to include VO-dependent metrics only. Find more details in SAM-1178.
  • ATP supports MPI services. Find more details in SAM-413. The MPI services will appear as 5 flavours:
    • MPICH
    • MPICH2
    • MPICH-1
    • OPENMPI
    • OPENMPI-1.
  • Central MRS is loading OSG services.
  • MyEGI no longer requires SSL authentication but uses standard HTTP.
  • After discussion with NDGF it was decided that RLS is not treated as production service. Metric org.arc.RLS has been removed from ARC profile. Find more details in SAM-1238.

Configuration Changes

These part includes also configuration changes from SAM-Update-08, which was an internal release:https://tomtools.cern.ch/confluence/display/SAMDOC/Update-08+-+internal+release
SAM-CA-Update-01 should be installed before you start deploying this release. More details at:

https://tomtools.cern.ch/confluence/display/SAMDOC/SAM-CA-Update-01

Note that after upgrade and before YAIM execution, atp_synchro.conf.rpmnew configuration file should replace the existing one, i.e.
mv /etc/atp/atp_synchro.conf.rpmnew /etc/atp/atp_synchro.conf
YAIM needs to be executed after the upgrade. Note that there's DB upgrade of 'metricstore' and 'atp' schemas so the execution will take longer.
Note that MyEGEE is no longer part of the release. We do not modify the config of existing myegee instances, but on a fresh install MyEGEE is not installed. All configuration variables MYEGEE_* can be removed.

There are many configuration changes in the area of DB Handling. Most importantly there is now only one set of DB parameters (with defaults). You will need to set the DB_PASS to the existing password for the mrs user (normally it would have been MYEGI_DATABASE_PASSWORD.

DB_TYPE=mysql
DB_USER=mrs
DB_NAME=mrs
DB_PASS=

These are used for ATP, MDDB, MRS, MyEGI configuration. All other DB configuration parameters can be removed.

The following SECRET_KEY parameters are no longer used:

ATP_WEB_SECRET_KEY
MYEGI_SECRET_KEY
# optional - turns on ACE support (Service Availability) on MyEGI (SAM-1142):
# This variable can be set only on central instance, do not set it on your Nagios instance,
# because ACE doesn't work in MySQL
MYEGI_ACE=True

# optional - change of notification header (SAM-1130):
NCG_NOTIFICATION_HEADER="CERN Nagios"

# optional - use of robot certificates (SAM-1180):
NCG_USE_ROBOT_CERT=true
# Robot cert and key can be different for each VO
# and standard Yaim VO notation is used
VO_OPS_ROBOT_CERT=/etc/nagios/globus/robot-cert.pem
VO_OPS_ROBOT_KEY=/etc/nagios/globus/robot-key.pem

# optional - add uncertified gLite sites (SAM-1143)
UNCERTIFIED_SITES="SiteA SiteB SiteC"
UNCERTIFIED_WMS=wms.uncert.org
UNCERTIFIED_BDII=bdii.uncert.org

Known Issues

NCG throws error and stops execution when site has no services and ATP used as topology provider.
https://tomtools.cern.ch/jira/browse/SAM-1271
Workaround:
Remove site from ncg.localdb, e.g.: REMOVE_SITE!SITE_NAME

List of Issues fixed in this release

jiraissues: Unable to determine if sort should be enabled.

(Only for central "Super" Nagios installation)

Document generated by Confluence on Feb 27, 2014 10:19