Looks good, thanks Luke. -Blake On 8/27/07, Luke Kanies <luke at madstop.com> wrote:> > I''ve got a first version of a doc explaining how multiple environment > support will work in the next release: > > http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments > > As always, comments are appreciated. Even if you just don''t > understand what the doc says, please let me know. It''s clear that > the community is generally unhappy with the documentation I write, so > if you want me to get better at this I need your feedback. > > -- > The great aim of education is not knowledge but action. > -- Herbert Spencer > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > _______________________________________________ > Puppet-users mailing list > Puppet-users at madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.madstop.com/pipermail/puppet-users/attachments/20070827/483f4328/attachment.htm
I''ve got a first version of a doc explaining how multiple environment
support will work in the next release:
http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments
As always, comments are appreciated. Even if you just don''t
understand what the doc says, please let me know. It''s clear that
the community is generally unhappy with the documentation I write, so
if you want me to get better at this I need your feedback.
--
The great aim of education is not knowledge but action.
-- Herbert Spencer
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
On 8/27/07, Luke Kanies <luke at madstop.com> wrote:> I''ve got a first version of a doc explaining how multiple environment > support will work in the next release: > > http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments > > As always, comments are appreciated. Even if you just don''t > understand what the doc says, please let me know. It''s clear that > the community is generally unhappy with the documentation I write, so > if you want me to get better at this I need your feedback.I wouldn''t assume that at all Luke. While the Puppet documentation isn''t the best documentation I''ve read, it''s most certainly not the worst either, and has been more than sufficient for us to get up and running with it here. I quite like the way you''ve sketched out environments, just one slight query regarding these lines: "You can alternatively create an environment fact for the same purpose." "The environment is also available as $environment within your manifests, so you can use the same manifests everywhere and behave differently internally depending on the environment." Why would we want to create an environment fact if this is the case?
On Aug 27, 2007, at 10:28 PM, Nigel Kersten wrote:> > I wouldn''t assume that at all Luke. > > While the Puppet documentation isn''t the best documentation I''ve read, > it''s most certainly not the worst either, and has been more than > sufficient for us to get up and running with it here.Great, thank you for the positive feedback.> I quite like the way you''ve sketched out environments, just one slight > query regarding these lines: > > "You can alternatively create an environment fact for the same > purpose." > > "The environment is also available as $environment within your > manifests, so you can use the same manifests everywhere and behave > differently internally depending on the environment." > > Why would we want to create an environment fact if this is the case?It just provides you more flexibility in how the environment is determined. It could especially make a difference in node initialization -- you could have a generic fact set up to query a database or calculate the environment based on node name or IP address or something. Otherwise you have to generate your puppet.conf with the correct value in it before the host ever contacts the server, which could be difficult in some cases. -- Now and then an innocent man is sent to the legislature. --Kin Hubbard --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On 8/27/07, Luke Kanies <luke at madstop.com> wrote:> On Aug 27, 2007, at 10:28 PM, Nigel Kersten wrote: > > I quite like the way you''ve sketched out environments, just one slight > > query regarding these lines: > > > > "You can alternatively create an environment fact for the same > > purpose." > > > > "The environment is also available as $environment within your > > manifests, so you can use the same manifests everywhere and behave > > differently internally depending on the environment." > > > > Why would we want to create an environment fact if this is the case? > > It just provides you more flexibility in how the environment is > determined. > > It could especially make a difference in node initialization -- you > could have a generic fact set up to query a database or calculate the > environment based on node name or IP address or something. Otherwise > you have to generate your puppet.conf with the correct value in it > before the host ever contacts the server, which could be difficult in > some cases.doh. In that case I misinterpreted the first line (which was my fault for not reading it clearly), but it might be more obviously spelled out as something like: "This will inform the server which environment the client is in. Rather than specifying this statically in the config file, you could alternatively create a custom fact that set the client environment based upon some other client attribute or external data source." Just to ram it down the throat of people like me who skimmed over the brevity... but just a suggestion.
Luke Kanies wrote:> I''ve got a first version of a doc explaining how multiple environment > support will work in the next release: > > http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments > > As always, comments are appreciated. Even if you just don''t > understand what the doc says, please let me know. It''s clear that > the community is generally unhappy with the documentation I write, so > if you want me to get better at this I need your feedback.Very clean, very neat implementation. Also documentation was perfectly understandable and made the detail very clear. Regards James Turnbull _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 27 August 2007, Luke Kanies wrote:> I''ve got a first version of a doc explaining how multiple environment > support will work in the next release: > > http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments > > As always, comments are appreciated. Even if you just don''t > understand what the doc says, please let me know. It''s clear that > the community is generally unhappy with the documentation I write, so > if you want me to get better at this I need your feedback.Perhaps it''s just the accumulated brain-damage of years in IT, but I did understand what you wrote :) What I''m missing though, is a little paragraph about recommended usage (beyond the naming). Also, would "puppetd --environment=testing --noop" be a good idea on a production server? Regards, David - -- The primary freedom of open source is not the freedom from cost, but the free- dom to shape software to do what you want. This freedom is /never/ exercised without cost, but is available /at all/ only by accepting the very different costs associated with open source, costs not in money, but in time and effort. - -- http://www.schierer.org/~luke/log/20070710-1129/on-forks-and-forking -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG0+tv/Pp1N6Uzh0URArlxAKCBp9JzblE1lUFxpT9dxQP4Wp8FJACfZ4GS qQ4TJZ/Dtx6byfckXxY8HtQ=0Q1R -----END PGP SIGNATURE-----
On Aug 27, 2007, at 11:00 PM, Nigel Kersten wrote:> doh. In that case I misinterpreted the first line (which was my fault > for not reading it clearly), but it might be more obviously spelled > out as something like: > > "This will inform the server which environment the client is in. > Rather than specifying this statically in the config file, you could > alternatively create a custom fact that set the client environment > based upon some other client attribute or external data source." > > Just to ram it down the throat of people like me who skimmed over the > brevity... but just a suggestion.It being a wiki... Would you be willing to make this modification? Thanks. -- If computers get too powerful, we can organize them into a committee -- that will do them in. -- Bradley''s Bromide --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Aug 28, 2007, at 4:31 AM, David Schmitt wrote:> Perhaps it''s just the accumulated brain-damage of years in IT, but > I did > understand what you wrote :) > > What I''m missing though, is a little paragraph about recommended > usage (beyond > the naming). > > Also, would "puppetd --environment=testing --noop" be a good idea on a > production server?The only way I can think this would be bad is if the next connection failed, because this connection would cache the testing configuration. If the next connection attempt then failed, it would use this cached configuration. So, if you do this, I recommend you do something like --localconfig / dev/null to make sure it does not cache it somewhere permanent. -- Whenever I hear anyone arguing for slavery, I feel a strong impulse to see it tried on him personally. -- Abraham Lincoln --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On 8/28/07, Luke Kanies <luke at madstop.com> wrote:> It being a wiki... Would you be willing to make this modification?of course. just thought I''d see if there were howls of protest....
On Mon, 2007-08-27 at 11:18 -0500, Luke Kanies wrote:> I''ve got a first version of a doc explaining how multiple environment > support will work in the next release: > > http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironmentsVery nice. Like that a lot; I think it will go nicely with checking different branches of your module SCM out to different locations. The one nit I have with it is that there is no environment by default - why not always have a default environment and call that cunningly ''main'' ? That way, there''s always an environment, and going to more of them is a logical extension of the default setup. David
On Sep 14, 2007, at 8:30 PM, David Lutterkort wrote:> Very nice. Like that a lot; I think it will go nicely with checking > different branches of your module SCM out to different locations. > > The one nit I have with it is that there is no environment by > default - > why not always have a default environment and call that cunningly > ''main'' ? That way, there''s always an environment, and going to more of > them is a logical extension of the default setup.I''m willing to have a default environment, although I''m more likely to call it ''dev'' or ''development''. We need to keep ''main'' separate because you''ll always want a way to set a value in all environments and on all executables, and ''main'' is the only way to do that. -- Think twice before you speak, and then you may be able to say something more insulting than if you spoke right out at once. - Evan Esar --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com