Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Agenda-10-02-2014"

From EGIWiki
Jump to navigation Jump to search
Line 17: Line 17:
== 1.2 UMD release ==
== 1.2 UMD release ==


* UMD [http://repository.egi.eu/2014/01/29/release-umd-3-4-0/ 3.4.0] was released 29/01/2014 and contained the following components:
* '''UMD [http://repository.egi.eu/2014/01/29/release-umd-3-4-0/ 3.4.0]''' was released 29/01/2014 and contained the following components:





Revision as of 13:24, 3 February 2014

Audio conference link Conference system is Adobe Connect, no password required.
Audio conference details Indico page



1. Middleware releases and staged rollout

1.1 News from URT

1.2 UMD release

  • UMD 3.4.0 was released 29/01/2014 and contained the following components:


  • CREAM TORQUE v. 2.1.2: This release fixes the wrong total cpu count from PBS infoprovider together with a dependency issue with lcg-info-dynamic-scheduler
  • ARC-CE v. 4.0.0: This is a major release of ARC-CE and include updates for both server and client tools. Among several new features now ARC client tools use by default the new client-side BDB job storage if available this leads to an backwards incompatible since jobs stored in xml file will not be accessed.
  • QCG COMP v. 3.2.0 : This release provides and optimization of the GetFactoryAttributes method together with an extension element in SLURM module and some bug fixes.
  • BDII-CORE v. 1.5.5: On this release there a new version of glite-yaim-bdii that sets the top BDII cache validity to 4 days by default. Also this release also contains a new version of glue-validator-cron that logs only the results for full EGI profile GLUE 2 validation.
  • BDII-TOP v. 1.1.4: This release decommissions the FCR (Freedom of Choice of Resources) mechanism that is no longer needed in the top BDII.

Messaging:

  • QCG NOTIFICATION v. 3.2.0 : This release provides server improvements like the option for disabling Current Messages and several bugfixes.
  • GridSite v. 2.2.0 : This is a minor release of GridSite addressing the issue of key lengths being hard-coded at 512 bits. It increases the default key length to 1024 bits, and exposes new functions in the API to accepts custom key lengths.

1.3 Staged rollout updates

1.3.1 WMS issues

  • At the moment there are 5 major open issues with WMS:
    • There are two problems regarding with the proxies that in some cases can still generate 512 bits proxies:
      • The WMS Purger still uses 512 bits which is hard-coded and can update wms's proxy with the worng 512 bits ([Problem https://issues.infn.it/jira/browse/WMS-114 NOTES).
      • The glite-wms-create-proxy.sh uses an undefined GLOBUS_LOCATION env var which avoids the invocation of grid-proxy-init, which by default produces 1024bit proxies. The missing variable its solved by the WMS purger which then generates 512 bits proxies. (NOTES).
    • Issues introduced only in 3.6.2 (UMD not affected):
    • WMProxy still uses the low-level symlink call which doesn't support heading dash ("-") in the filenames (NOTES).
    • Bad exception handling in ICE prevents the user from getting a readable error message (NOTES).
    • Problem on glite-wms-wmproxy-api-java with TERENA certificate (NOTE)

1.3.2 CREAM_SLURM

  • Cream-slurm v. 1.0.1 as some problem with accounting that many records not being published even if jobs successfully finished. This is under investigation so if you are planning to deploy cream-slurm I would delay it until putting into production.

1.4 Next releases

2. Operational issues

2.1 Report from DMSU

Nothing to report

2.1 EMI-2 decommision calendar

According to the EGI decommissioning policy, the decommissioning deadline expires one month after the end of security updates and support of the software. For EMI 2 the end of security support is: 30-04-2014. And unsupported services must be either decommissioned, upgraded or in downtime after 31 May 2014.

A broadcast will be sent today to sites and NGIs.

Broadcast text:

Dear Resource Centre Administrators and VO Managers.

The EMI-2 software will reach end of security updates and support on 30-04-2014
(http://www.eu-emi.eu/releases#MajRel).

In compliance to the EGI Service Operations Security Policy (https://documents.egi.eu/document/669) [1], unsupported software SHOULD be decommissioned before its End of Security Updates and Support, and MUST be retired no later than 1 month after its End of Security Updates and Support. After this date, if a critical vulnerability were to emerge in the software, EGI CSIRT can request the service to be turned off immediately [2].

Because of this, as of March 03 2014, Resource Centre Administrators will start getting alerts about EMI 2 products deployed in their site. The list of the affected service end-points will be available on the Operations Dashboard of your site: https://operations-portal.egi.eu/dashboard.

Purpose of these alarms is to:
1- pro-actively alert administrators about the need to upgrade EMI-2 services before they reach end of security updates and support;
2- collect information about decommissioning/upgrade plans of the affected products.

IMPORTANT. According to the EGI decommissioning policy [2], the decommissioning deadline expires one month after the end of security updates and support of the software.
For EMI 2 products this is: 31-05-2014 [3].

EMI 2 software versions are in general detected through nagios tests, which query the information discovery system (BDII), on whose accuracy they depend on. 

Please get in touch with your NGI operations staff for more information, or open a GGUS ticket.

Best wishes
Peter Solagna - EGI Operations

[1] a Resource Centre Administrator ''SHOULD follow IT security best practices that include pro-actively applying software patches, updates or configuration changes related to security''.
[2] https://wiki.egi.eu/wiki/PROC16#Policy
[3] https://wiki.egi.eu/wiki/Software_Retirement_Calendar#Decommissioning_Calendar_EMI2

List of affected products

  • ARC v2.*
  • ARGUS v1.5.*
  • BDII Site older than v1.2.0
  • BDII Top older than v1.1.0
  • CREAM v1.14.*
  • dCache v2.2.*
  • DPM older than v1.8.6
  • EMI-UI v2.*
  • EMI-WN v2.*
  • FTS v.2.2.8
  • StoRM older than v.1.11.0
  • VOMS v.2.*

3. AOB

3.1 Next meeting

4. Minutes