Difference between revisions of "Agenda-24-04-2013"
Jump to navigation
Jump to search
(6 intermediate revisions by the same user not shown) | |||
Line 4: | Line 4: | ||
| ''Conference system is Adobe Connect, no password required.'' | | ''Conference system is Adobe Connect, no password required.'' | ||
|- | |- | ||
| Audio conference details] | | [https://indico.egi.eu/indico/materialDisplay.py?materialId=0&confId=1382 Audio conference details] | ||
| [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1542 Indico page] | | [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1542 Indico page] | ||
|} | |} | ||
{{TOC right}} | {{TOC right}} | ||
=== 1. Middleware releases and staged rollout === | |||
= 1. | ==== 1.1. Update on the status of EMI updates ==== | ||
==== 1.2. Staged Rollout ==== | |||
'' | |||
* UMD-2 released: | |||
** Ready for production | |||
*** EMI: Cream 1.14.3 ; Wms 3.4.1. | |||
** IGE : Gsisshterm - 1.3.4; Gram5 - 5.2.3; | |||
* EMI WN tarball: | |||
** SL5 already in production: [http://repository.egi.eu/mirrors/EMI/tarball/production/sl5/emi2-emi-wn/ REPO] | |||
** SL6 need people to test if interested contact me or Matt Doidge; | |||
* EMI UI tarball: | |||
** Like for SL6 WN need people to test it. | |||
* UMD-3 released: | |||
** Products ready to be released: WMS, UI, WN, L&B, DPM, ARGUS, BDII's ... | |||
** CREAM under verification | |||
** STORM and VOMS have failed during Software Provisioning so we do not recommend sites to install them: | |||
*** STORM: Consecutive lcg-gt calls fail with a "Requested file is busy" error [https://ggus.eu/ws/ticket_info.php?ticket=92819 GGUS]; | |||
*** VOMS Admin service incorrectly parses truststore refresh period from configuration. VOMS: [https://issues.infn.it:8443/browse/VOMS-230 VOMS-230] | |||
*** Standalone VOMS Admin service deployment is not suitable for deployments with large number [https://issues.infn.it:8443/browse/VOMS-231 VOMS-231] | |||
* Under preparation a wiki with the issues found during Software Provisioning regarding the upgrades from EMI-2 to EMI-3 | |||
=== 2. Operational Issues === | |||
==== 2.2 Updates from DMSU ==== | |||
no particular issue to report | |||
==== 2.3 Top-BDII change in resource requirements ==== | |||
As a follow up of the performance issues reported in this [https://ggus.eu/tech/ticket_show.php?ticket=92745 ggus ticket], the Top-BDII product team updated the hardware requirements of the product. The wide deployment of GLUE2 increased the amount of data handled by the Top-BDIIs and triggered this new set of requirements. The new hardware requirements are available in the [https://tomtools.cern.ch/confluence/download/attachments/983044/EMI_BDII_sysadmin.pdf Top-BDII admin guide]: | |||
* Min dual core CPU (4 cores advised) | |||
* Min 4GB ram (6GB advised) | |||
* 10 GB disk space | |||
=== 3. AOB === | |||
==== 3.2 Next meeting ==== | |||
Proposed date for the next meeting is '''May 6th 2013, 14:00 CEST''' | |||
=== 4. Minutes === | |||
[https://indico.egi.eu/indico/materialDisplay.py?materialId=minutes&confId=1542 Minutes] |
Latest revision as of 17:11, 3 May 2013
Audio conference link | Conference system is Adobe Connect, no password required. |
Audio conference details | Indico page |
1. Middleware releases and staged rollout
1.1. Update on the status of EMI updates
1.2. Staged Rollout
- UMD-2 released:
- Ready for production
- EMI: Cream 1.14.3 ; Wms 3.4.1.
- IGE : Gsisshterm - 1.3.4; Gram5 - 5.2.3;
- Ready for production
- EMI WN tarball:
- SL5 already in production: REPO
- SL6 need people to test if interested contact me or Matt Doidge;
- EMI UI tarball:
- Like for SL6 WN need people to test it.
- UMD-3 released:
- Products ready to be released: WMS, UI, WN, L&B, DPM, ARGUS, BDII's ...
- CREAM under verification
- STORM and VOMS have failed during Software Provisioning so we do not recommend sites to install them:
- Under preparation a wiki with the issues found during Software Provisioning regarding the upgrades from EMI-2 to EMI-3
2. Operational Issues
2.2 Updates from DMSU
no particular issue to report
2.3 Top-BDII change in resource requirements
As a follow up of the performance issues reported in this ggus ticket, the Top-BDII product team updated the hardware requirements of the product. The wide deployment of GLUE2 increased the amount of data handled by the Top-BDIIs and triggered this new set of requirements. The new hardware requirements are available in the Top-BDII admin guide:
- Min dual core CPU (4 cores advised)
- Min 4GB ram (6GB advised)
- 10 GB disk space
3. AOB
3.2 Next meeting
Proposed date for the next meeting is May 6th 2013, 14:00 CEST