1. www.egi.euEGI-InSPIRE RI-261323 www.egi.eu EGI-InSPIRE RI-261323 Puppet community Next steps Peter Solagna – EGI.eu

2. www.egi.euEGI-InSPIRE RI-261323 Current status Based on the survey circulated at the beginning of this year in EGI: –18 sites (out of 97) are using Puppet as configuration manager –6 sites (out of 97) are using CFengine NGI_HR, Ibergrid and CERN experiences about Puppet were presented during the Resource Centre forum at the TF2013 The target for this activity is to share site manager experience, not to choose puppet as an official replacement for YAIM

3. www.egi.euEGI-InSPIRE RI-261323 Other activities in the community HEPIX has a working group dedicated to Puppet. –HEPIX Puppet WG twiki pageHEPIX Puppet WG twiki page –The wiki collects the modules shared by the participant sites (CERN, DESY and Bristol are the main contributors) –Focusing on EMI products

4. www.egi.euEGI-InSPIRE RI-261323 Next steps Publish an central index of available resources (modules or documentation) –Similar to the hepix twiki, the index will link to external repositories (github, puppetforge) –Collect resources about EMI, Globus and other middleware products If sites are already contributing to the HEPIX WG there is no need to duplicate the information –Will provide cross-reference between the two pages Similar index can be created for other configuration management tools such as CFengine

5. www.egi.euEGI-InSPIRE RI-261323 Summary Once the structure for the wiki page is available site managers will be notified, asking to populate it with their contributions: –Author/site/contact –Services configured –OS platform –Supported Puppet versions –Dependencies (e.g. YAIM) –License information In some cases the sites may need to clean the modules code before sharing –If a site does not want to share, it’s absolutely understandable