Re: [Puppet Users] librarian-puppet vs R10K
The requirement to "deploy code in complex ways" sounds like an "enterprise" thing. On the one hand, these companies may have few spare cycles for synchronizing configurations across disparate customer-facing products. On the other hand, there can be certain strategically important environments whose change managment is subject to agreements with major customers and operate on a different set of timelines. On the third hand, there can be a myriad of currently-unknown reasons why you would need the flexibility to do something complicated. Not to say that r10k versus other things (monolithic repositories for one) haven't been a subject of intense debate here too, they have. My current thinking is that we can more maintainably use a subset of r10k functionality than bolt stuff on to a simpler system on an ad-hoc basis. I think of things like ldap/r10k/radius as items which it really helps to already have when you start getting large and complicated problems. On Thu, Jan 28, 2016 at 06:40:15AM -0800, Alex Harvey wrote: >Hi all, >I am interested in the future of the Librarian-puppet project - to find >out how many people are still using it, and if there are people out there >who actually prefer it over R10K. >I recently looked into R10K for a few projects I was working on, and I >found it to be surprisingly complicated. It had many features I didn't >seem to need, features that overlap with features provided by >Jenkins/Bamboo, and appeared designed with a view to helping people deploy >code in complex ways, help them to test short lived branches on Puppet >masters, etc. This might have made sense once, but if you're doing all >your development in a test-driven fashion in Vagrant/Rspec-puppet/Beaker, >I can't see a need for R10K's features, and concluded it was mainly just a >lot harder to understand than Librarian-puppet. I do see that it performs >better, but again, Librarian-puppet has never been a bottleneck. >Other views most appreciated. >With best regards, >Alex > >-- >You received this message because you are subscribed to the Google Groups >"Puppet Users" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to [1]puppet-users+unsubscr...@googlegroups.com. >To view this discussion on the web visit > > [2]https://groups.google.com/d/msgid/puppet-users/639366f5-0fc8-47f8-a1ed-541c79dbc07c%40googlegroups.com. >For more options, visit [3]https://groups.google.com/d/optout. > > References > >Visible links >1. mailto:puppet-users+unsubscr...@googlegroups.com >2. > https://groups.google.com/d/msgid/puppet-users/639366f5-0fc8-47f8-a1ed-541c79dbc07c%40googlegroups.com?utm_medium=email_source=footer >3. https://groups.google.com/d/optout -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20160128162936.GA15474%40iniquitous.heresiarch.ca. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] librarian-puppet vs R10K
On Thu, 2016-01-28 at 06:40 -0800, Alex Harvey wrote: > Hi all, > > I am interested in the future of the Librarian-puppet project - to > find out how many people are still using it, and if there are people > out there who actually prefer it over R10K. > There's another one to consider https://github.com/cernops/jens it recently got an update to accept hook calls from gitlab. We get our git pushes deployed in 0.4s now. > I recently looked into R10K for a few projects I was working on, and > I found it to be surprisingly complicated. It had many features I > didn't seem to need, features that overlap with features provided by > Jenkins/Bamboo, and appeared designed with a view to helping people > deploy code in complex ways, help them to test short lived branches > on Puppet masters, etc. This might have made sense once, but if > you're doing all your development in a test-driven fashion in > Vagrant/Rspec-puppet/Beaker, I can't see a need for R10K's features, > and concluded it was mainly just a lot harder to understand than > Librarian-puppet. I do see that it performs better, but again, > Librarian-puppet has never been a bottleneck. > > Other views most appreciated. > > With best regards, > Alex -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1453995036.31188.4.camel%40cern.ch. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] librarian-puppet vs R10K
On 1/28/16 9:40 AM, Alex Harvey wrote: > Hi all, > > I am interested in the future of the Librarian-puppet project - to find > out how many people are still using it, and if there are people out > there who actually prefer it over R10K. > > I recently looked into R10K for a few projects I was working on, and I > found it to be surprisingly complicated. It had many features I didn't > seem to need, features that overlap with features provided by > Jenkins/Bamboo, and appeared designed with a view to helping people > deploy code in complex ways, help them to test short lived branches on > Puppet masters, etc. This might have made sense once, but if you're > doing all your development in a test-driven fashion in > Vagrant/Rspec-puppet/Beaker, I can't see a need for R10K's features, and > concluded it was mainly just a lot harder to understand than > Librarian-puppet. I do see that it performs better, but again, > Librarian-puppet has never been a bottleneck. > > Other views most appreciated. > > With best regards, > Alex Hi Alex, I generally implement both for customers. Though I use Dan Bode's librarian-puppet-simple which purposely does not handle dependencies. I spoke at a couple Puppet Camp's regarding dealing with modules and here are slides[1] explaining the pro's and con's of the different approaches. R10k is great, even with a build pipeline, because the caching feature really speeds up the build jobs over librarian-puppet, which will need to download the git repo's each time. I maintain a bunch of modules that you might consider as common or base to an OS such as SSH, NTP, PAM, hosts, timezone, NFS, etc as well as code for modeling PuppetDB, Puppet agents and masters that are tracked in a Puppetfile[2]. Since that has its own life cycle outside of the clients' and does not need git branch to environment mapping it is maintained with librarian-puppet-simple. I've also used r10k to build Puppet platform as a service for large enterprises that have many products and teams with their own distinct environments. This allows many teams to leverage each others work while giving them their own autonomy with regards to number of environments, testing abilities, module versions and release schedules. [1] - http://www.slideshare.net/gh/2014-multiple-approaches-to-managing-puppet-modules-puppet-camp-seattle [2] - https://github.com/ghoneycutt/puppet-modules Best regards, -g -- Garrett Honeycutt @learnpuppet Puppet Training with LearnPuppet.com Mobile: +1.206.414.8658 -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/56AA68D0.4070304%40garretthoneycutt.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] librarian-puppet vs R10K
On Friday, January 29, 2016 at 2:31:14 AM UTC+11, Steve Traylen wrote: > > > There's another one to consider > https://github.com/cernops/jens > it recently got an update to accept hook calls from gitlab. We get > our git pushes deployed in 0.4s now. > Thanks I'll keep it in mind! > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/384059a2-15e6-4996-b139-4f3c908dea76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] librarian-puppet vs R10K
Hi all, I am interested in the future of the Librarian-puppet project - to find out how many people are still using it, and if there are people out there who actually prefer it over R10K. I recently looked into R10K for a few projects I was working on, and I found it to be surprisingly complicated. It had many features I didn't seem to need, features that overlap with features provided by Jenkins/Bamboo, and appeared designed with a view to helping people deploy code in complex ways, help them to test short lived branches on Puppet masters, etc. This might have made sense once, but if you're doing all your development in a test-driven fashion in Vagrant/Rspec-puppet/Beaker, I can't see a need for R10K's features, and concluded it was mainly just a lot harder to understand than Librarian-puppet. I do see that it performs better, but again, Librarian-puppet has never been a bottleneck. Other views most appreciated. With best regards, Alex -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/639366f5-0fc8-47f8-a1ed-541c79dbc07c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] librarian-puppet vs R10K
On Friday, January 29, 2016 at 6:15:41 AM UTC+11, Garrett Honeycutt wrote: > > > Hi Alex, > > I generally implement both for customers. Though I use Dan Bode's > librarian-puppet-simple which purposely does not handle dependencies. I > spoke at a couple Puppet Camp's regarding dealing with modules and here > are slides[1] explaining the pro's and con's of the different approaches. > Thanks. Your slides are just what I needed to see. And I didn't know about librarian-puppet-simple and I'm glad I do now. Yes, dependency resolution is indeed a mixed blessing. When you say you implement both do you mean you use librarian-puppet-simple on the CI side of the pipeline and R10K on the deployment to Puppet masters side? > > R10k is great, even with a build pipeline, because the caching feature > really speeds up the build jobs over librarian-puppet, which will need > to download the git repo's each time. > It may be a documentation problem that I'm struggling with. You don't happen to know of any code or documentation that shows how to R10K in the build pipeline? By the way, Librarian-puppet does support caching via $LIBRARAN_PUPPET_TMP, which can point to a long-lived directory on the CI server. So, actually, Librarian-puppet has never been a bottleneck for me, and unnoticeable relative to the time it takes all the tests to run. > I've also used r10k to build Puppet platform as a service for large > enterprises that have many products and teams with their own distinct > environments. This allows many teams to leverage each others work while > giving them their own autonomy with regards to number of environments, > testing abilities, module versions and release schedules. > I'd love to know more about this. :) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4677fe0e-4a21-4635-9333-2a2c99f516ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] librarian-puppet
Did you install puppet via an RPM? If so, this patch will likely fix your issue. https://github.com/rodjek/librarian-puppet/issues/38 On Oct 31, 2012, at 2:52 PM, Worker Bee beeworke...@gmail.com wrote: Unless I install puppet vis gems, I get the following error when attempting to use librarian-puppet. librarian-puppet /usr/lib/ruby/site_ruby/1.8/rubygems.rb:779:in `report_activate_error': Could not find RubyGem puppet (= 0) (Gem::LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:214:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:1082:in `gem' from /usr/bin/librarian-puppet:18 Has anyone created a workaround for this? Thanks! bee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] librarian-puppet
Unless I install puppet vis gems, I get the following error when attempting to use librarian-puppet. librarian-puppet /usr/lib/ruby/site_ruby/1.8/rubygems.rb:779:in `report_activate_error': Could not find RubyGem puppet (= 0) (Gem::LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:214:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:249:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `each' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:248:in `activate' from /usr/lib/ruby/site_ruby/1.8/rubygems.rb:1082:in `gem' from /usr/bin/librarian-puppet:18 Has anyone created a workaround for this? Thanks! bee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] librarian-puppet vs git superproject?
On 24 July 2012 00:43, Ryan Bowlby rbowlb...@gmail.com wrote: Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet? I've been using git subtree merge for this. I think it is better than git submodules as it limits the complexity to only the people merging and updating external modules (and it's really not that complex). But people can continue to commit fixes without much hassle or updating multiple repositories. Some wrapper scripts against git subtree are here: https://github.com/apenwarr/git-subtree/ Or in contrib in git 1.7.11+ One advantage of librarian-puppet though is that you can effectively create topic branches where only one module is denomalized but the rest are following the latest version you have. That sort of workflow is clunky at best with submodules/subtrees. -- Erik Dalén -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] librarian-puppet
I've heard this project mentioned a few times and I have found the projects site on github. Is there information available on how to setup the repos that it would pull from (layout etc)? The boxes I would be using this on do not have access to the Puppet Forge but this project looks like it would be useful in addressing somethings I've been trying to decide on how to handle for a while now. I know that as of yet there isn't a way to setup a true private forge, though some options are in the works (pulp, for example). Unfortunately, pulp is currently on officially supported on Fedora/RHEL based systems and YUM repos, though they are working on expanding the options. Any other suggestions or recommendations for getting started with this would be appreciated as well. Thanks. --Lee -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Ro7BbUmQctMJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] librarian-puppet vs git superproject?
On Mon, Jul 23, 2012 at 8:43 PM, Dan Bode d...@puppetlabs.com wrote: On Mon, Jul 23, 2012 at 3:43 PM, Ryan Bowlby rbowlb...@gmail.com wrote: Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? I tried using git submodules for a long time. I found that I just could not keep up with updating changed modules in two places (the module repo and the superproject repo). I wound up with projects that were never quite in sync. My other problem is that the puppet ecosystem (the forge, etc) does not really have a concept of a super project. All that it has is modules. I wound up switching to yaml files that specify dependencies with a rake task. This way, I can have superprojects that are themselves puppet modules. It also allows me to only check in the fact that master of all modules should work with master of its dependencies (which is almost always the state that I want checked-in) For an example, have a look at the rake tasks for the puppetlabs-openstack modules: https://github.com/puppetlabs/puppetlabs-openstack/blob/master/Rakefile I would love to see something like this eventually expanded into the Modulefile. I havent really looked at librarian yet, but I am interested. I probably should have looked into puppet librarian before sending this email. Its very similar to the custom yaml files with rake tasks that I had mentioned before. I should actually be able to remove my custom yaml files and drop in puppet-librarian. We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet? Thanks, Ryan Bowlby -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4Kf47PY2sIwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] librarian-puppet vs git superproject?
Thanks all, we've decided to stick with git super project and per module repositories. Some of the modules will be a clone from github, but most are internal. It seems to suit our needs and we don't see a reason to implement librarian-puppet. Ohad, I setup pulp at work and it's pretty good (tasks get stuck occasionally). We don't use consumer though, we manage packages via puppet. I'm actually thinking of creating a pulp defines for some of the pulp-server tasks pulp-admin repo create. I guess I should publish our existing pulp module. I take it you're talking about a future release where pulp has a plugin model and is more of a generalized manage all the things tool? Is there going to be a plugin for the forge or something? -Ryan On Tuesday, July 24, 2012 1:00:00 AM UTC-7, ohad wrote: On Tue, Jul 24, 2012 at 9:49 AM, David Schmitt da...@dasz.at wrote: On 24.07.2012 00:43, Ryan Bowlby wrote: Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet? I've played around with repo (android's git forest manager) but it's just too much complexity for non-developers. I've now switched to everything in one .git and it's just so much easier to manage. Putting external modules in a separate branch and then subtree merge is a viable, albeit still too complex, way for tracking externals. I myself still use submodules, as most of my modules are not in the forge, maybe that would change once pulp will offer an alternative. Ohad Best Regards, David -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@** googlegroups.com puppet-users%2bunsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/** group/puppet-users?hl=enhttp://groups.google.com/group/puppet-users?hl=en . -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/L6w5ahoRnKsJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] librarian-puppet vs git superproject?
Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet? Thanks, Ryan Bowlby -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4Kf47PY2sIwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] librarian-puppet vs git superproject?
On Mon, Jul 23, 2012 at 3:43 PM, Ryan Bowlby rbowlb...@gmail.com wrote: Can anyone comment on their experiences with librarian-puppet or using git superproject with per puppet module repositories? I tried using git submodules for a long time. I found that I just could not keep up with updating changed modules in two places (the module repo and the superproject repo). I wound up with projects that were never quite in sync. My other problem is that the puppet ecosystem (the forge, etc) does not really have a concept of a super project. All that it has is modules. I wound up switching to yaml files that specify dependencies with a rake task. This way, I can have superprojects that are themselves puppet modules. It also allows me to only check in the fact that master of all modules should work with master of its dependencies (which is almost always the state that I want checked-in) For an example, have a look at the rake tasks for the puppetlabs-openstack modules: https://github.com/puppetlabs/puppetlabs-openstack/blob/master/Rakefile I would love to see something like this eventually expanded into the Modulefile. I havent really looked at librarian yet, but I am interested. We are in the midst of determining which route is optimal for our environment. It seems like using git superprojects would mean one less new tool for everyone to learn. What then would be the advantages of librarian-puppet? Thanks, Ryan Bowlby -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4Kf47PY2sIwJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
