 |
 |
Hi, There is some info here concerning what will be the upcoming 2.6.0 release. This is not a general release as yet though. Steve ----- Forwarded message from Markus Schulz <[log in to unmask]> ----- From: Markus Schulz <[log in to unmask]> Subject: pre-release notes draft Date: Fri, 15 Jul 2005 18:57:40 +0200 To: "project-egee-roc-managers ((EGEE ROC managers and alternates))" <[log in to unmask]> Cc: Maarten Litmaath <[log in to unmask]>, Louis Poncet <[log in to unmask]>, Oliver KEEBLE <[log in to unmask]>, Laurence Field <[log in to unmask]>, Ognjen Prnjat <[log in to unmask]> Dear ROC managers, this is the release note for the pre-release of LCG-2_6_0 The purpose of the pre-release is to allow the three ROCs, Italy, UK/ IE, and SE to do a deployment test and give feedback before the release is made public. We expect to receive feedback during next week. Since serious problems might be found it is not advisable to use the pre-release as the basis for regional customization, please wait the extra week. The pre-release has already the same version number as the final release, we will just re-tag the public release. The pre-release doesn't come with the completely updated documentation. Instead we will provide comments on the configuration changes compared to the LCG-2_4_0 release in the site-info.def file at the end of this mail Contacts: ======= Problems with the pre-release should NOT be sent to public lists to avoid a wrong perception of the deployability of the release. Please sent problems to the following people: -------------------------------------------------------------- [log in to unmask] [log in to unmask] [log in to unmask] [log in to unmask] [log in to unmask] Upgrades paths that are supported ------------------------------------------------ 2_4_0 -> 2_6_0 and installation from scratch. Since 2_5_0 is very close to 2_4_0 we are quite confident that this works too. If your site is on 2_5_0 you still have to upgrade because 2_6_0 contains major changes. Read this if you opt to ignore all documentation: ====================================== The glue schema has changed to GLUE-1.2. If you upgrade any node that provides information for the information system (BDII) make sure that you FIRST upgrade the elements higher in the hierarchy. First the BDII, then the Site BDII and at the end the GRIS on the nodes. The schema is backward compatible, but a pre 1.2 element will ignore entries that use the new schema. Do not configure the FTS clients on your T1 or T2 center unless you are participating in the SC3 activity and you know who your T0/T1 center is! If in doubt, have a look at the SC3 page. FTS services are configured with direct help by the SC3 team at CERN. DO NOT INSTALL A FTS SERVER UNLESS YOU ARE A T1 IN SC3 Make sure you understand how to configure the LFC as a local catalogue or as a replica catalogue and that you know what you want to setup. Only install one of the new VO-boxes after you have clarified with the VO that you want to support on it that they will use this as a pilot service. Documentation on how to use this node will be provided shortly via the GOC-wiki pages. Where can I find the link to the new release? ----------------------------------------------------------------- here: http://grid-deployment.web.cern.ch/grid-deployment/gis/yaim- devel/lcg-yaim-2.6.0-0.noarch.rpm Now some more details ================== GLUE 1.2 -------------- The new version of the Glue Schema is backwards compatible although the top level BDIIs need to be upgraded first. If a site update to the new information providers before the top level BDII has been upgrade the site will be rejected by the BDII. This affects ALL nodes that provide data for the information system. In addition several of the client tools to access the information system have been adapted, like the popular lcg-infosites. Details on the new schema can be seen here: http:// infnforge.cnaf.infn.it/glueinfomodel LFC 1.3.5 ------------- The LFC has now two different usages. As a central replica catalogue and as a local file catalogue. Make sure you don't get confused when setting up a node. Depending if you install a local or a central LFC, the information to publish in the Information System It nows supports sessions, and a Python interface is provided as a separate RPM. In addition the DLI interface is supported. The LFC Administrator's Guide is available at : http://goc.grid.sinica.edu.tw/gocwiki/How_to_set_up_an_LFC_service The archived LFC support mailing list to contact is : [log in to unmask] The release includes YAIM install-scripts for use with MySQL backends. For the ORACLE backend, refer to the LFC Administrator's Guide. For both backends, meta-rpms are provided. The LFC service is relevant for all those sites that either host and LFC for VOs, or provide the service of a local LFC catalogue. DPM 1.3.5 ---------------- The DPM Administrator's Guide is available at : http://goc.grid.sinica.edu.tw/gocwiki/ How_to_install_the_Disk_Pool_Manager_%28DPM%29 The archived DPM support mailing list to contact is : [log in to unmask] The DPM includes secure rfio, and a DPM-enabled standard GridFTP server. For SEs based on DPM, YAIM installation and configuration scripts are provided for the MySQL based version. For the ORACLE backend version, refer to the DPM Administrator's Guide. For both backends, meta-rpms are provided. The minimal configuration, where the disk server and the DPM servers are located on the same machine, is supported by YAIM. Bugs fixed : #9293, #9393, #9510 VO-BOX 1.0.0 ---------------------- This is a pilot version of the node type that allows VOs to run their own user level agents. VO's software managers can use their certificates to get interactive access to these nodes and install the agents. Mechanisms for proxy renewal are provided. This uses gsi- ssh. We don't suggest that sites set these nodes up immediately unless a VO approaches them directly. Documentation on the usage will be provided at the beginning of the week on the GOC-wiki page. FTS ------ The clients are part of the UIs and WNs and supported by YAIM scripts. The server installation is described on the service challenge WIKI page: https://uimon.cern.ch/twiki/bin/view/LCG/LCGServiceChallenges See the section "Read this if you opt to ignore all documentation:" for details on who should install/configure this. New and updated software ====================== Data Management Client: ------------------------------------- There are now LCG data management libs with timeouts. These should make it easier to handle the all to frequent problems with hanging calls. Lcg_util and GFAL have been modifed to acdept a timeout parameter (-t SECS). This is used to timeout both gridftp transfers and interactions with the SRM. CTRL-C is now caught during gridftp transfers too, and the transfer is cleaned up properly. This requires an update of the WNs and UIs. VDT 1.2.2: -------------- Updated Workload Management 1.6.8: ------------------------------------------ Updated Information System: ---------------------------- BDII now supports the new GLUE 1.2 schema and nolonger uses iptables. The information providers also publish GLUE 1.2 information. The RB now has a dynamic plug-in that gets information about the load. dCache: ----------- The configuration contains several fixes and enhancements provided by GridPP R-GMA ------------ The new glite1.2 version of R-GMA. This is setup in a compatibility mode offering secure and in-secure services. Monitoring ---------------- Significant new or improved components are now available. There is a sensor for gridFTP logfiles that allows to monitor the transfers from a globus gridFTP server There is a new sensor for the job state found in the lb server on the RB. There is a new sensor that monitors the resource usage of running jobs. All of the above are based on R-GMA. In addition monitoring for stdout and error while jobs are running is now available. Documentation on the usage will be provided shortly on the GOC-Wiki Accounting ------------------- Updated to work with the glite version of R-GMA and now supports LSF VOMS ---------- new version YAIM --------- Bug fixes, new services and adaptation to the new glue schema. The install and configure node types have been unified. The list of node types can be found in the file: /opt/lcg/yaim/scripts/node-info.def To extract the list do: cat /opt/lcg/yaim/scripts/node-info.def | grep FUNC | sed "s/ _FUNC.*//g" Other: ======== The SFTs have been packaged and are now available on the UI and WN. gsi version of ssh is included on the UIs. YAIM site-info.def changes ======================== DPMUSER_PWD password of the database user for DPM. DPMMGR username of the database user for DPM. Can be chosen by the site FTS_SERVER_URL Set by those involved in the Service Challenge 3. LEAVE THIS EMPTY IF YOU ARE NOT IN SC3!!!! LFC_DB_PASSWORD password of the database user for LFC. VOBOX_HOST, host for the new VO box. VOBOX_PORT, port used by the VO box. GSSKLOG set to yes if your site provides an X509 to KERBEROS Authentication Server (AFS used kerberos) GSSKLOG_SERVER Name of the local Authentication Server LFC_TYPE local or central TORQUE_SERVER host running the torque server. APEL_DB_PASSWORD password of the database user for apel. SITE_LOC the location of the site, (Nearest town/city). SITE_LAT latitude of the site. SITE_LONG longitude of the site. SITE_WEB web url for the site. SITE_TIER the site tier, (Tier0, Tier1 or Tier2) SITE_SUPPORT_SITE the site name of your Tier1 site. Tier1 sites should put CERN-CIC. EDG_WL_SCRATCH scratch directory for jobs. VO_<VONAME>_VOMS_SERVERS VOMS server for the VO. VO_<VONAME>_VOMS_POOL_PATH path on VOMS server for pool accounts. VO_<VONAME>_VOMS_EXTRA_MAPS for accounts other than sgm or pool. Notice also that the following variables are not needed any more: DPMCONFIG DPMDB_PWD DPMLOGS DPM_POOLS CA_WGET SITE_VERSION Here is the full list of new and updated rpms. ---------------------------------------------- VDT vdt_globus_data_server-VDT1.2.2rh9-1.i386.rpm vdt_globus_essentials-VDT1.2.2rh9-1.i386.rpm vdt_globus_info_client-VDT1.2.2rh9-1.i386.rpm vdt_globus_info_essentials-VDT1.2.2rh9-1.i386.rpm vdt_globus_info_server-VDT1.2.2rh9-1.i386.rpm vdt_globus_jobmanager_condor-VDT1.2.2rh9-1.i386.rpm vdt_globus_jobmanager_lsf-VDT1.2.2rh9-1.i386.rpm vdt_globus_jobmanager_pbs-VDT1.2.2rh9-1.i386.rpm vdt_globus_rm_client-VDT1.2.2rh9-1.i386.rpm vdt_globus_rm_essentials-VDT1.2.2rh9-1.i386.rpm vdt_globus_rm_server-VDT1.2.2rh9-1.i386.rpm vdt_globus_sdk-VDT1.2.2rh9-1.i386.rpm Work Load Management edg-wl-chkpt-api_gcc3_2_2-lcg2.1.68-1 edg-wl-common-api-java-interface_gcc3_2_2-lcg2.1.68-1 edg-wl-common-api-java_gcc3_2_2-lcg2.1.68-1 edg-wl-common-api_gcc3_2_2-lcg2.1.68-1 edg-wl-config_gcc3_2_2-lcg2.1.68-1 edg-wl-interactive_gcc3_2_2-lcg2.1.68-1 edg-wl-lbserver_gcc3_2_2-lcg2.1.68-1 edg-wl-locallogger_gcc3_2_2-lcg2.1.68-1 edg-wl-logging-api-c_gcc3_2_2-lcg2.1.68-1 edg-wl-logging-api-cpp_gcc3_2_2-lcg2.1.68-1 edg-wl-logging-api-sh_gcc3_2_2-lcg2.1.68-1 edg-wl-proxyrenewal_gcc3_2_2-lcg2.1.68-1 edg-wl-services-common_gcc3_2_2-lcg2.1.68-1 edg-wl-ui-api-cpp_gcc3_2_2-lcg2.1.68-1 edg-wl-ui-api-java-interface_gcc3_2_2-lcg2.1.68-1 edg-wl-ui-api-java_gcc3_2_2-lcg2.1.68-1 edg-wl-ui-cli_gcc3_2_2-lcg2.1.68-1 edg-wl-ui-config_gcc3_2_2-lcg2.1.68-1 edg-wl-ui-gui_gcc3_2_2-lcg2.1.68-1 edg-wl-wm_gcc3_2_2-lcg2.1.68-1 Information System bdii-3.3.7-1.noarch.rpm glue-schema-1.2.2-1.noarch.rpm lcg-schema-1.2.0-1.noarch.rpm lcg-info-generic-1.0.20-1.noarch.rpm lcg-info-templates-1.0.8-1.noarch.rpm lcg-info-dynamic-rb-1.0.1-1.noarch.rpm lcg-info-dynamic-classicSE-1.0.4-1.noarch.rpm lcg-info-dynamic-lsf-1.0.6-1.noarch.rpm lcg-info-dynamic-pbs-1.0.7-1.noarch.rpm lcg-info-api-ldap-2.4-7.i386.rpm FTS glite-data-catalog-cli-1.5.3-1.i386.rpm glite-data-catalog-fireman-api-c-2.0.0-2.i386.rpm glite-data-catalog-interface-2.0.0-6.noarch.rpm glite-data-catalog-storageindex-api-c-2.0.0-1.i386.rpm glite-data-transfer-api-c-2.9.0-1.i386.rpm glite-data-transfer-cli-1.3.4-1.i386.rpm glite-data-transfer-interface-2.9.0-1.noarch.rpm glite-security-voms-1.2.32-1.i386.rpm LFC LFC-client-1.3.5-1sec_sl3.i386.rpm LFC-python-interface-1.3.5-1_sl3.i386.rpm LFC-server-mysql-1.3.5-1sec_sl3.i386.rpm LFC-server-oracle-1.3.5-1sec_sl3.i386.rpm DPM DPM-client-1.3.5-1sec_sl3.i386.rpm DPM-name-server-mysql-1.3.5-1sec_sl3.i386.rpm DPM-rfio-server-1.3.5-1sec_sl3.i386.rpm DPM-server-mysql-1.3.5-1sec_sl3.i386.rpm DPM-srm-server-mysql-1.3.5-1sec_sl3.i386.rpm DPM-gridftp-server-1.3.5-1sec_sl3.i386.rpm lcg-dm-common-1.3.5-1_sl3.i386.rpm dCache d-cache-client-1.0-99.i386.rpm d-cache-core-1.5.2-82.i386.rpm d-cache-opt-1.5.3-83.i386.rpm Monitoring glite-rgma-flexible-archiver-4.1.16-2.noarch.rpm glite-rgma-standard-tables-4.1.8-1.noarch.rpm glite-rgma-api-c-4.1.11-1.i386.rpm glite-rgma-gin-4.1.16-1.noarch.rpm glite-rgma-stubs-servlet-java-4.1.12-1.noarch.rpm glite-rgma-api-cpp-4.1.14-1.i386.rpm glite-rgma-log4cpp-4.1.4-0.i386.rpm glite-rgma-system-tests-4.1.7-1.i386.rpm glite-rgma-api-java-4.1.5-1.noarch.rpm glite-rgma-log4j-4.1.5-1.noarch.rpm glite-rgma-api-python-4.1.13-1.i386.rpm glite-rgma-publish-site-4.1.14-1.noarch.rpm glite-rgma-base-4.1.19-1.noarch.rpm glite-rgma-server-servlet-4.1.21-1.noarch.rpm glite-rgma-command-line-4.1.13-1.noarch.rpm glite-rgma-servicetool-4.1.19-3.noarch.rpm glite-security-trustmanager-1.7.3-1.noarch.rpm glite-security-util-java-1.1.2-2.noarch.rpm lcg-mon-gridftp-1.0.14-1.noarch.rpm lcg-mon-job-status-1.0.15-1.noarch.rpm lcg-mon-wn-1.0.8-1.noarch.rpm lcg-archiver-1.0.13-1.noarch.rpm lcg-mon-tools-1.0.2-1.noarch.rpm lcg-mon-stdout-1.0.1-1.noarch.rpm Accounting gLite-apel-pbs-1.0.0.0.rpm gLite-apel-lsf-1.0.0.0.rpm gLite-apel-publisher-1.0.0.0.rpm gLite-apel-core-1.0.0.0.rpm VOMS voms-api_gcc3_2_2-1.5.4-1_sl3 voms-api-gcc32dbgpthr-_gcc3_2_2-1.5.4-1_sl3 voms-client_gcc3_2_2-1.5.4-1_sl3 lcg-voms-alice-3.0.0-1 lcg-voms-atlas-3.0.0-1 lcg-voms-cms-3.0.0-1 lcg-voms-dteam-3.0.0-1 lcg-voms-lhcb-3.0.0-1 lcg-voms-sixt-3.0.0-1 lcg-voms-na48-1.0.0-1 lcg-vomscert-alice-3.0.0-1 lcg-vomscert-atlas-3.0.0-1 lcg-vomscert-cms-3.0.0-1 lcg-vomscert-dteam-3.0.0-1 lcg-vomscert-lhcb-3.0.0-1 lcg-vomscert-sixt-3.0.0-1 lcg-vomscert-na48-1.0.0-1 Other lcg-sft-2.0.1-1.noarch.rpm lcg-vobox-1.0.0-2.noarch.rpm edg-mkgridmap-2.5.0-1_sl3 edg-mkgridmap-conf-2.5.0-1_sl3 GFAL-client-1.7.0-1_sl3.i386.rpm lcg_util-1.3.0-1_sl3.i386.rpm lcg-ManageSoftware-2.0-2.noarch.rpm lcg-info-1.5-1.noarch.rpm CGSI_gSOAP_2.3-1.1.9-1.slc3.i386.rpm CGSI_gSOAP_2.6-1.1.9-1.slc3.i386.rpm CGSI_gSOAP_2.6-dev-1.1.9-1.slc3.i386.rpm lcg-lcas-lcmaps-1.1.1-1 edg-gridftpd-1.1.0-1_sl3 globus-config-0.23-1.lcg gsiopenssh-VDT1.2.2rh9-1 > ----- End forwarded message ----- -- Steve Traylen [log in to unmask] http://www.gridpp.ac.uk/