Puppet will not do anything you don't tell it to do. Try think of it
more along the lines of your modules and manifests describing how a
server should be and only how it should be. So if you don't tell it
NOT to be something, it's just going to ignore anything else that
exists on the system - this is why you haven't needed to tell Puppet
to install the packages kernel, and core-utils, it's not going to undo
anything that already exists that it doesn't know about otherwise
Puppet manifests would be massively redundant :)
A lot of people follow the convention of using an inherited class like
apache::disabled that shuts down everthing that the class apache does:
class apache {
package { "httpd": ensure => present }
service { "httpd": ensure => running }
}
class apache::disabled inherits apache {
Package["httpd"] { ensure => absent }
Service["httpd"] { ensure => stopped }
}
node never_be_a_web_server {
include apache::disabled
}
On Mar 2, 4:42 am, Luis Miguel Silva
<[email protected]> wrote:
> Dear all,
>
> I finally managed to load an extra module (apache) via dashboard but
> i'm having trouble removing it?
> My expectation was that, once i removed the class from the node
> (stopped including it), Puppet would call some sort of deprovisioning
> mechanism that would remove the class (so, in my case, when i stopped
> including the apache class in my node, puppet would remove apache from
> my node).
>
> According to my tests, that did not happen (Apache is still up and running).
> What are the best practices to remove a module when we no longer need it?
>
> Thanks,
> Luis
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users?hl=en.
