On Tuesday, August 7, 2012 9:21:10 AM UTC-5, TORO wrote:
>
>
> Am Dienstag, 7. August 2012 15:08:38 UTC+2 schrieb jcbollinger:
>>
>>
>>
>> On Tuesday, August 7, 2012 2:47:05 AM UTC-5, TORO wrote:
>>>
>>> Yes you are right , :
>>>
>>>> b) the class itself is not being included properly elsewhere
>>>
>>> as it is not listed i
>>> /var/lib/puppet/state/classes.txt
>>>
>>> And Yes you are right , I should have attached my init.pp and oel.pp see
>>> now below:
>>>
>>
>> No, if the the node's catalog compiles correctly, but the class is not
>> included, then the problem is not with the class's own manifest(s). Ken
>> described the most common ways in which class 'itrs_probe' could be
>> assigned to your node; are you using one of those?
>>
>>
>> John
>>
>> He John ,
>
> Thanks for Your comment. But now I´m totally lost.
>
> I have to admit, the puppet server was already set up and working with a
> bunch of modules when I take over ( I have not set puppet up myself....and
> do not have many experience with Puppet !)
>
> So I had expected to create new path under modules e.g......testing
> /modules/itrs_prob/ { files, templates, manifests} and then put a init.pp
> and the oel.pp into manifests should let puppet deploy my stuff.
>
> This seems not to be the case.
>
> For testing I made again a new modul (/dummy/ { files, templates,
> manifests} and also put an init.pp in to manifests .
>
> (this init pp)
>
> class dummy () {
>
> notify { 'inside dummy': }
>
> }
>
> I had expected to see something like this ...what I have tested on a
> other already working modul ... it additionally send the notify ....
>
> notice: /Stage[main]/Altiris_client/Notify[inside altiris_client]/message:
> current_value absent, should be inside altiris_client (noop)
>
> But the notify for dummy does not appear ...
>
> How do I add my new modules to get deploy ... ( where dummy is not
> required it does nothing ... but my itrs_probe needed)
>
What you are missing is that Puppet does not automatically deploy all
available modules to all nodes. It must be told which classes of which
modules to assign to each node. This is a good thing, for otherwise every
node would have to be configured the same way.
The assignments of classes to nodes may appear, either at top level or in a
'node' declaration block matching the target node, in the site-wide root
manifest "site.pp" or a manifest 'import'ed directly or indirectly by it.
Ken described how those might look. Alternatively, Puppet may assign
classes to nodes based on the output of an "external node classifier" (ENC)
program that someone set up for your site. Additionally, classes may add
other classes (as your its_probe class does), provided they themselves are
assigned to the target node by one of the available means.
I can't tell you exactly what to do because I can't tell what mode(s) of
class assignment your site is using, nor which of your nodes are supposed
to get the classes you have created.
I urge you to invest some time in learning at least the fundamentals of
your tools (Puppet, in this case). Puppet has on-line documentation and
tools that will carry you a long way:
http://docs.puppetlabs.com/#puppetpuppet. I would recommend either the
Learning Puppet series or the Language Guide (or both). The former may be
a bit more accessible, but if you're up to it then the latter may be more
comprehensive.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/m9Bx-BT-wgcJ.
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.
