Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
From their web site: Puppet is an open-source next-generation server automation tool. It is composed of a declarative language for expressing system configuration, a client and server for distributing it, and a library for realizing the configuration. Basically Puppet can be a (better?) replacement for cfengine (at least, I prefer it) I've contributed init scripts and portage integration to the Puppet project (available in version 0.19.0) and here you have the ebuild for this version of Puppet. Puppet needs Facter ti run (also from the same people) so you also have the corresponding ebuild in this issue. Thanks in advance
Created an attachment (id=96286) [edit] net-misc/facter-1.3.3 ebuild
Created an attachment (id=96287) [edit] net-misc/puppet-0.19.0 ebuild
Nice work, although it seems to me that facter would be better suited to dev-ruby, and while cfengine is in net-misc, I would personally put puppet in app-admin. Of course, the final decision rests with whichever dev elects to maintain the packages. I'm excited by the idea of puppet, and if it meets my needs I'll maintain it (and use it at work).
No problem in changing category, I put them in net-misc just because cfengine was there
Please don't put any new packages in net-misc :) That category is a historical dumping ground that we'd like to prevent getting out of control once more. Many thanks, Stu
Hi, Puppet looks very interesting indeed. To help with wider testing, I've put this into my server overlay. You can download this overlay by installing layman, and then running 'layman -a stuart-server'. Best regards, Stu
Oh, many thanks :)
puppet 0.19.1 is out. Haven't tested it, but just changing the ebuild name should do the trick
stuart: we (my boss and coworkers) are intending on using puppet for our boxen, so I'll take it for putting it in the tree if you want.
Hi Robin, By all means, take these packages. Let me know when they're in the tree, and I'll drop them from my overlay. Best regards, Stu
There are new versions of the packages (facter-1.3.5 and puppet-0.19.3). Just changing the ebuld name should work although I haven't tested it. In addition, it seems there's some problem with init scripts (puppet shows an error while trying to ensure a service is running). I'll take a look at it as soon as possible and provide a patch to mainstream. Anyway, contributions are welcome: it would be great if I'm not the only one working on improvements for Puppet on Gentoo!
Created an attachment (id=106338) [edit] net-misc/puppet-0.22.0 ebuild New ebuild for puppet-0.22.0. Updated facter and eix dependencies, added amd64 keyword, added some warnings in post_inst with information about requirements/limitations of puppet. Please, update in the corresponding overlay.
Created an attachment (id=106340) [edit] net-misc/facter-1.3.5 ebuild New ebuild for facter-1.3.5. Added amd64 keyword. Please, update in the corresponding overlay.
(From update of attachment 106338 [edit]) ><HTML><HEAD/><BODY><PRE># Copyright 1999-2006 Gentoo Foundation ># Distributed under the terms of the GNU General Public License v2 ># $Header$ > >inherit eutils ruby > >DESCRIPTION="A system automation and configuration management software" >LICENSE="GPL-2" >HOMEPAGE="http://reductivelabs.com/projects/puppet/index.html" >SRC_URI="http://reductivelabs.com/downloads/${PN}/${P}.tgz" >RDEPEND=">=dev-ruby/facter-1.3.5 >=app-portage/eix-0.7.9" > >SLOT="0" >IUSE="" >KEYWORDS="~x86 ~amd64" > >USE_RUBY="ruby18" > >pkg_setup() { > built_with_use virtual/ruby ipv6 || \ > die "Ruby must be built with ipv6 support, otherwise puppet will not be able to run" > > enewgroup puppet || die "Problem creating group puppet" > enewuser puppet -1 -1 /var/lib/puppet puppet || die "Problem creating user puppet" >} > >src_compile() { > DESTDIR=${D} ruby_econf || die > DESTDIR=${D} ruby_emake "$@" || die >} > >src_install() { > DESTDIR=${D} ruby_einstall "$@" || die > DESTDIR=${D} erubydoc > > # Installation of init scripts and configuration > doinitd ${S}/conf/gentoo/init.d/puppetmaster > doconfd ${S}/conf/gentoo/conf.d/puppetmaster > doinitd ${S}/conf/gentoo/init.d/puppet > doconfd ${S}/conf/gentoo/conf.d/puppet > > # Initial configuration files > dodir /etc/puppet/manifests > insinto /etc/puppet > doins ${S}/conf/gentoo/puppet/* > > # Location of log and data files > dodir /var/log/puppet > dodir /var/lib/puppet > keepdir /var/run/puppet >} > >pkg_postinst() { > ewarn "Please, *don't* include the --ask option in EMERGE_EXTRA_OPTS as this could cause puppet to hang" > ewarn "while installing packages." > ewarn > ewarn "Puppet uses eix to get information about currently installed packages, so please keep the eix" > ewarn "metadata cache updated so puppet is able to properly handle package installations." > ewarn > ewarn "Currently puppet only supports adding and removing services to the default runlevel, if you" > ewarn "want to add/remove a service from another runlevel you may do so using symlinking." >} ></PRE></BODY></HTML>
(From update of attachment 106340 [edit]) Changed category to match Stuart's overlay
Created an attachment (id=106568) [edit] app-admin/puppet-0.22.0 ebuild Changed category to match Stuart's overlay
I'll add the current versions to my (non-layman, currently) overlay at http://svn.digital-trauma.de/gentoo/trunk/. Contact me if you're interested in commit access.
Created an attachment (id=109838) [edit] 0.22.1 ebuild New ebuild for 0.22.1 version
No need to attach if you don't change anything; in overlay (layman: trauma).
if no one will take case of this ebuild, i'll do that.
go!go!go!
Created an attachment (id=113478) [edit] dev-ruby/facter-1.3.6.ebuild
Added, need tester
hi, I've been using puppet for a while and going to add it to the portage tree. Before that, according to http://mail.madstop.com/pipermail/puppet-users/2007-February/001211.html , "lockdir" in config files pretend from starting up because it's obsoleted option. I've added a logic to remove the lockdir from the default config files. I'm going to add the ebuilds to portage in the next several hours. Let me know if there are any problems.
added to the portage tree. Let me know if there are any problems. Thanks
