/* * 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-7.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- windows XP and 7 supported -A.2- server : access logs are now stored in HomeDir as found in config file and not in /tmp -A.3- server : a bug corrected in group management -A.4- server : DB access improved -A.5- remove leading and trailing spaces from job command line -A.6- the communication protocol has been improved so that the server always sends an answer, especially on error. The client now displays errors received from the server, if any. The client also sets its return code accordingly. -A.7- the worker-server communication protocol has been corrected so that the worker keeps a chance to upload results, even on server FS error. This feature exists for long (since INRIA XtremWeb 1.6) but was buggy. -A.8- client GUI improved -A.9- a security hole corrected on object removal -A.10- on Mac OS X, the server is now correctly installed and works well We don't use Mac OS X specific stuffs, like StartupItems or LaucnhDaemons, because it does not work Instead, we use linux like scripts : xtremweb.server [start | stop | restart | status] There are two drawbacks : the server does not automatically starts at boot time and the server runs as root under Mac OS X. -A.11- Attic removed until further notification : Attic may crash the worker under certain circumstances -B- New features -B.1- client can connect using its certificate and associated private key. The client-server connection is challenged using this key pair. The client certificate must be certified by a CA cert path known by the server. -B.2- client accepts a new --xwout command line option to set the output file name (used with xwresults and xwdownload) -B.3- client can now retrieve applications by their name and users by their login -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.