Hello folks, I''ve blended/updated the Glossary of Terms (<http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms>). It seems the definition of "manifests" is a bit different amongst members. Some people consider a "manifest" to be a configuration file written in puppet, e.g. any .pp file. But at my organization, we''ve considered the totality of configurations settings (i.e. all the resources with their parameters, etc) to be the "manifest" for a server. What makes more sense to people? -- DK -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 17 March 2007 00:04, Digant C Kasundra wrote:> Hello folks, > > I''ve blended/updated the Glossary of Terms > (<http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms>). It seems > the definition of "manifests" is a bit different amongst members. > > Some people consider a "manifest" to be a configuration file written in > puppet, e.g. any .pp file. But at my organization, we''ve considered the > totality of configurations settings (i.e. all the resources with their > parameters, etc) to be the "manifest" for a server. What makes more sense > to people?I think with the advent of modules (see David Lutterkort''s patch and ModuleOrganization on the wiki) your use of manifest will be superseded by "module", leaving manifest for the puppet.pp source. Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF+9KG/Pp1N6Uzh0URArmgAKCZNlYFKDaPcee4VTvA5s4Icu80CACgm5MT +Y/VPe4AnSUxFsDgDsFGCH0=ggiE -----END PGP SIGNATURE-----
--On Saturday, March 17, 2007 12:35 PM +0100 David Schmitt <david@schmitt.edv-bus.at> wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Saturday 17 March 2007 00:04, Digant C Kasundra wrote: >> Hello folks, >> >> I''ve blended/updated the Glossary of Terms >> (<http://reductivelabs.com/trac/puppet/wiki/GlossaryOfTerms>). It seems >> the definition of "manifests" is a bit different amongst members. >> >> Some people consider a "manifest" to be a configuration file written in >> puppet, e.g. any .pp file. But at my organization, we''ve considered the >> totality of configurations settings (i.e. all the resources with their >> parameters, etc) to be the "manifest" for a server. What makes more >> sense to people? > > I think with the advent of modules (see David Lutterkort''s patch and > ModuleOrganization on the wiki) your use of manifest will be superseded > by "module", leaving manifest for the puppet.pp source.I think David Lutterkort''s use of the word module is pretty compatible with the way we are using it, but to me the use of the word manifest still doesn''t make sense. To me, a manifest, such as for a cargo ship, is the list of all cargo. To me, the word manifest in the module doc and in other places is actually meant to describe only a very small component of what a servers total configuration would be composed of. I think another term would be better in these cases. For instance, in the Module Organzation, "manifest" is really the "puppet source code" part of the overall module. In fact, it isn''t a manifest but rather the code that describes how the templates and files are to be used and what other resource types belong with this particular module. To liken it to the ship analogy, this might be the ingredients for ship''s cook along with the recipes he will use, but it is only a small piece of the entire ship''s manifest, which also includes the other cargo on the ship.
On Mar 18, 2007, at 5:46 PM, Digant C Kasundra wrote:> > For instance, in the Module Organzation, "manifest" is really the > "puppet > source code" part of the overall module. In fact, it isn''t a > manifest but > rather the code that describes how the templates and files are to > be used > and what other resource types belong with this particular module. > To liken > it to the ship analogy, this might be the ingredients for ship''s > cook along > with the recipes he will use, but it is only a small piece of the > entire > ship''s manifest, which also includes the other cargo on the ship.I enjoy my use of the word ''manifest'' here, and am hesitant to give it up because I think it both sets Puppet apart a bit and because it makes it clear we''re not talking about executable code here, but I''m willing to consider other options. I don''t think the standard choices (mostly "script" and "configuration") are very good choices, though, because they imply things that aren''t true. Do you have a better choice, so you can repurpose ''manifest'' in this way? -- Due to circumstances beyond your control, you are master of your fate and captain of your soul. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 18 March 2007 23:46, Digant C Kasundra wrote:> I think David Lutterkort''s use of the word module is pretty compatible with > the way we are using it, but to me the use of the word manifest still > doesn''t make sense. To me, a manifest, such as for a cargo ship, is the > list of all cargo. To me, the word manifest in the module doc and in other > places is actually meant to describe only a very small component of what a > servers total configuration would be composed of. I think another term > would be better in these cases. > > For instance, in the Module Organzation, "manifest" is really the "puppet > source code" part of the overall module. In fact, it isn''t a manifest but > rather the code that describes how the templates and files are to be used > and what other resource types belong with this particular module. To liken > it to the ship analogy, this might be the ingredients for ship''s cook along > with the recipes he will use, but it is only a small piece of the entire > ship''s manifest, which also includes the other cargo on the ship.I equate "resources on the target" = cargo and "puppet source" = manifest, the document which specifies which cargo is where. That is the beauty of puppet''s declarative style. If it were more like a shell script, I would agree, that recipe or something similar would be more fitting. But as long as I can take a (compiled) manifest and check off, that everything (on the node) is where it belongs, manifest is a good word for me. English is not my native language and Exec exists, so of course I might be totally off too. Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/mNW/Pp1N6Uzh0URAiDLAJ9rpCXayuIyMUx/wPR3GKYCcP0cygCeNdOc B+nOq2EK33sLJzL/aK6x0Ck=1zy4 -----END PGP SIGNATURE-----
--On Sunday, March 18, 2007 7:42 PM -0500 Luke Kanies <luke@madstop.com> wrote:> On Mar 18, 2007, at 5:46 PM, Digant C Kasundra wrote: >> >> For instance, in the Module Organzation, "manifest" is really the >> "puppet >> source code" part of the overall module. In fact, it isn''t a >> manifest but >> rather the code that describes how the templates and files are to >> be used >> and what other resource types belong with this particular module. >> To liken >> it to the ship analogy, this might be the ingredients for ship''s >> cook along >> with the recipes he will use, but it is only a small piece of the >> entire >> ship''s manifest, which also includes the other cargo on the ship. > > I enjoy my use of the word ''manifest'' here, and am hesitant to give > it up because I think it both sets Puppet apart a bit and because it > makes it clear we''re not talking about executable code here, but I''m > willing to consider other options. > > Do you have a better choice, so you can repurpose ''manifest'' in this > way?I think we''re forgetting the other option which is to find a better term for "the complete totality of stuff on a server." Perhaps that is better candidate for terminology change. Ideas on that? I guess "total manifest" would work if nothing else exists. -- DK
--On Monday, March 19, 2007 11:17 AM +0100 David Schmitt <david@schmitt.edv-bus.at> wrote:> I equate "resources on the target" = cargo and "puppet source" > manifest, the document which specifies which cargo is where. That is the > beauty of puppet''s declarative style. If it were more like a shell > script, I would agree, that recipe or something similar would be more > fitting. But as long as I can take a (compiled) manifest and check off, > that everything (on the node) is where it belongs, manifest is a good > word for me.When you put it that way, it does make very good sense. So manifest should stay the way it is, and I need a better term for "totality of configuration settings and actions that describe a given system."
On Mar 19, 2007, at 10:30 AM, Digant C Kasundra wrote:> > > --On Monday, March 19, 2007 11:17 AM +0100 David Schmitt > <david@schmitt.edv-bus.at> wrote: > >> I equate "resources on the target" = cargo and "puppet source" >> manifest, the document which specifies which cargo is where. That >> is the >> beauty of puppet''s declarative style. If it were more like a shell >> script, I would agree, that recipe or something similar would be >> more >> fitting. But as long as I can take a (compiled) manifest and >> check off, >> that everything (on the node) is where it belongs, manifest is a >> good >> word for me. > > When you put it that way, it does make very good sense. So > manifest should > stay the way it is, and I need a better term for "totality of > configuration > settings and actions that describe a given system."I like "codex", mainly because it''s short and unusual. I also like "catalog/catalogue". -Blake
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 19 March 2007 18:30, Digant C Kasundra wrote:> --On Monday, March 19, 2007 11:17 AM +0100 David Schmitt > > <david@schmitt.edv-bus.at> wrote: > > I equate "resources on the target" = cargo and "puppet source" > > manifest, the document which specifies which cargo is where. That is the > > beauty of puppet''s declarative style. If it were more like a shell > > script, I would agree, that recipe or something similar would be more > > fitting. But as long as I can take a (compiled) manifest and check off, > > that everything (on the node) is where it belongs, manifest is a good > > word for me. > > When you put it that way, it does make very good sense. So manifest should > stay the way it is, and I need a better term for "totality of configuration > settings and actions that describe a given system."For the current-state-of-a-server I''d say "current system configuration" which is something quite unrelated to puppet. For the bits which are read by puppetmasterd: files, templates, manifests, config files. Sets of those: modules. The tree of resources that is referenced by a particular node-snippet in site.pp? Something like "target-set of resources," "target configuration"? Note the missing "system" since puppet doesn''t (yet) aim to configure the totality of a system. Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/xOq/Pp1N6Uzh0URAuqMAJ9sk7s8+ZXCpeeyb2d5tUQIxUuVpgCeN7q1 Xk+isATwp9e4NjIUU6aM0a8=O2OG -----END PGP SIGNATURE-----
--On Monday, March 19, 2007 12:08 PM -0700 Blake Barnett <shadoi@nanovoid.com> wrote:> > On Mar 19, 2007, at 10:30 AM, Digant C Kasundra wrote: > >> When you put it that way, it does make very good sense. So >> manifest should >> stay the way it is, and I need a better term for "totality of >> configuration >> settings and actions that describe a given system." > > I like "codex", mainly because it''s short and unusual. I also like > "catalog/catalogue". >I like catalogue. I vote for that. Anyone else with an opinion on this?
--On Monday, March 19, 2007 11:50 PM +0100 David Schmitt <david@schmitt.edv-bus.at> wrote:> The tree of resources that is referenced by a particular node-snippet in > site.pp? Something like "target-set of resources," "target > configuration"? Note the missing "system" since puppet doesn''t (yet) aim > to configure the totality of a system.Those work but aren''t as easy to use in a sentence as "catalogue," IMHO. If I wanted to train someone and say "when you adding a User type to a node makes sure the user becomes part of the catalogue for that server," I think it reads pretty good. "target-set of resources" sounds fine too but it uses words that individually already have a definition in puppet (except for set). "catalogue" is a complete and wholly unused word so as to minimize confusion as to its context. But part of this effort requires buy-in from the user community so I want to know what you and others think and hopefully form some consensus. -- DK
On Mar 19, 2007, at 7:37 PM, Digant C Kasundra wrote:> > Those work but aren''t as easy to use in a sentence as "catalogue," > IMHO. > If I wanted to train someone and say "when you adding a User type > to a node > makes sure the user becomes part of the catalogue for that server," > I think > it reads pretty good. "target-set of resources" sounds fine too > but it > uses words that individually already have a definition in puppet > (except > for set). "catalogue" is a complete and wholly unused word so as to > minimize confusion as to its context.I like catalogue (or the Americanized ''catalog'', whichever), also.> But part of this effort requires buy-in from the user community so > I want > to know what you and others think and hopefully form some consensus.It''s surprising how quickly good terminology spreads, especially if all of us who know better do our best to be specific. I know I''ve felt a huge amount of relief ever since we settled on ''resource'', and ''property'' has recently been quite enjoyable. -- I wanna hang a map of the world in my house. Then I''m gonna put pins into all the locations that I''ve traveled to. But first, I''m gonna have to travel to the top two corners of the map so it won''t fall down. -- Mitch Hedberg --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> I know I''ve felt a huge amount of relief ever since we settled on > ''resource'', and ''property'' has recently been quite enjoyable.I don''t have a definition for property. Does the def of resource look okay?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 20 March 2007 01:37, Digant C Kasundra wrote:> --On Monday, March 19, 2007 11:50 PM +0100 David Schmitt > > <david@schmitt.edv-bus.at> wrote: > > The tree of resources that is referenced by a particular node-snippet in > > site.pp? Something like "target-set of resources," "target > > configuration"? Note the missing "system" since puppet doesn''t (yet) aim > > to configure the totality of a system. > > Those work but aren''t as easy to use in a sentence as "catalogue," IMHO. > If I wanted to train someone and say "when you adding a User type to a node > makes sure the user becomes part of the catalogue for that server," I think > it reads pretty good. "target-set of resources" sounds fine too but it > uses words that individually already have a definition in puppet (except > for set). "catalogue" is a complete and wholly unused word so as to > minimize confusion as to its context. > > But part of this effort requires buy-in from the user community so I want > to know what you and others think and hopefully form some consensus.My main gripe with catalogue, is that someone usually picks a few things from a catalogue - usually to order/receive. I can''t really see that when talking about the "tree of resources that is referenced by a particular node-snippet". What if catalogue were defined as "everything on the MODULE_PATH"? Then the node-mapper would be e.g. "an agent who chooses components from the the catalogue which should be applied to the client node". That sounds better. Is it still what you were searching a word for? Regards, David - -- - - hallo... wie gehts heute? - - *hust* gut *rotz* *keuch* - - gott sei dank kommunizieren wir über ein septisches medium ;) -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF/7aJ/Pp1N6Uzh0URAsvyAKCV444n7PK8Sg+r04kvmr/EPS+F2QCdE1eD yEBQNUsmO+yAWPFv9WOZ7/M=XVSW -----END PGP SIGNATURE-----
Digant C Kasundra wrote:> > --On Monday, March 19, 2007 12:08 PM -0700 Blake Barnett > <shadoi@nanovoid.com> wrote: > >> On Mar 19, 2007, at 10:30 AM, Digant C Kasundra wrote: >> >>> When you put it that way, it does make very good sense. So >>> manifest should >>> stay the way it is, and I need a better term for "totality of >>> configuration >>> settings and actions that describe a given system." >> I like "codex", mainly because it''s short and unusual. I also like >> "catalog/catalogue".> I like catalogue. I vote for that. Anyone else with an opinion on this?I tend to use the phrases "The current state of a machine" and "The intended state of a machine", as they seem to accurately convey the intent. Of course, this state can include things that aren''t described by some configuration management system. ***************************************************************************** This email and any attachments are strictly confidential and intended for the addressee(s) only. If this email has been sent to you in error, please let us know by forwarding it to us at support@scansafe.com. Neither ScanSafe nor its directors, officers or employees accepts any liability for the accuracy or completeness of this email. Unless expressly stated to the contrary, no contracts may be concluded on behalf of ScanSafe by means of e-mail communication. *****************************************************************************
On Mar 20, 2007, at 3:25 AM, David Schmitt wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tuesday 20 March 2007 01:37, Digant C Kasundra wrote: >> --On Monday, March 19, 2007 11:50 PM +0100 David Schmitt >> >> <david@schmitt.edv-bus.at> wrote: >>> The tree of resources that is referenced by a particular node- >>> snippet in >>> site.pp? Something like "target-set of resources," "target >>> configuration"? Note the missing "system" since puppet doesn''t >>> (yet) aim >>> to configure the totality of a system. >> >> Those work but aren''t as easy to use in a sentence as "catalogue," >> IMHO. >> If I wanted to train someone and say "when you adding a User type >> to a node >> makes sure the user becomes part of the catalogue for that >> server," I think >> it reads pretty good. "target-set of resources" sounds fine too >> but it >> uses words that individually already have a definition in puppet >> (except >> for set). "catalogue" is a complete and wholly unused word so as to >> minimize confusion as to its context. >> >> But part of this effort requires buy-in from the user community so >> I want >> to know what you and others think and hopefully form some consensus. > > My main gripe with catalogue, is that someone usually picks a few > things from > a catalogue - usually to order/receive.<snip> A catalogue is the totality of a stores'' offerings. Think of it from the business owner perspective, not the shopper. :) -Blake
--On Tuesday, March 20, 2007 11:25 AM +0100 David Schmitt <david@schmitt.edv-bus.at> wrote:> My main gripe with catalogue, is that someone usually picks a few things > from a catalogue - usually to order/receive. I can''t really see that > when talking about the "tree of resources that is referenced by a > particular node-snippet". What if catalogue were defined as "everything > on the MODULE_PATH"? Then the node-mapper would be e.g. "an agent who > chooses components from the the catalogue which should be applied to the > client node". That sounds better. Is it still what you were searching a > word for?That''s not quite the term I''m looking to define. I''m trying to create a term that means "everything in classes.txt and localconfig.yaml." So, out of all the modules and files and whatnots that are available, the catalog for a server is the list of those thing that it has. It is "a complete list of things" that belong as part of that server, not the complete list of things available and defined in the Puppet Master. Does that make sense?
--On Tuesday, March 20, 2007 11:06 AM +0000 Ceri Storey <cez@necrofish.org.uk> wrote:> I tend to use the phrases "The current state of a machine" and "The > intended state of a machine", as they seem to accurately convey the > intent. Of course, this state can include things that aren''t described > by some configuration management system.Phrases are great but sometimes, it is better to have a specific term to represent that phrase and since there is much in the puppet language that determines does or does not go into the intended state of a machine, I think a term would be helpful here. Any ideas?
Hey All,
Just updated puppet from 0.22.1 -> 0.22.2
when i run puppetd --server localhost --listen --debug
i get the following
/usr/local/lib/site_ruby/1.8/puppet/util/config.rb:29:in `[]'':
Undefined configuration parameter ''authconfig'' (ArgumentError)
from /usr/local/lib/site_ruby/1.8/puppet.rb:83:in `[]''
from /usr/bin/puppetd:360
all that is in my /etc/puppet/puppetd.conf is the following:
[puppetd]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run
listen = true
server = citadel.brennanit.net.au
[puppet]
confdir = /etc/puppet
this does not occur when dropping the --listen option
Cheers
Brendan
Brendan Beveridge
Managed Services Consultant
Direct 02 8235 9593
Mobile 0434 077 934
Email Brendan.Beveridge@brennanit.com.au
Sydney - Melbourne - Brisbane
| Phone | 02 8235 9595 | Fax | 02 8235 9594 | Web : http://www.brennanit.com.au
"Introducing our new brand - Brennan." Click here to find out more.
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
On Mar 26, 2007, at 7:04 AM, Brendan Beveridge wrote:> Hey All, > > Just updated puppet from 0.22.1 -> 0.22.2 > > when i run puppetd --server localhost --listen --debug > > i get the following > > /usr/local/lib/site_ruby/1.8/puppet/util/config.rb:29:in `[]'': > Undefined configuration parameter ''authconfig'' (ArgumentError) > from /usr/local/lib/site_ruby/1.8/puppet.rb:83:in `[]'' > from /usr/bin/puppetd:360 >This has been fixed in svn and will be released in a small bugfix release early this week. -- "In theory, there is no difference between theory and practice; In practice, there is." -- Chuck Reid --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com