TRiRODS is a local meetup for iRODS users and developers in the RDU area. TRiRODS works to build a strong sense of community, to offer a space for collaboration and sharing of individual implementations of iRODS, and to further the work on a hardened version of the code.
By Jason Coposky, iRODS Consortium
Wednesday, February 19, 2020
Historically a single static policy enforcement point, such as acPostProcForPut, was the sole location for all policy implementation. With the addition of a continuation code to the rule engine plugin framework, we may now configure multiple policies to be invoked for any given policy enforcement point. This subsequently allows for a separation of concerns and clean policy implementation. The policy developers now have the ability to separate the “when” (the policy enforcement points) from the “what” (the policy itself). How the policy is then invoked becomes a matter of configuration rather than implementation.
Given this new approach, multiple policies can now be configured together, or composed, without the need to touch the code. For example, the Storage Tiering capability is effectively a collection of several basic policies: Replication, Verification, Retention, and the Violating Object Discovery. All of these policies are configured via metadata annotating root resources, and taken as a whole provide a flexible system for automated data movement.
Jason Coposky is the Executive Director of the iRODS Consortium.
Join us at our next meetup for dinner and discussion.
© 2024 RENCI
