I forgot to tell that using git for deploying puppet have also some disadvantages : you cant'use some puppet feature as external node classifiers or stored configurations. As always, there are tradeoff. For more
http: //bitfieldconsulting.com/scaling-puppet-with-distributed-version-control (the missing link) cheers 2012/7/21, Elia Pinto <gitter.spi...@gmail.com>: > Sure . There is a complete paragraph " creating decentralized puppet > architecture" in "puppet 2.7 cookbook". I am also sure to have read > the same topic on web on the site bitfieldconsulting.com , not > casually : the book's author have his blog there. Sorry i have not the > complete url now - old smartphone, no wifi etc. But i hope this can > help you the same. > > Best regards > > 2012/7/21, Martin Langhoff <martin.langh...@gmail.com>: >> On Sat, Jul 21, 2012 at 3:11 AM, Elia Pinto <gitter.spi...@gmail.com> >> wrote: >>> Well, many folks use puppet in serverless configuration pushing the >>> manifest from a central git server via cron and applying locally the >>> configuration fetched. In this sense git IS used for deployement. And, >>> for a configuration management system as puppet this could be a >>> sensible thing to do - reduce load, scalability ecc. >> >> That's a great thing to know, and timely too. I am looking at Puppet, >> and worried a bit about reported memory load on the server side (and >> some rumours of memory footprint issues on the client side too). >> >> Can you point me to more information & discussion? >> >> thanks! >> >> >> >> m >> -- >> martin.langh...@gmail.com >> mar...@laptop.org -- Software Architect - OLPC >> - ask interesting questions >> - don't get distracted with shiny stuff - working code first >> - http://wiki.laptop.org/go/User:Martinlanghoff >> > > -- > Inviato dal mio dispositivo mobile > -- Inviato dal mio dispositivo mobile -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
