A pretty full month for development this time - we're in a full sprint until the Netherlands.
It's the last day for submission of UGM2019 abstracts! Register today and submit your talks for Utrecht!
In working towards our 4.3.0 release, we now have parallel building and testing of our many plugins. We've got a prototype of topology testing Dockerized and hope to have Federation completed soon as well. We can start building and testing iRODS in parallel within days. This has been a long time coming.
NFSRODS is all but ready - expect a first release soon. It has already been deployed into an enterprise environment and is being tested for performance and compliance. We simplified the security model to assume identity/user management is already in place. The new model assumes that the user traversing the mount point is already authenticated - and presents that user with a view of their iRODS collections and data objects. It's very clean.
Metalnx 2.0.0 was released a couple weeks ago! Since the merger of Dell and EMC was announced in 2015, this release marks the completion of the contribution of the codebase to the iRODS Consortium. We'll continue to work to make Metalnx even easier to stand up and maintain. It's nice to have a few different iRODS clients production-ready.
We are investigating new transport mechanisms within iRODS. With our new stream operators, we are looking into new approaches that work with UDT, FDT, and RDMA. If you have interest or working knowledge of best practices or design criteria, please get in touch. If there is enough interest, we could schedule a quick conference call (or even spin up a Working Group).
We have isolated and fixed an issue within the irodsReServer that will be included in 4.2.6. Also to be included is some additional work on the new irods::filesystem collection iterator. As we continue to refactor our own code, the new things are being more deeply exercised. Expect this release within the week.
In the run-up to iRODS 4.3.0, we have settled on rsyslog and JSON for the new logging infrastructure. However, the option to run iRODS as a Non-Package Install requires a bit more thinking (rsyslog may not be running or under the control of the user running the iRODS server). We've started a promising conversation around how these options can play well with each other (perhaps a 'foreground' option...). Please share your input in the Google Group.
Active Development Work
Python iRODS Client (PRC)
Cacheless and Detached S3
iRODS Capability - Automated Ingest
Multipart Transfer, v5 API
Storage Tiering Capability Package
Continuous Integration (CI)
Samba/CIFS/SMB project to surface iRODS as SMB
Python Rule Engine Plugin
CockroachDB Database Plugin
Swagger REST API