1. www.egi.eu EGI-InSPIRE RI-261323 EGI-InSPIRE www.egi.eu EGI-InSPIRE RI-261323 UMD Platform Documentation Álvaro Simón CESGA 02/12/2011 SA2 TF2011, Amsterdam1

2. www.egi.eu EGI-InSPIRE RI-261323 Outline Requirements Documentation structure Information providers Documentation maintenance Conclusions 02/12/2011 SA2 F2F2011, Amsterdam2

3. www.egi.eu EGI-InSPIRE RI-261323 Requirements As democratic as possible: Documentation valid for newbie's and experienced administrators. Easily accessible: Create a single endpoint as main entrance to guide the user to a specific subject. Keep as simple as possible : Documentation pages should be maintained by different persons. A simple documentation structure will help future maintainers. Include all the platforms: UMD documentation must include information for all platforms available within EGI repository. Service oriented: TPs products are grouped into services. 02/12/2011 SA2 F2F2011, Amsterdam3

4. www.egi.eu EGI-InSPIRE RI-261323 Documentation Structure 02/12/2011 SA2 F2F2011, Amsterdam4 A single main entrance must show a generic schema and a short description for each platform. ScalePlatform gLiteUnicoredCacheArc Big Production sites with more than x jobs processed per h. Storage > x Tb. gLite has different services. Production sites with more than x jobs processed per h. Storage > x Tb. Big sites which need to store and retrieve huge amounts of data distributed in different nodes. Production sites with more than x jobs processed per h. Storage > x Tb. Medium? Small No production sites or less than x jobs processed per h. Storage < x Tb N/ANo production sites or less than x jobs processed per h. Storage < x Tb

5. www.egi.eu EGI-InSPIRE RI-261323 Documentation Structure 02/12/2011 SA2 F2F2011, Amsterdam5 After the first selection we know the platform and the scale desired by the user. At this point we can show the available capabilities for the desired platform. As example for gLite: ClientComputeDataInformationOperationsSecurityStorage UICREAM CELFCBDII siteAPELVOMSDPM BDII TopARGUSStoRM Proxyrenewal

6. www.egi.eu EGI-InSPIRE RI-261323 Documentation Structure 02/12/2011 SA2 F2F2011, Amsterdam6 This structure has several advantages: The user can choose between different platforms in the first level. After 2 clicks the desired information is shown. Gives an overview about the different capabilities available in each platform.

7. www.egi.eu EGI-InSPIRE RI-261323 Documentation Structure 02/12/2011 SA2 F2F2011, Amsterdam7 Products

8. www.egi.eu EGI-InSPIRE RI-261323 Documentation Structure 02/12/2011 SA2 F2F2011, Amsterdam8 Each product has its own wiki page and includes different sections. Product overview: A brief description about product capabilities and available services. Summary of appliances provided by the product. Installation & Configuration: Links provided by the TP to install and configure each service. Deployment Scenarios: This section includes different kind of configurations for small/big deployments. Tips & Tricks: Known tricks provided by experienced site admins.

9. www.egi.eu EGI-InSPIRE RI-261323 Information providers 02/12/2011 SA2 F2F2011, Amsterdam9 We have two main information providers and their feedback is crucial for this task. TP Experienced site admins and sites. We have contacted with EMI (Morris Riedel) but we didn’t receive any response (yet). Mario will contact with the sites and EAs. We will fill the wiki little by little, based on the information gathered from the TPs and sites.

10. www.egi.eu EGI-InSPIRE RI-261323 Documentation maintenance 02/12/2011 SA2 F2F2011, Amsterdam10 The documentation wiki pages need a maintainer or maintainers. This task can be shared between different SA2 members (by shift handover?). Scheduled documentation maintenance: The documentation could be outdated, we have to schedule a time period to update the wiki pages regularly. (an update each 6 months).

11. www.egi.eu EGI-InSPIRE RI-261323 Conclusions 02/12/2011 SA2 F2F2011, Amsterdam11 The UMD platform documentation project is a big task that should be shared between different teams. TPs are working to deploy a similar documentation, we should collaborate with them. (we don't need to duplicate our effort). This work will benefit future users, production sites but also to the TPs.

12. www.egi.eu EGI-InSPIRE RI-261323 Conclusions 02/12/2011 SA2 F2F2011, Amsterdam12 Comments or Suggestions?