On Wed, Apr 14, 2010 at 12: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)
I don't even know what pi does :-P "puppet ca" should be "puppet cert" or "puppet ssl" "puppet server" should have an alias "puppet master" if we are transitioning the terminology. I don't mind "puppet server", but people will think "master" for awhile. "puppet run" has always bothered me, but I don't have a better term for it. "puppet main" sucks. I like "puppet apply" better, as suggested by someone else. "puppet sa" for "puppet standalone" ? "puppet agent" is excellent. Should probably have an alias "puppet client" --Paul -- 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.
