/* * Copyrights : CNRS * Author : Oleg Lodygensky * Acknowledgment : XtremWeb-HEP is based on XtremWeb 1.8.0 by inria : http://www.xtremweb.net/ * Web : http://www.xtremweb-hep.org * * This file is part of XtremWeb-HEP. * * XtremWeb-HEP is free software: you can redistribute it and/or modify * it under the terms of the GNU General Public License as published by * the Free Software Foundation, either version 3 of the License, or * (at your option) any later version. * * XtremWeb-HEP is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with XtremWeb-HEP. If not, see . * */ ******************************************** * XWHEP-8.X * *------------------------------------------* * Release date : * * Author : Oleg Lodygensky * * lodygens@lal.in2p3.fr * * Trac : https://trac.lal.in2p3.fr/DGHEP * ******************************************** Developments are tracked on our trac server referred above. -A- Corrections -A.1- a bug corrected in Socket Time out management: reconnection must be automatic -A.2- the client now compressed any data, if necessary -A.3- worker must not use the "connected" mode introduced in 7.4.0 -A.4- worker and dispatcher must not use any device at all : setProperty("java.awt.headless", "true") (See http://java.sun.com/developer/technicalArticles/J2SE/Desktop/headless/) -A.5- a bug corrected on URI usage: ampersand are now accepted if written as "&" -A.6- on client side, bugs corrected on XML file usage (whith "--xwxml") -A.7- on client side, a bug corrected when retrieving user group -B- New features -B.1- worker definition has new attributes: * shared applications : comma separated list of application names shared as volunteer sharing * shared library : comma separated list of library names shared as volunteer sharing * shared data : comma separated list of data names shared as volunteer sharing * incomingconnections : volunteer resoure may accept incoming connection -B.2- usage of IBIS SmartSockets to interconnect jobs running on worker side (to each other and to/from client) -B.3- a new CommandLineOption : KEEPZIP (for debug purposes) -B.4- work definition has new attributes: * readydate : when the work has been downloaded by the worker * datareadydate : when all data of the work has been downloaded by the worker * compstartdate : when the worker has started the job * compenddate : when the worker has ended the job -B.5- tasks have their own UID now (it used to be their related work one) this aims to keep track of all event over the platform we can now retrieve all run informations (all start dates and host informations per task) -B.6- a work can be modified by its owner or the administrator this is needed by SpeQulOS (EDGI JRA2) -B.7- we can force the cache content path for any entry this is needed by Bitdew/XWHEP interconnection (still under development) -C- Known Bugs -C.1- Result download errors reported using 'xwdownload', but not with 'xwresult' We have not been able to reproduce them If you encounter these, please send us log file in DEBUG mode -C.2- xtremweb.gmond.pl does not scale -C.3- the scheduler is not fair -C.4- there may be some concurrent access problems leading to some errors There may be two concurrent accesses problems - on server side, DB access may lead to inconsistency between works and tasks tables This could certainly be solved using SQL transactions But we would then need MySQL >=5 There are sime issues withe transactions with hsqldb - on worker side, file access if a worker is configured to run jobs in parallel (default one thread per CPU core) We have observed that these concurrent access problems may lead to up to 6% erroneous jobs. Until further notification, we consider this rate acceptable. - Versionning - Versionning is as follow - X is a major part of the version - Y is a minor part of the version - Z is the micro part of the version (*) X reports a very important change : for example the communication protocol changes or a major new feature is modified/introduced/removed When X changes, backward compatibility is not ensured (*) Y reports a important but not critical change : backward compatibility is ensured (*) Z reports a minor change : bug correction, documentation changes etc.