Release Notes for Quattor Configuration of LCG 2.7.0

The most up to date documentation about QWG templates for LCG2 are now availableonline at url :

	https://trac.lal.in2p3.fr/LCGQWG


Major Changes
-------------

* The LCG configuration file has been completely revamped.  It now
uses systematically the "?=" operator so that the standard site
configuration file can be included directly.  The standard "defaults"
file defines values for those variables with usable defaults.  For 
those which do not have usable defaults, the value is defined to be
"undef".  Create a "pro_lcg2_config_site" file which contains the
values you want to use and then include the "pro_lcg_config_site_defaults"
template at the end.  It is recommended that you use the "?=" 
for your definitions in your site configuration file. 

* The VO-specific configuration has also changed radically.  The 
old configuration (where the VO account configurations are 
included manually in a template) still works.  These files can
be found in the "vo" subdirectory.  

The new configuration creates a global variable (VO_INFO) with 
all of the VO-specific configuration.  There are a set of 
functions which copy this information into the configuration tree 
as needed, based on the values in the VOS list.  These files can
be found in the "vo" subdirectory.  The examples use this type
of configuration.

* The names of accounts in the new release have changed.  By 
default the first three letters of the VO name are used for 
account prefixes.  The software manager has an 's' suffix; the
production manager, a 'p' suffix.  E.g. alice has pool accounts
ali000, ali001, etc.; "alis" and "alip" for the managers.  For
each VO, 200 pool accounts are created. 

* The account/group numbers have changed.  See the files in the
"vo" area for the new numbers.  The account configuration also
avoids conflicts with accounts created with the "adduser" 
command. 

* The GIP configuration has changed radically with the latest 
release; consequently, the GIP component has also changed.  It is
not backward compatible with previous versions of the component. 
You should use the older version of the GIP component for releases
prior to LCG 2.7.0.

Changes from Standard LCG 2.7.0 Release
---------------------------------------

* The versions of torque and maui have been made configurable.
I recommend using Torque 2.0 and the latest maui rpms rather
than those distributed with the LCG 2.7.0 release.

* "Tank & Spark" has been removed from the CE configuration.
This was never configured by LCG.  This removes an unneeded 
service from the CE and removes the need for MySQL. 

Minor Issues
------------

* Resource Broker: LB user and database still needs to be 
configured manually.  (DLI/RLSCatalog configuration is now
handled by the VO configuration.)

* Computing Element: The NFS mounts are still handled by direct
configuration rather than automount.  The automount configuration
will be added later.  This is only a problem if the WNs are 
updated/installed before the gatekeeper. 

* User Interface: The vomsclient configuration is not handled
for the VOs.  The component exists, but the information has not
been collected for most VOs. 

* Worker Node: No known issues. 

* SE Classic: No known issues. 

* MON Box (R-GMA server): No known issues. 

* MyProxy: No known issues.

* LFC: The upgrade lists should work, although this hasn't been
tested explicitly.  Use with care. 

* DPM: The upgrade lists should work, although this hasn't been
tested explicitly.  NOTE: After the upgrade, a script must be 
run to convert the internal databases to a new format!

* VOBOX: The lists should work, but no configuration has 
been created for this yet.