1
edit
Changes
→Release 0.3
4) start the client
<pre>
#service puppet start
</pre>
this create the necessary certificate itself for the secure communication.
5) In puppetmaster issue the folling command
<pre>
#puppetca --list
</pre>
it will the client that need to be signed.
6) In the puppetmaster issue the folling command to sign the above listed client.
<pre>
#puppetca --sign cdot-guru-1-2
</pre>
this will sign the certificate.
For example:
<pre>
'''file {“/etc/resolv.conf”:
}'''
</pre>
The resource type is file, the resource type tells the puppet what type of the resource is managed.
For example if you want to manage the “ypbind” in the node1
<pre>
node ‘node1.example.com’{
}
</pre>
This is configuration is applied to the node1.exapmle.com. Imagine if there are 100 of node to be managed, this configuration has to done again and again. This does not scale well. To reduce this configuration effort in every nodes, wed can group this in to a class instead and then include the class with each node.
For example:
<pre>
# /etc/puppet/manifest/classes/yp.pp
}
</pre>
<pre>
# /etc/puppet/manifest.pp
include yp::client
}
</pre>
what I have done is that I group the recourses type into class. Then I call the class in to each node. By doing this eliminate the configuring each resources in each node. Just call the class into each node.
But sill it cab be made to scale more. Think if there are few more classes to be applied then each classes has to be called into. For example,
<pre>
# /etc/puppet/manifest/site.pp
}
</pre>
This again brings little bit more configuration over head. There to over come from this we can do it such a way,
<pre>
#/etc/puppet/manifest/group/desktop.pp
}
</pre>
<pre>
#/etc/puppet/manifest/site.pp
include desktop
}
</pre>
What I did was group the classes into another class and apply that group into the nodes. This configuration method pretty scale well.
