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-15-05-2013"

From EGIWiki
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 89: Line 89:
== APEL / CREAM interoperability  ==
== APEL / CREAM interoperability  ==


*'''Additional Details:'''
* APEL
**Detailed release notes:  [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-3-30-04-2013-v-3-2-0-1#APEL_publisher_v_4_1_0_task_4087 APEL PUBLISHER 4.1.0]
** To use new APEL server sites should be aware that this version (4.1.0) of APEL Publisher is compatible only with APEL Parsers 2.1.0 and above. Sites installing EMI-3 APEL should follow the instructions in the APEL Client Upgrade Plan which can be found  [https://twiki.cern.ch/twiki/pub/EMI/EMI3APELClient/APEL_Client_Upgrade_Plan.pdf here]
*'''Installation Notes:''' No issues found during EGI's Software Provisioning but sites should be aware of the following:
*** This APEL version publish information to a different server, meaning sites needs to previously '''open a GGUS ticket to APEL''' in order to be allowed to publish to new server.
* To use new APEL server sites should be aware that this version (4.1.0) of APEL Publisher is compatible only with APEL Parsers 2.1.0 and above. Sites installing EMI-3 APEL should follow the instructions in the APEL Client Upgrade Plan which can be found  [https://twiki.cern.ch/twiki/pub/EMI/EMI3APELClient/APEL_Client_Upgrade_Plan.pdf here]
*** In production sites are not allowed to publish to both servers, nevertheless during test period you will allowed to publish to both.
** This APEL version publish information to a different server, meaning sites needs to previously open a GGUS ticket to APEL in order to be allowed to publish to new server.
*** ** IT is recomended to use CREAM 1.15.1 or higher (EMI-3).
** In production sites are not allowed to publish to both servers, nevertheless during test period you will allowed to publish to both.
 
*'''Known Issues:'''
*CREAM
** ** IT is recomended to use CREAM 1.15.1 or higher (EMI-3).
** By default this CREAM release installs the APEL 2.1.0 parsers.
*'''Version:'''4.1.0
**If making fresh install, and you do not want to move to the new APEL clients, please read how to set CREAM to use APEL from UMD-2 [https://wiki.egi.eu/wiki/UsingCreamUMD3WithApelUMD2 wiki]
** If migrating CREAM from UMD-2 to UMD/EMI-3, and without any other action APEL works if installed in the same machine.


=== UMD-2: General status of new updates ===
=== UMD-2: General status of new updates ===
Line 117: Line 118:
** [[UMD-2:UMD-2.3.0#emi.lb.sl5.x86_64]]
** [[UMD-2:UMD-2.3.0#emi.lb.sl5.x86_64]]
*LB developers released in the latest EMI-2 update a fix for this issue (the same as in the workaround), which is now in the UMD software provisioning queue to be released soon as an emergency update.
*LB developers released in the latest EMI-2 update a fix for this issue (the same as in the workaround), which is now in the UMD software provisioning queue to be released soon as an emergency update.
==== 2.4 EMI-3 APEL packages ====
The latest APEL release included in EMI-3 and currently under EGI's software provisioning process, its inclusion in UMD-3 requires special care since all the APEL components must be updated at the site level (parser and publishers) and a new central accounting database must be used. The central database is currently being tested with selected sites.
* '''Do not update''' to the latest APEL version until both the client update and the central database have been extensively tested.
** Do not update APEL components to EMI-3.
** It's advisable to wait for the deployment of CREAM from EMI-3 repositories, since the installation would deploy the latest APEL clients.
* The deployment of the EMI-3 APEL clients on an EMI-2 CREAM is not advisable.
** It could be possible with a workaround but it has not been extensively tested. Workaround: [https://ggus.eu/tech/ticket_show.php?ticket=92872 On GGUS], [http://www.eu-emi.eu/products/-/asset_publisher/1gkD/content/apel-parsers-2#INstConf On EMI release notes]
* A new version of APEL has been released in the latest EMI update. We would suggest to wait for the release in UMD-3 for the deployment of APEL+CREAM
** Central repository must be confirmed to be ready for production
** Known issues and installation notes will be released in the release notes of UMD 3.0.0


=== 3. AOB  ===
=== 3. AOB  ===
Line 136: Line 125:


=== 4. Minutes  ===
=== 4. Minutes  ===
[https://indico.egi.eu/indico/materialDisplay.py?materialId=minutes&confId=1720 Available on Indico]

Latest revision as of 13:28, 10 June 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 Staged Rollout

Status of the products verification/staged rollout

For UMD-3 a comprehensive view can be found in this RT dashboard. Please note that the page could take time to load.


UMD-3.0 released

Issues found during staged rollout

emi.lfc

  • Installation Notes: There are some dependency problems (already included in the release notes) GGUS
  • Version:1.8.6

emi.bdii-top

  • Known Issues:
    • Due to the caching mode, decommissioned services are published as 'Production' until the cache expires. Savannah BUG #99298
    • The glite-info-update-endpoints script does not fail when using the manual option and the input file does not exist. Savannah BUG #99322
  • Version: 1.1.0

emi.dpm

  • Installation Notes: There is a dependency issue with lcgdm-dav GGUS TICKET
    • Workaround: remove obsolete packages:
# yum remove emi-dpm_mysql gridsite-libs emi-version emi-dpm_disk gridsite

and install again DPM metapackage 

# yum install emi-dpm_mysql emi-dpm_disk
  • Known Issues: In some cases you may have conflicting UIDs/GIDs since uids and gids < 201 are reserved which was not mandatory in previous versions.
  • Version: 1.8.6

EMI.argus

  • Installation Notes:
    • Due to missing dependencies in the emi-argus metapackage it is needed to install fetch-crl package by hand prior to any other installation.Workaround
  • Known Issues:
    • Because SL6 uses the NSS library instead of OpenSSL, the proxy are not correctly handled this means Argus interoperabilty with WMS in SL6 is not working. GGUS TICKET
    • Argus DN with EMAILADDRESS will fail GGUS TICKET
  • Version: 1.6.0

EMI.emi-ui

  • Installation Notes:
    • When upgrading from EMI-2 version wn there is an issue with the upgrad of voms-clients package:
# yum remove voms-clients

# yum install emi-wn
  • Known Issues: No issues found during EGI's Software Provisioning.
  • Version:3.0.0


EMI.emi-wn

  • Installation Notes:
    • When upgrading from EMI-2 version wn there is an issue with the upgrad of voms-clients package:
# yum remove voms-clients

# yum install emi-wn

EMI.lb.sl5.x86_64

  • Installation Notes: Backward Incompatible: DB schema change. Configuration scripts update the DB automatically, manual update script provided.
  • Known Issues: Setup script may fail when unable to find messaging brokers through BDII (reporting:"glite-lb-setup: ERROR: msg, ABORT: glite-lb-setup failed!") GGUS
    • Solution: provided in the release notes
  • Version: 4.0.4

APEL / CREAM interoperability

  • APEL
    • To use new APEL server sites should be aware that this version (4.1.0) of APEL Publisher is compatible only with APEL Parsers 2.1.0 and above. Sites installing EMI-3 APEL should follow the instructions in the APEL Client Upgrade Plan which can be found here
      • This APEL version publish information to a different server, meaning sites needs to previously open a GGUS ticket to APEL in order to be allowed to publish to new server.
      • In production sites are not allowed to publish to both servers, nevertheless during test period you will allowed to publish to both.
      • ** IT is recomended to use CREAM 1.15.1 or higher (EMI-3).
  • CREAM
    • By default this CREAM release installs the APEL 2.1.0 parsers.
    • If making fresh install, and you do not want to move to the new APEL clients, please read how to set CREAM to use APEL from UMD-2 wiki
    • If migrating CREAM from UMD-2 to UMD/EMI-3, and without any other action APEL works if installed in the same machine.

UMD-2: General status of new updates

  • LB will be released asap to solve a problem with an log4c update released in EPEL.
  • The next release cycle of UMD-2 will start after the UMD-3 first release on May 14th.

2. Operational Issues

2.1 Updates from DMSU

no particular issue to report

2.3 UMD-2 LB issue with EPEL update

  • An update of the package log4c (from v1.2.1 to v1.2.3) in EPEL, which is not compatible, and breaks, with the LB version currently available in the UMD-2 repositories (LB v3.2.8).
    • This issue affects both SL5 and SL6 installations.
    • Upgrade of log4c lib is not recommended.
    • Ggus ticket reference
  • Developers provided a workaround which is now described in the LB known issues:
  • LB developers released in the latest EMI-2 update a fix for this issue (the same as in the workaround), which is now in the UMD software provisioning queue to be released soon as an emergency update.

3. AOB

3.2 Next meeting

Proposed date for the next meeting is May 27th 2013, 14:00 CEST

4. Minutes

Available on Indico

Retrieved from "https://wiki.egi.eu/w/index.php?title=Agenda-15-05-2013&oldid=56363"