Douglas Garstang <doug.garst...@gmail.com> writes:
> On Thu, Apr 15, 2010 at 8:44 AM, Jim Bala <usr...@gmail.com> wrote:
>> On Apr 15, 2010, at 1:30 AM, Mayank wrote:
>>
>>> I'm trying to manage some hosts using a single puppetmaster. I don't know
>>> why but puppet on clients seems to be executing the recipes hosted on
>>> puppetmaster in a random order which is breaking apart dependencies and
>>> resulting in a failed run of puppet for first time.
[...]
>>> package {"ruby-devel": ensure=>latest}
>>> package {"rubygems": ensure=>latest}
>>> exec {"install-mysql-gem":
>>> command=>'gem install mysql',
>>> path=>"/bin:/usr/bin:/usr/sbin:/sbin",
>>> require=>[ Package["ruby-devel"], Package["rubygems"]]
>>> }
>>>
>>> Now in many cases puppet tries to execute Exec["install-mysql-gem"]
>>> before Package["ruby-devel"] or Package["rubygems"] or both.
...if you specify the 'require' in your 'exec', and puppet tries to run it
before the packages are installed you have found a puppet bug.
I strongly suspect from ...
>>> Is there a way that I can ensure that puppet renders the file in order the
>>> script is written ?
... this that you don't have that dependency, however, and are looking for a
shortcut way to specify the dependencies through ordering of the input file.
[...]
> Keep at it. You'll get it all working with requires=> eventually. It will
> take forever, your head will hurt, and by the time your done, you'll have a
> god-aweful dependency mess that will make you totally afraid to touch any of
> it ever again, but you'll get it eventually if you keep at it! I did!
...and here I would have to say that, Doug, you are probably getting something
wrong somewhere if the dependencies in your system setup are that complex.[1]
Generally, your dependency chains shouldn't be enormously complex or deep in
puppet, and there are several tricks that make it easy to express complex
dependencies quickly.
One of the big ones is a Class dependency:
# Shouldn't I be using the OS package for this?
exec { "install-mysql-gem":
command => "/sbin/do-magic",
require => Class["ruby"]
}
Then, inside class ruby you install the dependent packages:
class ruby { package ["ruby-devel", "rubygems"]: ensure => latest }
That ensures that *all* the stuff in class 'ruby' is done before the exec for
your gems. Nice, short, and encapsulated.
Then, if you build appropriate classes you can have very short, specific
requirements that can express complex — and transparently changing —
requirements through your codebase.
(For example: using the 'class ruby' structure you can easily implement the
Debian version of it, and the mysql gem thing doesn't need change at all.)
Regards,
Daniel
Footnotes:
[1] ...that, or maybe you work somewhere that does have enormously complex
dependency sequences across your network, and they cannot be simplified
in any way including changing the network. ;)
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
