Puppet Python release?

252 views
Skip to first unread message

gluegl

unread,
Feb 23, 2009, 5:56:54 PM2/23/09
to Puppet Users
Is there a Puppet Python version?
If so where can the latest version be downloaded?
Thanks in advance,
-E

James Turnbull

unread,
Feb 23, 2009, 6:16:56 PM2/23/09
to puppet...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Not sure what you are asking.

Are you asking if Puppet supports managing python? Or if there is a
version of Puppet written in Python and not Ruby?

If the former, I am fairly sure there is a module out there somewhere
for that.

If the latter, then no - Puppet is written in Ruby.

Regards

James Turnbull

- --
Author of:
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/1590594444/)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmjLmgACgkQ9hTGvAxC30Cf+wCgm7npfcORV0MFUejEwlllzHt/
sbIAn0k5rsatgkq0YeZixyPaC/1uIuGB
=m6ih
-----END PGP SIGNATURE-----

Martin Marcher

unread,
Feb 24, 2009, 4:28:21 AM2/24/09
to Puppet Users
Hi,
I'd be interested in a python version of puppet.

Don't get me wrong it's a great tool it's just that I like python a
lot more than ruby and hence (of course) do most of my scripting in
python which leads to more python knowledge which leads (for me) to
easier expansion if it would be python instead of ruby :)

cheers,
Martin

PS: Just having wild dreams, I wouldn't expect the current codebase to
be given up because of at least 1 whacko (me, I wouldn't dare calling
anyone else a bit crazy) :)

go8ose

unread,
Feb 27, 2009, 10:15:54 PM2/27/09
to Puppet Users
>
> I'd be interested in a python version of puppet.
>
> Don't get me wrong it's a great tool it's just that I like python a
> lot more than ruby and hence (of course) do most of my scripting in
> python which leads to more python knowledge which leads (for me) to
> easier expansion if it would be python instead of ruby :)
>
> cheers,
> Martin
>
> PS: Just having wild dreams, I wouldn't expect the current codebase to
> be given up because of at least 1 whacko (me, I wouldn't dare calling
> anyone else a bit crazy) :)

Two wackos. But I know the authors aren't going to throw away the work
they have done and start again in a language that Luke originally
discarded because it annoyed him.

Nigel Kersten

unread,
Feb 27, 2009, 11:30:58 PM2/27/09
to puppet...@googlegroups.com

3. ++ to what everyone else said.

There has been discussion around a future version of Facter allowing
for facts to be provided by executables in a certain directory, which
is about as far as I can see Python integration with Puppet going.

--
Nigel Kersten
Systems Administrator
Tech Lead - MacOps

James Turnbull

unread,
Feb 28, 2009, 12:30:42 AM2/28/09
to puppet...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nigel Kersten wrote:
>
> 3. ++ to what everyone else said.
>
> There has been discussion around a future version of Facter allowing
> for facts to be provided by executables in a certain directory, which
> is about as far as I can see Python integration with Puppet going.

Agreed. That'd be a useful feature and if we'd probably do it like
Nagios plug-ins do - doesn't matter what the language is as long as they
output data that the Facter API can parse into facts - Perl, Python, C,
Rexx (*coughs*), etc.

Regards

James Turnbull

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)


Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJqMwC9hTGvAxC30ARAuOsAKCmzaXxxNdIqcuupKpvGpHOWuIY8QCeKUFg
BMcyS3AFsWyegTaLc5rUZUI=
=V2Gi
-----END PGP SIGNATURE-----

GWD

unread,
Feb 28, 2009, 9:27:14 AM2/28/09
to Puppet Users
Was hoping for something like ((for discussion purposes)MOD_PyPUPPET)
module to call Puppet from Python and write Facter Recipes from Pyhon.

Though I strongly favor Python, Puppet should make easier for other to
write their recipes in PHP, JavaScript, even Haskell....
The point being that Puppet should be call from any scripting
language...

Best,
-G

Evan Hisey

unread,
Feb 28, 2009, 9:58:11 AM2/28/09
to puppet...@googlegroups.com
I am missing something here. Why would I want to call puppet from
another scripting language? I can see wanting puppet to be able to
call or talk to other languages for may be templating purposes. But I
can already use generate() to call custom scripts in other languages.

Evan

youbiquity

unread,
Feb 28, 2009, 1:20:54 PM2/28/09
to Puppet Users
Good point..
James put it best: "That'd be a useful feature and if we'd probably do
it like
Nagios plug-ins do - doesn't matter what the language is as long as
they
output data that the Facter API can parse into fact"

Ed

James Turnbull

unread,
Feb 28, 2009, 5:16:34 PM2/28/09
to puppet...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Happy to see this in Facter - in the use case I cited in the previous
email - but I just don't see the value of this for Puppet.

I don't want to write my recipes in PHP, JS or Haskell - I want Puppet's
DSL.

If you want to CALL Puppet from any scripting language - well there is
nothing stopping you calling out to the binary or triggering a Puppet run.

Regards

James Turnbull

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)


Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJqbfC9hTGvAxC30ARAuqVAKCdlG3GZTH5cVikxaJzCHc8m52UhQCdGCoo
6KH0crADCqDfcEqtx0XDFWg=
=/Iqw
-----END PGP SIGNATURE-----

Luke Kanies

unread,
Mar 3, 2009, 11:56:56 AM3/3/09
to puppet...@googlegroups.com


Not to nit-pick, but it's more that I just couldn't write in the
language. I did try pretty hard, and have since successfully written
a bit in it (in Jython, actually), but I just could never turn my
ideas into code in Python. And no, it wasn't the white space.

--
It is dangerous to be right when the government is wrong.
-- Voltaire
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com

Luke Kanies

unread,
Mar 3, 2009, 12:02:07 PM3/3/09
to puppet...@googlegroups.com
On Feb 27, 2009, at 11:30 PM, James Turnbull wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nigel Kersten wrote:
>>
>> 3. ++ to what everyone else said.
>>
>> There has been discussion around a future version of Facter allowing
>> for facts to be provided by executables in a certain directory, which
>> is about as far as I can see Python integration with Puppet going.
>
> Agreed. That'd be a useful feature and if we'd probably do it like
> Nagios plug-ins do - doesn't matter what the language is as long as
> they
> output data that the Facter API can parse into facts - Perl, Python,
> C,
> Rexx (*coughs*), etc.


This is something that I'm in total agreement on, it's just a question
of getting the time to do the work.

If anyone's interesting in taking up the torch, I'm glad to help come
up with the development plan. It's not nearly as complicated is it
might seem.

James and I had a brief discussion about the possibility of using non-
ruby plugins in Puppet, too, and I think it's feasible although not as
easy as Facter, of course, and not necessarily something you could get
straight to from where we are now. Once we've got the new, cleaner
internal DSL for resource type specification (the whole thread about
internal vs. external DSL I did a while back), we can migrate it to
the RAL, and it will bring with it a *much* cleaner model, and that
cleaner model will allow us to add some pluggability to the system.

Yes, I know this is mostly gibberish to most people, unfortunately -
the summary is that we're a ways away from it on Puppet but it's
something I'd like to be able to do and it's also something that our
current development plan will get us much closer to supporting.

--
You've got to take the bitter with the sour.
-- Samuel Goldwyn

Rob Chanter

unread,
Mar 3, 2009, 11:07:53 PM3/3/09
to puppet...@googlegroups.com
On Sat, Feb 28, 2009 at 4:30 PM, James Turnbull <ja...@lovedthanlost.net> wrote:
>
> Agreed. That'd be a useful feature and if we'd probably do it like
> Nagios plug-ins do - doesn't matter what the language is as long as they
> output data that the Facter API can parse into facts - Perl, Python, C,
> Rexx (*coughs*), etc.
>

I am *so* writing a fact in Rexx. Just one, probably "rexx_version".
Just watch me.

cheers
rob

mattim...@gmail.com

unread,
Mar 4, 2009, 5:44:00 AM3/4/09
to Puppet Users


On Mar 4, 3:56 am, Luke Kanies <l...@madstop.com> wrote:
>
> Not to nit-pick, but it's more that I just couldn't write in the  
> language.  I did try pretty hard, and have since successfully written  
> a bit in it (in Jython, actually), but I just could never turn my  
> ideas into code in Python.  And no, it wasn't the white space.
>

Without preusing the code base, how much of Puppet is RESTful these
days? I thought work was done in this area already. Wouldn't that
imply we could interface to those parts in any language?

/usr/bin/curl FTW!

--
Matthew Flanagan
http://wadofstuff.blogspot.com

Luke Kanies

unread,
Mar 4, 2009, 4:03:19 PM3/4/09
to puppet...@googlegroups.com


Much of Puppet's internals use the plugin interface that provides
RESTful behaviour (the mythical Indirector), but 0.25 will be the
first release where we actually use RESTful connections.

And yes, you can kind of use curl, as long as you can get it to speak
ssl, but at least initially, you'll mostly get yaml- or marshal-dumped
Ruby objects, not language-agnostic information.

It'll ship with support for adding things like json, but I don't want
to delay the release further trying to squeeze those in.

--
In theory, there is no difference between theory and practice; in
practice, there is. -- Chuck Reid

Reply all
Reply to author
Forward
0 new messages