Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Preview 2.29.0"

From EGIWiki
Jump to navigation Jump to search
Line 2: Line 2:
Back to [https://wiki.egi.eu/wiki/Preview_Repository#Repository_configuration repository configuration]
Back to [https://wiki.egi.eu/wiki/Preview_Repository#Repository_configuration repository configuration]


= BDII 5.5.26 and glite-info-update-endpoints 3.0.2 =
= BDII 5.5.26 =
The Berkeley Database Information Index (BDII) consists of two or more standard LDAP databases that are populated by an update process. Port forwarding is used to enable one or more databases to serve data while one database is being refreshed. The databases are refreshed cyclically. Any incoming connection is forwarded to the most recently updated database, while old connections are allowed to linger until it is the turn of their database to be refreshed and restarted. The update process obtains LDIF from either doing an ldapsearch on LDAP URLs or by running a local script (given by a URL with "file" protocol) that generates LDIF. The LDIF is then inserted into the LDAP database. Options exist to update the list of LDAP URLs from a web page and to use an LDIF file from a web page to modify the data before it is inserted into the database.


'''Release notes''':
See more information [https://github.com/EGI-Foundation/bdii here]
* BDII: https://github.com/EGI-Foundation/bdii/releases/tag/v5.2.26
 
* glite-info-update-endpoints: https://github.com/EGI-Foundation/glite-info-update-endpoints/releases/tag/v3.0.2
'''Release notes''': https://github.com/EGI-Foundation/bdii/releases/tag/v5.2.26
 
= glite-info-update-endpoints 3.0.2 =
This component is used with Top BDII and is intented to update LDAP endpoits for EGI. BDII documentation is available here: https://gridinfo-documentation.readthedocs.io/
 
''glite-info-update-endpoints'' is a cron job that runs every hour to download the list of site BDII URLs that are going to be used by the top level BDII to publish their resources.
 
The script uses the ''/etc/glite/glite-info-update-endpoints.conf'' file which by default is configured to use EGI's list of site BDIIs. The list of site BDIIs is taken from the EGI GOCDBs.
 
See more information [https://github.com/EGI-Foundation/glite-info-update-endpoints here].
 
'''Release notes''': https://github.com/EGI-Foundation/glite-info-update-endpoints/releases/tag/v3.0.2


= STORM 1.11.18 =
= STORM 1.11.18 =

Revision as of 15:36, 24 September 2020

Back to repository configuration

BDII 5.5.26

The Berkeley Database Information Index (BDII) consists of two or more standard LDAP databases that are populated by an update process. Port forwarding is used to enable one or more databases to serve data while one database is being refreshed. The databases are refreshed cyclically. Any incoming connection is forwarded to the most recently updated database, while old connections are allowed to linger until it is the turn of their database to be refreshed and restarted. The update process obtains LDIF from either doing an ldapsearch on LDAP URLs or by running a local script (given by a URL with "file" protocol) that generates LDIF. The LDIF is then inserted into the LDAP database. Options exist to update the list of LDAP URLs from a web page and to use an LDIF file from a web page to modify the data before it is inserted into the database.

See more information here

Release notes: https://github.com/EGI-Foundation/bdii/releases/tag/v5.2.26

glite-info-update-endpoints 3.0.2

This component is used with Top BDII and is intented to update LDAP endpoits for EGI. BDII documentation is available here: https://gridinfo-documentation.readthedocs.io/

glite-info-update-endpoints is a cron job that runs every hour to download the list of site BDII URLs that are going to be used by the top level BDII to publish their resources.

The script uses the /etc/glite/glite-info-update-endpoints.conf file which by default is configured to use EGI's list of site BDIIs. The list of site BDIIs is taken from the EGI GOCDBs.

See more information here.

Release notes: https://github.com/EGI-Foundation/glite-info-update-endpoints/releases/tag/v3.0.2

STORM 1.11.18

The StoRM Product Team is pleased to announce the release of StoRM 1.11.18 that includes the following updated components:

This release introduces the support for CentOS 7 for all StoRM components.

It also provides fixes to some outstanding bugs, in particular:

  • fixes errors on published storage space occupancy in case multiple storage area shares the same VO;
  • fixes not published WebDAV endpoints when latest logic is used;
  • fixes not dropped Authorization header in WebDAV TPC redirects;
  • fixes leaked file descriptors when Conscrypt is enabled on StoRM WebDAV;
  • sets correctly HTTP content-length for large files;
  • fixes errors on transferred files through GridFTP that leave empty files with an adler32 checksum for a non-empty file;
  • fixes KillMode on GridFTP systemd unit.

It also provides several improvements, in particular:

  • fixes wrong ERROR log messages when file does not exist on srmRm requests;
  • changes the way info provider checks if Backend is running;
  • introduces a Background DU Service (disabled by default) that periodically updates the storage space info for non-GPFS storage areas (read more info here);
  • adds Date and thread pools metrics in the metrics logged info;
  • updates spring boot to 2.2.6 release for StoRM WebDAV;
  • adds SystemD support for StoRM Backend and StoRM Frontend.

Please, follow the upgrade instructions.

Starting from StoRM v1.11.18 StoRM production repository has been migrated. Read how to install/upgrade StoRM repositories into the Downloads section.

Read the release notes for more details.