Skip to content

Releases: opensciencegrid/osg-configure

Release 1.10.2

24 Oct 21:06
Compare
Choose a tag to compare

(SOFTWARE-2943)

This release contains the following changes since 1.9.0:

  • Fix not detecting some invalid configs with -v (SOFTWARE-2772)
  • Configures GUMS before running gums-host-cron (SOFTWARE-2792)
  • Removed all GRAM code and made attempting to configure GRAM settings an error (SOFTWARE-2821, SOFTWARE-2822)
  • Properly detect when fetch-crl is missing (SOFTWARE-2891)
  • Don't use condor_config_val -expand -- unnecessary and broken on certain 8.7 versions of HTCondor (SOFTWARE-2902)
  • Add all_fqans option to 10-misc.ini for configuring vomsmap auth to look at all VOMS FQANs (SOFTWARE-2932)
  • Internal logging, exception handling improvements, and cleanup

These changes are also in release 2.2.2.

Release 2.1.0

28 Jun 20:13
Compare
Choose a tag to compare

(SOFTWARE-2789)

This release of osg-configure contains two changes:

  • the condor-python dependency has been made optional. This is mostly a packaging change, as the modules that require condor-python (infoservices, subcluster, resourcecatalog) will no longer get installed unless the package osg-configure-infoservices is installed. The only code change here is for the test code: tests for modules that are not installed now get skipped. (SOFTWARE-2757)
  • GUMS-based auth now uses the GUMS JSON interface if gums-host-cron is not installed. (A future version of osg-configure will make the GUMS JSON interface preferred.) (SOFTWARE-2482)

These changes are also in release 1.9.0.

Release 1.9.0

28 Jun 20:14
Compare
Choose a tag to compare

(SOFTWARE-2790)

This release of osg-configure contains two changes:

  • the condor-python dependency has been made optional. This is mostly a packaging change, as the modules that require condor-python (infoservices, subcluster, resourcecatalog) will no longer get installed unless the package osg-configure-infoservices is installed. The only code change here is for the test code: tests for modules that are not installed now get skipped. (SOFTWARE-2757)
  • GUMS-based auth now uses the GUMS JSON interface if gums-host-cron is not installed. (A future version of osg-configure will make the GUMS JSON interface preferred.) (SOFTWARE-2482)

These changes are also in release 2.1.0.

Release 2.0.0

31 May 15:08
Compare
Choose a tag to compare

The first release for OSG 3.4 only, this release removed or disabled features that are no longer supported in OSG 3.4 (many of which are also unsupported or barely supported in OSG 3.3). The dropped features are:

  • managedfork and network config, which was GRAM only and unsupported on 3.3 as well (SOFTWARE-2705)
  • GRAM configuration, which is unsupported on 3.3 as well and now raises an error when the user tries to request GRAM (SOFTWARE-2726)
  • glexec - now raises an error when the user tries to request it (SOFTWARE-2697)
  • osg-cleanup - also GRAM-only, and has been a no-op for a while (SOFTWARE-2695)
  • the "configure-osg" symlink to the osg-configure script (SOFTWARE-2743)

In addition:

  • the default auth method was changed to "vomsmap". Requesting "xacml" (i.e. GUMS) auth now raises a warning (SOFTWARE-2737)
  • an empty "allowed_vos" attribute is no longer allowed in Subcluster or Resource Entry sections (SOFTWARE-2703)

This release includes all the changes from 1.8.0 as well.

Release 1.8.1

30 May 21:28
Compare
Choose a tag to compare

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 using vomsmap auth, and is done for subclusters where allowed_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

Release 1.7.0

24 Apr 21:13
Compare
Choose a tag to compare
  • Drop GIP/OSG-Info-Services support (SOFTWARE-2644)
  • Make absence of user-vo-map file non-fatal (SOFTWARE-2696)
  • Create /etc/lcmaps.db from template and add voms-mapfile support (SOFTWARE-2601)
    (adds dependency on lcmaps-db-templates (SOFTWARE-2692)

Release 1.6.2

29 Mar 20:59
Compare
Choose a tag to compare

This fixes two of the infoservices unit tests so they properly get skipped when osg-info-services is not installed. (SOFTWARE-2655)

Release 1.6.1

30 Jan 23:05
Compare
Choose a tag to compare

This contains a fix for Resource Entry sections for checking config correctness (i.e. osg-configure -v) where osg-configure was not raising an error on missing attributes (e.g. maxmemory). SOFTWARE-2562

Release 1.5.3

29 Nov 16:39
Compare
Choose a tag to compare

Contains fix for SOFTWARE-2311, properly quoting values entered into Gratia ProbeConfig files.

Another bugfix for Resource Entry feature

11 Nov 20:33
Compare
Choose a tag to compare
v1.5.2

Bump version to 1.5.2