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-----
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
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
- --
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.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJqMwC9hTGvAxC30ARAuOsAKCmzaXxxNdIqcuupKpvGpHOWuIY8QCeKUFg
BMcyS3AFsWyegTaLc5rUZUI=
=V2Gi
-----END PGP SIGNATURE-----
Evan
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
- --
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.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJqbfC9hTGvAxC30ARAuqVAKCdlG3GZTH5cVikxaJzCHc8m52UhQCdGCoo
6KH0crADCqDfcEqtx0XDFWg=
=/Iqw
-----END PGP SIGNATURE-----
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
>
> -----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
I am *so* writing a fact in Rexx. Just one, probably "rexx_version".
Just watch me.
cheers
rob
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