1. EUDAT Data Policy Manager Mark van de Sanden (SURFsara) Maria Francesca Iozzi (SIGMA/University of Oslo) Claudio Cacciari (CINECA) RDA 3 rd Plenary meeting Practical Policy Working Group Date : 27 March 2014

2. Objectives 2 –allow a Community Manager (CM) to specify data management policies –allow a Community Manager (CM) to manage those policies via a web-portal

3. Replication 3 CM wants to specify the type of replication, the replica sites and how often data shall be replicated Replication from A to B and from B to C Replication from A to B and from A to C 789/abc 29db...279b4a 1839/abc 29db...279b4a 456/abc 29db...279b4a 1.10.13 02:00 1.10.13 00:00

4. Integrity 4 789/abc 29db...279b4a 1839/abc 29db...279b4a Checksum recalculation on the physical file 456/abc 29db...279b4a 1.10.13 02:005.10.13 05:00 1.10.13 00:00 CM wants to specify the periodicity of integrity checking

5. Data Policy Manager Portal 5 By using the portal the CM can: –Select policies (replication, integrity checking, retention, etc…) –Hand-pick the sites involved in the policy –Visualize the history of the issued policies on a searchable table The created policies are in an abstract way, i.e. independent from any technology or technology format (e.g. iRODS rules).

6. Policy hierarchy 6 Policy schema Policy template 1 Policy template 2 Policy template 3 Policy template n Policy Concrete Instance 1A Policy Concrete Instance 2A Policy Concrete Instance 3A Policy Concrete Instance nA Policy Concrete Instance 1B Policy Concrete Instance 2B Policy Concrete Instance 2C … … Policy schema: the xml schema which defines the elements of a policy document

7. Abstract Policy template 7 Policy template: the policy document which defines a policy process, but without specific parameters. Therefore the tasks are defined, but without input/output parameters. For example: replicate modify object Define data sets Define action Target descriptons Policy type

8. Concrete Policy description 8 Policy instance: the policy document which defines a policy process, but with specific parameters. 11100/6c8ac19e-c982-11e2-b3cb-e41f13eb41b2 replicate modify object CINECA /path/to/destination defaultResc

9. Data Policy Manager Architecture 9

10. Simple Replication, Replication from A to B and from A to C, Replication from A to B and from B to C,... How often should data be replicated Different protocols can be adopted (not only iRODS). CM can hand-pick the target sites 10 Data Policy Manager Portal

11. EUDAT is working on We are implementing a web-based portal to manage policies: −lightweight and easy to use tool −independent from any protocols −integrated with other EUDAT service (first and foremost with the B2SAFE service) −Authentication and authorization mechanism will be implemented to guarantee security. −Policies must be flexible to be tailored to Communities requirements. −More communities involved, more complex rules/policy- templates implemented. 11

12. Requirements − We need a structured way to define abstract policies: policies templates, policy terminology − Define policies in a flexible way: not everything is a policy, some are actions or functions of a policy − We also need –Tools to manage policies, –A mechanism to distribute policies, –Technologies adapted to work on policies 12 EUDAT: Data Policy Manager Currently basic HTTP get EUDAT: iRODS!