Skip to content

Releases: irods-contrib/metalnx-web

2.6.1

27 Mar 23:50
Compare
Choose a tag to compare
2.6.1 Release

2.6.0

12 Apr 01:35
Compare
Choose a tag to compare
2.6.0 Release

2.5.1

15 Oct 19:13
Compare
Choose a tag to compare
2.5.1 Release

2.5.0

13 Sep 23:21
Compare
Choose a tag to compare
2.5.0 Release

2.4.0

05 Jun 01:22
Compare
Choose a tag to compare
2.4.0 Release

2.3.0

26 Feb 21:23
Compare
Choose a tag to compare
2.3.0 Release

2.2.0

13 Nov 20:59
Compare
Choose a tag to compare
2.2.0 Release

2.1.0

27 Jan 15:59
Compare
Choose a tag to compare
2.1.0 Release

2.0.0

19 Apr 19:16
Compare
Choose a tag to compare

This is the first release from the iRODS Consortium.

1.4.0

19 Jul 12:11
Compare
Choose a tag to compare

This is the release of Metalnx 1.4.0.

Changes

  • Rules Deployment

    • Admin users have the option to deploy rule files into the grid
    • A rule is uploaded to the grid into the /<zone-name>/.rulecache
    • A copy of this rule is created into the /etc/irods directory
    • The rule is added to the rulebase_set section of the server_config.json file

Notes

Note that this new Rule Deployment feature is designed to work with the Metalnx MSI package 1.3.0+, which has the specific microservice that handles the deployment on each server of the grid. Previous versions of the MSI project do not have support for rules deployment, so the Metalnx Web Rules Deployment will not work. For more information about the MSI package, check out the project home page.

Be aware that by default, both iRODS and Metalnx will use CS_NEG_DONT_CARE as the negotiation policy. This implies the use of SSL for all operations.

If you do not want to use SSL at all, make sure the core.re file in iRODS is set to CS_NEG_REFUSE. Otherwise, Metalnx will fail to start.

Packages

RPM
DEB

Requirements

Check out our Wiki to see all dependencies required for the application to work.