Puppet is a configuration Management tool, used for managing configuration of systems systematically. It keeps a historical record of state of systems properly.\u00a0 Puppet used pull methodology where nodes request configuration details from a server. It works on a Master and Slave environment. It\u00a0helps system administrators automate the provisioning, configuration, and management of a server infrastructure<\/p>\n
The architecture\u00a0used is where the client\/slave node contacts the server\/Master node and supplies few information about the client. The server verifies the records, creates a catalog, a document that tells the desired configuration of that client node, and updates the client node about the configurations to be used. Then the client updates the server with the status of configuration.<\/p>\n
Installing puppet master server<\/strong><\/p>\n Installing puppet agents in client hosts<\/strong><\/p>\n Starting the services:<\/strong><\/p>\n The command “puppet agent –test<\/strong><\/em>” when executed on a puppet client will communicate with the server\u00a0and apply the main manifest.<\/p>\n Configuring puppet server to create a file named <\/strong>\/usr\/local\/sbin\/puppetsimple.sh<\/em>\u00a0<\/em>and install<\/strong>\u00a0<\/strong>apache webserver\u00a0<\/em>in the client<\/strong><\/p>\n class toolbox {<\/em> class apache {<\/em> include apache<\/em> <\/p>\n Puppet master gathers facts about its nodes with a tool called facter<\/strong><\/em>, which by default, gathers information such as OS, hostnames, IP addresses, SSH keys, etc. This info the server gets from the client node can in-turn be used to configure parameters such as IP, hostname, etc in the configurations for the client.<\/p>\n The puppet agent when connects and checks with the puppet master, it will send facts about itself to the master, and pull a current catalog (a compiled list of resources and their desired states that are relevant to the agent, determined by the main manifest). Then the agent node will attempt to make the appropriate changes to achieve its desired state.<\/p>\n Puppet programs are called manifests, composed of puppet code,\u00a0written in a “.pp<\/strong><\/em>” file. The default main manifest is site.pp<\/strong><\/em><\/p>\n Retrieving new instructions from the puppet master that will create the file<\/strong><\/p>\n <\/p>\n Defining class to add a user named shijuv<\/strong><\/p>\n class addmyuser{<\/em><\/p>\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 user {‘shijuv’:<\/em> Defining class to delete a user<\/strong> \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 user {‘shijuv’:<\/em> <\/p>\n Transferring files from the Puppet File Server<\/strong><\/p>\n file { “\/tmp\/sample.txt”:<\/em> \u00a0 \u00a0 #NOTE: The folder named files is deliberately removed from source parameter<\/em> Puppet automatically serves PLUGINS and FILES FROM MODULES: anything in <module name>\/files\/<file name> is available to authenticated nodes at puppet:\/\/\/modules\/<module name>\/<file name>. You do not need to edit this file to enable this.<\/em><\/p>\n Default configuration for nodes not defined specifically:<\/p>\n When a client node contacts the puppet server, if there are no xxxx for the node, the node will apply all condifuration defines in “node default {}<\/strong><\/em>” in\u00a0\/etc\/puppet\/manifests\/site.pp<\/em><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"\n
\nInstall vmware tools if the host is a vm running on ESX<\/li>\n
\n#] rpm -ivh http:\/\/yum.puppetlabs.com\/puppetlabs-release-el-7.noarch.rpm<\/em><\/strong>
\n#] yum install puppet-server<\/em><\/strong><\/li>\n
\ndns_alt_names = <hostname>,<FQDN of hostname><\/em><\/li>\n
\n#] systemctl start puppetmaster<\/strong><\/em><\/li>\n\n
\n#] echo “<IP of pupper master server>\u00a0 <hostname of pupper master server>\u00a0\u00a0 <FDQN hostname of pupper master server>” >> \/etc\/hosts<\/em><\/strong><\/li>\n
\nserver=<hostname<\/strong> of pupper master server><\/em><\/li>\n<\/ul>\n\n
\n
\n\u00a0\u00a0 \u00a0file {‘\/usr\/local\/sbin\/puppetsimple.sh’:<\/em>
\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0owner => root, group => root, mode => 0755,<\/em>
\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0content => “#!\/bin\/sh \\necho ‘HHHHEEEELLLLOOO’ $1\\n”,<\/em>
\n\u00a0\u00a0 \u00a0}<\/em><\/p>\n
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 package {‘httpd’:<\/em>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ensure => installed,<\/em>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>
\n}<\/em>
\n}<\/em>node ‘<client hostname>’\u00a0\u00a0 \u00a0{<\/em>
\n\u00a0\u00a0 \u00a0include toolbox<\/em><\/p>\n
\n}<\/em><\/p>\n\n
\n#] puppet agent –no-daemonize –onetime –verbose<\/strong><\/em><\/li>\n
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ensure\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 => ‘present’,<\/em>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>
\n}<\/em><\/p>\n
\nclass delmyuser{<\/em><\/p>\n
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ensure\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 => ‘absent’,<\/em>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 }<\/em>
\n}<\/em><\/p>\n\n
\n#] mkdir -p \/etc\/puppet\/modules\/shiju_module\/files<\/em><\/strong><\/li>\n
\n#] echo “Hello World” >> \/etc\/puppet\/modules\/shiju_module<\/em><\/strong>\/<\/em>files<\/em>\/<\/em>shiju.txt <\/em><\/strong><\/li>\n
\n\u00a0\u00a0\u00a0 mode\u00a0\u00a0 => 440,<\/em>
\n\u00a0\u00a0\u00a0 owner\u00a0 => root,<\/em>
\n\u00a0\u00a0\u00a0 group\u00a0 => root,<\/em>
\n\u00a0\u00a0\u00a0 source => “puppet:\/\/\/modules\/shiju_module\/shiju.txt”\u00a0 <\/em><\/p>\n
\n}<\/em><\/p>\n\n