On Apr 14, 2010, at 12:16 PM, Stéphan Gorget wrote:
On Wed, Apr 14, 2010 at 9:07 PM, Jesse Wolfe <[email protected]>
wrote:
the new puppet single-executable is in master, but I think the names
of the commands should be up for discussion. These are something
that we may have to live with for a long time.
Here's what's currently in master:
bin/filebucket => puppet filebucket
bin/pi => puppet pi
bin/puppetdoc => puppet doc
sbin/puppetca => puppet ca
sbin/puppetmasterd => puppet server
sbin/puppetrun => puppet run
bin/puppet => puppet main
bin/ralsh => puppet resource
sbin/puppetd => puppet agent
sbin/puppetqd => puppet queue
Here's my commentary:
bin/pi => puppet pi (what does "i" stand for, anyway?)
sbin/puppetmasterd => puppet server (I'd rather keep the "master"
jargon)
bin/puppet => puppet main (doesn't seem very main to me.
"exec"? "do"?)
sbin/puppetd => puppet agent (is "agent" the jargon we use in
training? I can't remember)
Why don't we merge puppet and puppetd and use sthg like --local
instead ?
In general you need to provide some code for puppet to apply, which
isn't the case with puppetd. Also, there'll basically be an
assumption about both: puppetd will need to run as root, it'll
maintain a catalog, it needs auth credentials, and plenty more. In
contrast, puppet should always be able to run as a normal user, should
have little if any state, and probably doesn't need certificates or
any sense of membership to a network.
--
Discovery consists of seeing what everybody has seen and thinking what
nobody has thought. -- Albert Szent-Gyorgyi
---------------------------------------------------------------------
Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
