1 / 5

Puppet Community: Next Steps & EGI.eu Status Update

Explore the current status of Puppet usage in the EGI community and upcoming plans. Discover the Puppet Working Group's initiatives, module sharing, and plans for resource indexing. Collaborate with site managers to enhance Puppet deployment information.

nunezk
Download Presentation

Puppet Community: Next Steps & EGI.eu Status Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Puppet community Next stepsPeter Solagna – EGI.eu

  2. 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. Other activities in the community • HEPIX has a working group dedicated to Puppet. • HEPIX 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. Next steps • Publish an central index of available resources (modulesor documentation) • Similar to the hepixtwiki, 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. 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

More Related