Difference between revisions of "Agenda-24-09-2012"

Latest revision as of 17:55, 29 November 2012

EVO direct link	Pwd: gridops
EVO details	Indico page

1. Middleware releases and staged rollout

1.1. Update on the status of EMI updates

EMU Updates are expected for today, at latest tomorrow, no changes from what was listed in the previous Operations Meeting:

EMI 1
- RC gridftp server v.1.1.1
- ARC Infosys v.1.1.1
- ARC Clients v.1.1.1
- ARC Core v.1.1.1
- ARC CE v.1.1.1
- WMS v. 3.3.8

EMI 2
- CREAM v. 1.14.1
- dCache v. 2.2.4
- EMIR v.1.2.0
- UNICORE/X6 v. 5.0.0-2
- WNoDES v. 2.0.2

1.2. Staged Rollout

The IGTF trusted CA's have passed the verification process and are to be staged rollout today.

For UMD1 update, we have the following in staged rollout

IGE SAGA 1.6.1: EA has accepted the test.
IGE GridSafe: waiting integration into APEL accounting.
IGE GridSAM: No EA, continues on hold in staged rollout.

For UMD2 update now planed to be released on the 8 of October:

In UMDStore area (SW provisioning complete):
- CREAM SGE 2.0.0 module
- LB 3.2.6: though a new update (3.2.7) is in the verification process, that may deprecate the 3.2.6
In staged rollout:
- MPI 1.3.0: staged undergoing by EA team
- UNICORE UVOS 1.5.1
- BDII core 1.4.0: it was also released for emi1, if this passes the staged rollout the emi1 component will also be released in the next UMD1 update
- IGE components:
  - Globus Default security 5.2.1
  - Globus MyPROXY 5.6.3
  - Security integration 2.2.0
  - Gridway 5.10.2
The following products are still to be verified, but aimed at the next update:
- LB 3.2.7: notification sent to the verifiers to start it asap
- MyPROXY 1.0.1: verification finished, and staged rollout will follow today or tomorrow.
- All others will be prioritized in SA2, most corresponded to the lower priority products communicated by the SA1.

2. Operational Issues

2.1 Decommissioning of unsupported middleware

All gLite 3.1 components must be upgraded to an UMD release or decommissioned by the end of September. Sites still deploying gLite 3.1 components are eligible for suspension from the first of October.
- You can check the list of WMS's in production in WMS_Monitor
All gLite 3.2 unsupported components must be upgraded to an UMD release or decommissioned but the end of September. EGI management will receive a report containing the sites with unsupported middleware components still deployed, further actions will be defined, including possible suspension at the end of October.
EGI COD and EGI CSIRT will follow up with sites starting from October the first.

2.1.2 Currently supported components

The following components are not part of the decommissioning campaign, as they are still under security support, until November 30 2012:

DPM
LFC
gLite-WN
gLite-UI
gLExec

2.2 Security contact

Most of the sites in the EGI infrastructure have the security contacts correctly filled in the GOCDB.

Two sites without CSIRT email contact (notified via GGUS ticket)
Some sites without CSIRT telephone contact (office telephone)
- CSIRT officers may need to contact site security contacts by phone to have a prompt feedback on critical issues regarding the site (during office hours). The office telephone contact has not been enforced as mandatory - so far - but sites are warmly recommended to fill this field in GOCDB.

Missing CSIRT telephone number in GOCDB:

AsiaPacific T2-TH-CUNSTDA, NZ-UOA, HK-HKU-CC-01
NGI_BG BG06-GPHI
NGI_CH UNIGE-DPNC
NGI_DE wuppertalprod
NGI_FRANCE AUVERGRID, IN2P3-LPSC, IN2P3-IPNL
NGI_IBERGRID CIEMAT-TIC, CIEMAT-LCG2, IFCA-LCG2
NGI_IL NGI_IL, IL_IUCC_IG, NGI_IL_MED1
NGI_IT INFN-ROMA2, GARR-01-DIR
NGI_MK MK-03-FINKI
NGI_UK UKI-LT2-UCL-HEP
ROC_IGALC GRID-CEDIA

2.3 User DN publication

Sites should publish UserDN information in their accounting data.

Instructions about how to properly configure the APEL clients are available here: Agenda-01-06-2012
If sites need to re-publish the accounting data with userDN, they must open a GGUS ticket vs the APEL support unit and wait the green light from the APEL team.

Some sites are still publishing 'unknown' DN, I will attach the updated list of sites currently not publishing with the minutes.

3. AOB

3.1 Next meeting

@@ Line 1: / Line 1: @@
+[[Category:Grid Operations Meetings]]
+__NOTOC__
 {|
 |-
-| [http://evo.caltech.edu/evoNext/koala.jnlp?meeting=M9MIMi292lDuDu9M9iDD99 EVO direct link]
+| [http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MeMMMu2e29D9DB9v9BDv9e EVO direct link]
 | Pwd: '''gridops'''<br>
 |-
-| [https://indico.egi.eu/indico/materialDisplay.py?materialId=1&confId=1158 EVO details]
+| [https://indico.egi.eu/indico/materialDisplay.py?materialId=1&confId=1167 EVO details]
-| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1158 Indico page]
+| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1167 Indico page]
 |}
 === 1. Middleware releases and staged rollout===
 ====1.1. Update on the status of EMI updates ====
-Update from EMI: [https://twiki.cern.ch/twiki/bin/view/EMI/EmiEgiGOM#Status_10_09_2012 EMI twiki link]
-Provided by Cristina Aiftimiei.
+EMU Updates are expected for today, at latest tomorrow, no changes from what was listed in the previous Operations Meeting:
+*EMI 1
+** RC gridftp server v.1.1.1
+** ARC Infosys v.1.1.1
+** ARC Clients v.1.1.1
+** ARC Core v.1.1.1
+** ARC CE v.1.1.1
+** WMS v. 3.3.8
+*EMI 2
+** CREAM v. 1.14.1
+** dCache v. 2.2.4
+** EMIR v.1.2.0
+** UNICORE/X6 v. 5.0.0-2
+** WNoDES v. 2.0.2
 ==== 1.2. Staged Rollout  ====
-UMD-2.2.0: tentative release date for 8 October 2012.
+The IGTF trusted CA's have passed the verification process and are to be staged rollout today.
-Some products ready in the UMDStore area, all SW provisioning done with success:
+For UMD1 update, we have the following in staged rollout
-*CREAM-SGE 2.0.0
+*IGE SAGA 1.6.1: EA has accepted the test.
-*LB 3.2.6: but a new version is in the loop now 3.2.7, so that 3.2.6 maybe set to unpublished
+*IGE GridSafe: waiting integration into APEL accounting.
+*IGE GridSAM: No EA, continues on hold in staged rollout.
-Products in staged rollout:
+For UMD2 update now planed to be released on the 8 of October:
-*From EMI2:
+*In UMDStore area (SW provisioning complete):
-**MPI 1.3.0
+**CREAM SGE 2.0.0 module
+**LB 3.2.6: though a new update (3.2.7) is in the verification process, that may deprecate the 3.2.6
+*In staged rollout:
+**MPI 1.3.0: staged undergoing by EA team
 **UNICORE UVOS 1.5.1
-*From IGE:
+**BDII core 1.4.0: it was also released for emi1, if this passes the staged rollout the emi1 component will also be released in the next UMD1 update
-**Globus Default Security 5.2.1
+**IGE components:
-**Globus Security Integration 2.2.0
+***Globus Default security 5.2.1
-**Globus MyPROXY 5.6.3
+***Globus MyPROXY 5.6.3
-**Gridway 5.10.2
+***Security integration 2.2.0
+***Gridway 5.10.2
+*The following products are still to be verified, but aimed at the next update:
+**LB 3.2.7: notification sent to the verifiers to start it asap
+**MyPROXY 1.0.1: verification finished, and staged rollout will follow today or tomorrow.
+**All others will be prioritized in SA2, most corresponded to the lower priority products communicated by the SA1.
+===2. Operational Issues ===
+==== 2.1 Decommissioning of unsupported middleware  ====
-Products in verification:
+*All gLite 3.1 components must be upgraded to an UMD release or decommissioned by the end of September. Sites still deploying gLite 3.1 components are eligible for suspension from the '''first of October'''.
+**You can check the list of WMS's in production in [[WMS_Monitor]]
+*All gLite 3.2 unsupported components must be upgraded to an UMD release or decommissioned but the end of September. EGI management will receive a report containing the sites with unsupported middleware components still deployed, further actions will be defined, including possible suspension at the '''end of October'''.
+* EGI COD and EGI CSIRT will follow up with sites starting from October the first.
+===== 2.1.2 Currently supported components  =====
-*UNICORE HILA 2.3.0
+The following components are not part of the decommissioning campaign, as they are still under security support, until '''November 30 2012''':
-*All ARC 2.0.0 products: we are waiting for the next release in order to fix some bugs, this version should be set to unpublished.
-UMD-1.9.0: does not have a release date yet, but there are some products from IGE in staged rollout now:
+*DPM
+*LFC
+*gLite-WN
+*gLite-UI
+*gLExec
-*IGE-SAGA 1.6.1
+==== 2.2 Security contact ====
-*IGE-GridSafe 1.0.1
-*IGE-GridSAM 2.3.1: No EA for this one
-===2. Operational Issues ===
+Most of the sites in the EGI infrastructure have the security contacts correctly filled in the GOCDB.
-==== 2.1 Bug in CREAM resource information provider ====
+* Two sites without CSIRT email contact (notified via GGUS ticket)
+* Some sites without CSIRT telephone contact (office telephone)
+** CSIRT officers may need to contact site security contacts by phone to have a prompt feedback on critical issues regarding the site (during office hours). The office telephone contact has not been enforced as mandatory - so far - but sites are warmly recommended to fill this field in GOCDB.
-The current UMD2 version of CREAM has a bug in the resource information provider: [https://ggus.eu/tech/ticket_show.php?ticket=84509 GGUS ticket].<br>
+Missing CSIRT telephone number in GOCDB:
-The problem is that the '''RunTimeEnvironment''' tags are converted to lowercase in the information system. GLUE1.3 specification is not case sensitive (while GLUE 2 is), but applications that use the RunTimeEnvironment tags for resource matchmaking may have case sensitive algorithms.
+* AsiaPacific	T2-TH-CUNSTDA, NZ-UOA, HK-HKU-CC-01
-* The issue is already in the UMD2.1 release notes
+* NGI_BG	BG06-GPHI
-* EMI rolled back to the previous version of the script, re-versioning it as "lcg-info-dynamic-software-1.0.7-2.emi". This version is available in the EMI repositories.
+* NGI_CH	UNIGE-DPNC
-** This fix is '''only for GLUE1.3''' not GLUE2.0
+* NGI_DE	wuppertalprod
-* The fix will be pushed into UMD as soon as possible
+* NGI_FRANCE	AUVERGRID, IN2P3-LPSC, IN2P3-IPNL
+* NGI_IBERGRID	CIEMAT-TIC, CIEMAT-LCG2, IFCA-LCG2
+* NGI_IL	NGI_IL, IL_IUCC_IG, NGI_IL_MED1
+* NGI_IT	INFN-ROMA2, GARR-01-DIR
+* NGI_MK        MK-03-FINKI
+* NGI_UK	UKI-LT2-UCL-HEP
+* ROC_IGALC	GRID-CEDIA
-==== 2.2 Relevant sessions at the EGI Technical Forum ====
+==== 2.3 User DN publication ====
-* '''Tuesday 18th September'''
+Sites should publish UserDN information in their accounting data.
-**Double session of presentations about new products and new features from the EGI's technology providers latest releases
+* Instructions about how to properly configure the APEL clients are available here: [[Agenda-01-06-2012#2.1_Sites_not_publishing_user_DN_in_the_usage_record| Agenda-01-06-2012]]
-*** Featured topics: DPM, dCache, STS, EMIR, storage federations, messaging services, CREAM HA
+* If sites need to re-publish the accounting data with userDN, they must open a GGUS ticket vs the APEL support unit and wait the green light from the APEL team.
-**WNoDeS demonstration and tutorial
-* '''Wednesday 19th September'''
-**EMI 2 tutorial for system administrators, extensive tutorial session featuring: '''YAIM, CREAM, DPM, BDII and WMS'''
-* '''Thursday 20th September'''
-**session on Job management services and batch systems
-*** Featured topics: SLURM, GridWay and more
-** EMI training for the management of security tools
-*** Featured topics: STS, CANL, Hydra, Argus and gLExec
-There are more relevant sessions for the operations, i.e.: OMB workshops, OTAG and the GGUS advisory board. A detailed mail with the relevant sessions of the technical forum will be circulated later today.
+Some sites are still publishing 'unknown' DN, I will attach the updated list of sites currently not publishing with the minutes.
 ===3. AOB ===
 ====3.1 Next meeting====
-=== 4  Minutes ===
-[https://indico.egi.eu/indico/materialDisplay.py?materialId=minutes&confId=1158 The minutes of the meeting are on indico]
-[[Category:GridOpsMeeting]]