Release 1.8.1
The big change for this release is how the allowed_vos
attribute in the Subcluster
/Resource Entry
sections is handled:
- As of OSG-Configure 2.0.0 (OSG 3.4),
allowed_vos
will become mandatory, so the user is warned if it is unspecified. - Autodetection of
allowed_vos
based on existing Unix accounts now works when usingvomsmap
auth, and is done for subclusters whereallowed_vos
is "*
". - Explicitly setting
allowed_vos
to the empty string has become a warning. It will become an error in OSG-Configure 2.0.0.
In addition, in the Storage
section, app_dir
and data_dir
no longer have to exist on the CE. If they are missing, a warning is issued, but OSG-Configure keeps running.
This release contains fixes for the following tickets:
- SOFTWARE-2703 reject empty allowed_vos in subclusters
- SOFTWARE-2670 get default allowed_vos with lcmaps_voms_plugin
- SOFTWARE-2674 unnecessary check for OSG_APP and OSG_DATA