Stable-20250210

This is a bugfix and feature release:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173+179+180)
• Prevent external users changing ID fields during semi-automatic renew with authentication (PR174)
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Switched unit testing to consistent docker containerization for py2+3 but still with native support (PR134)
• Fix a corner-case bug with exceptions in output handling (PR178)
• Clean up old unused native dev account code obsoleted by containerized deployments (PR185)
• Fix crashes in the PAM module on Rocky/RHEL 8+ in the handling of repeated sftpsubsys login failures (PR188+189)
• Helper to refresh old accounts in relation to switch from OpenID 2.0 to OpenID Connect auth provider (PR181)
• Integration of built-in status page as standalone virtual host alias like https://status.erda.dk (PR192)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and about to be phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding main and next (previously edge and experimental) branches used in production. Thus, we recommend using Main for any legacy python2 and Next for all python3 deployments.

Next-20250121-rc3

This is a bugfix and feature release candidate for the upcoming proper release. It extends the previous release candidates:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173+179+180)
• Prevent external users changing ID fields during semi-automatic renew with authentication (PR174)
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Switched unit testing to consistent docker containerization for py2+3 but still with native support (PR134)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Main-20250121-rc3

This is a bugfix and feature release candidate for the upcoming proper release. It extends the previous release candidates:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173+179+180)
• Prevent external users changing ID fields during semi-automatic renew with authentication (PR174)
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Switched unit testing to consistent docker containerization for py2+3 but still with native support (PR134)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Next-20250110-rc2

This is a bugfix and feature release candidate for the upcoming proper release. It extends the previous release candidate:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173)
• Prevent external users changing ID fields during semi-automatic renew with authentication
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Main-20250110-rc2

This is a bugfix and feature release candidate for the upcoming proper release. It extends the previous release candidate:

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Optionally allow auto-signup for external users e.g. from WAYF if they have existing peer acceptance (PR166)
• Prevent GDP log messages propagating to mig.log
• Updated front pages to use OIDC instead of OID 2.0 service for local user auth (reused as template)
• Key+certificate improvements to allow fully automatic fingerprint updates e.g. with LetsEncrypt (PR171+173)
• Prevent external users changing ID fields during semi-automatic renew with authentication
• UI polish: show explanatory warning when not allowed to create vgrids/workgroups (PR170)
• Added basic per-user account page with account info (PR176)
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Next-20241213-rc1

This is a bugfix and feature release candidate for the next proper release.

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Main-20241213-rc1

This is a bugfix and feature release candidate for the next proper release.

• Fix to gdp mode project handover in python3
• Fix choice of python in sftpsubsys PAM auth extension on python2 when 3 is also installed
• general grid compute bugfixes for python3
• Increased unit test coverage

Additional details are available in the complete changelog since last release for further elaboration in the real release.

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Next-20241023

This is a bugfix and feature release.

• Workaround to avoid excessive memory use during certain web downloads (#119) with new wwwserve_max_bytes limit
• Tune SFTP security for modern OS versions and try harder to mitigate Terrapin issue on some legacy systems (PR132)
• Skip making pointless client ID directory in user_pending during account create/renew (#141) to reduce log noise
• Avoid copy of unique ID to project users when in gdp_mode to avoid bogus ID collision warnings on user renew/edit
• Cloud instance status page improvement and polish to clarify jump host setup
• Expose storage_protocols for use e.g. in above size limit hint for #119 and reuse in Duplicati protocol selection
• Internal configuration restructuring for better unit testing and potential future interactive configuration features
• Fix a unit test regression during test clean up
• Increased unit test coverage

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Main-20241023

This is a bugfix and feature release.

• Workaround to avoid excessive memory use during certain web downloads (#119) with new wwwserve_max_bytes limit
• Tune SFTP security for modern OS versions and try harder to mitigate Terrapin issue on some legacy systems (PR132)
• Skip making pointless client ID directory in user_pending during account create/renew (#141) to reduce log noise
• Avoid copy of unique ID to project users when in gdp_mode to avoid bogus ID collision warnings on user renew/edit
• Cloud instance status page improvement and polish to clarify jump host setup
• Expose storage_protocols for use e.g. in above size limit hint for #119 and reuse in Duplicati protocol selection
• Internal configuration restructuring for better unit testing and potential future interactive configuration features
• Fix a unit test regression during test clean up
• Increased unit test coverage

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.

Stable-20241023

This is a bugfix and feature release.

• Workaround to avoid excessive memory use during certain web downloads (#119) with new wwwserve_max_bytes limit
• Tune SFTP security for modern OS versions and try harder to mitigate Terrapin issue on some legacy systems (PR132)
• Skip making pointless client ID directory in user_pending during account create/renew (#141) to reduce log noise
• Avoid copy of unique ID to project users when in gdp_mode to avoid bogus ID collision warnings on user renew/edit
• Cloud instance status page improvement and polish to clarify jump host setup
• Expose storage_protocols for use e.g. in above size limit hint for #119 and reuse in Duplicati protocol selection
• Internal configuration restructuring for better unit testing and potential future interactive configuration features
• Fix a unit test regression during test clean up
• Increased unit test coverage

Note: the Stable-YYYYMMDD release series specifically refers to the master branch, which is strictly in lock-step with the old SourceForge repo and being phased out. The matching Main-YYYYMMDD and Next-YYYYMMDD releases refer to the corresponding edge and experimental branches used in production - despite the somewhat misleading branch names. Thus, we recommend using Main for python2 and Next for python3 deployments.