On Thursday, June 14, 2012 6:39:36 PM UTC-5, tas wrote:
>
> Dear Ygor,
>
> Thank you for the guidance.
> I didn't know we have to specify one... almost every single tutorial I
> visit didn't mention it :( bad...
>
> http://pratikamin.wordpress.com/2011/05/24/turning-a-blueprint-puppet-recipe-into-a-puppet-deployment/
>
Do you mean like this section from that article?
4. Edit /etc/puppet/manifests/site.pp, this is the default file puppet
looks for, and loads first. For now you probably want to do it in here, but
later put it into node.pp or something(assuming client name is
blogtest.test.com)
node vpsblueprint {
include vps_blueprint
}
node 'blogtest.test.com' inherits vpsblueprint{
}
This tells puppet for the client connecting with the hostname
blogtest.test.com it should use the vpsblueprint node, which includes the
vps_blueprint module.
I must say that I have not noticed tutorials to be systematically deficient
in that regard. Puppetlabs's own cover the topic, and I don't recall
seeing any full-blown tutorials that miss it. More narrowly-focused
tutorials might omit it where it would be out of scope, of course.
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/-/dprdzL7sH8cJ.
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.
