May somebody has answer ...
How can I ensure that certain classes get executed on the client side
before the other ones do?
Have a look on the example:
class AA
case $operatingsystem {
"redhat": { include AA::do-first }
default: {}
}
include AA::software
include AA::desktop
}
class AA::do-first {
# do an rhn_register
exec { "register-system":
command => "rm -f /etc/sysconfig/rhn/systemid ; rhnreg_ks
--force --serverUrl=https://$rhn_server/XMLRPC
--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
--activationkey=$activation_key",
logoutput => true,
unless => "/usr/sbin/rhn_check",
tag => register-system,
}
}
class AA::software {
# do someting after AA::do-first
}
class AA::desktop {
# do something after AA::do-first
}
For an Redhat system the resource(s) in AA::do-first should run before
the resource(s) in AA::software & AA::desktop.
Is their an simple way for that?
An other wish would be: If Exec "register-system" fails, puppet should
stop his execution without do go through the class AA::software &
AA::desktop.
Thanks for the help!
Philipp
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~----------~----~----~----~------~----~------~--~---
