Hello reader,
iRODS 4.3.5 is coming together very well. For those who aren't aware, it is the final release of the 4.3 series. We've closed a little over 100 issues and plan to resolve a few more before starting release testing.
Let's talk about what's happened since last month. Starting with the server, we've taught the UnregDataObj and RegReplica APIs to honor logical locking. The TicketAdminInput data structure used by the TicketAdmin API is now being serialized for policy enforcement. Work to absorb the Logical Quotas rule engine plugin is in progress. It is being modeled after physical quotas. We've re-integrated the iCommands source code into the server repository since the version numbers were always going to be tightly coupled. Lastly, the Oracle database plugin is now scheduled for deprecation.
The iRODS Testing Environment has received a very important update. This project relied on the Docker Compose v1 python library to manipulate docker containers through docker compose files. That library was deprecated some years back. We're happy to say that the Testing Environment no longer depends on the Docker Compose v1 python library.
For Policy Composition, we're still making progress towards an initial release. The access time policy engine has been removed and we're now working on various smaller tasks such as build and test hooks for automated testing via GitHub Actions.
Work to add support for CRC64/NVME to the S3 resource plugin continues. We have an initial implementation that shows promise. It is now going through the review process.
The Storage Tiering rule engine plugin has received a small, but important fix involving permissions during checksum verification. The fix will be included in the next release of the plugin.
For the Python iRODS client (PRC), a new reusable GitHub Actions workflow was added to help catch formatting issues and potential bugs.
On the iRODS S3 API front, we're working to improve compatibility with various GUI applications such as Cyberduck and S3 Browser. If there are other GUIs we should test against, please reach out to us.
To wrap up, the pull requests for Cyberduck which replace Jargon with irods4j have been merged. This work was initially implemented by one of our interns.
Thanks for reading.
New Development Work
Active Development Work
Docker-based Testing Environment
Cyberduck
Background Items
Build and Packaging
Docker-based Development Environment
PAM Interactive Authentication Plugin
CockroachDB Database Plugin
iRODS Kubernetes Testing Environment
iRODS Command Line Interface (CLI)
Logical Locking
New RPC API framework
Parallel Filesystem Integration
Discussion