Extracts from Digitalocean tutorial - Revision history

George2 at 08:15, 6 May 2016

2016-05-06T08:15:20Z

2016-05-06T08:14:35Z

2016-05-06T08:14:20Z

2016-05-06T08:13:22Z

2016-05-05T17:41:16Z

2016-05-05T17:29:30Z

2016-05-05T17:24:53Z

2016-05-05T17:19:42Z

2016-05-05T17:18:19Z

2016-05-05T17:17:22Z

@@ Line 6: / Line 6: @@
 sudo apt-get update<br>
 sudo apt-get -y install ntp<br>
-Configure ntp.conf<br>
+Configure ntp.conf with appropriate ntp servers<br>
 sudo service ntp restart<br>
 '''Install puppet'''<br>

@@ Line 1: / Line 1: @@
 Reference - https://www.digitalocean.com/community/tutorials/how-to-install-puppet-4-in-a-master-agent-setup-on-ubuntu-14-04<br><br>
-This installs puppet client and puppet server on a pair of Ubuntu 14.4 machines.<br>
+This installs puppet client and puppet server on a pair of Ubuntu 14.4 machines.<br><br>
 '''Ubuntu 14.04'''<br>
 timedatectl list-timezones<br>

@@ Line 1: / Line 1: @@
 Reference - https://www.digitalocean.com/community/tutorials/how-to-install-puppet-4-in-a-master-agent-setup-on-ubuntu-14-04<br><br>
 '''Ubuntu 14.04'''<br>
 timedatectl list-timezones<br>

@@ Line 1: / Line 1: @@
-Reference - https://www.digitalocean.com/community/tutorials/how-to-install-puppet-4-in-a-master-agent-setup-on-ubuntu-14-04<br>
+Reference - https://www.digitalocean.com/community/tutorials/how-to-install-puppet-4-in-a-master-agent-setup-on-ubuntu-14-04<br><br>
 '''Ubuntu 14.04'''<br>
 timedatectl list-timezones<br>

← Older revision		Revision as of 17:41, 5 May 2016
Line 88:		Line 88:

	node default {} # applies to nodes that aren't explicitly defined		node default {} # applies to nodes that aren't explicitly defined
		+
		+
		+
		+	'''Using a Module'''
		+
		+	Now let's use a module. Modules are useful for grouping tasks together. There are many modules available in the Puppet community, and you can even write your own.<br>
		+	On the Puppet master, install the puppetlabs-apache module from forgeapi:
		+
		+	sudo /opt/puppetlabs/bin/puppet module install puppetlabs-apache
		+
		+	Warning: Do not use this module on an existing Apache setup. It will purge any Apache configurations that are not managed by Puppet.
		+
		+	Now edit site.pp:
		+
		+	sudo vi /etc/puppetlabs/code/environments/production/manifests/site.pp
		+
		+	Now add the following lines to install Apache on host2:<br>
		+	site.pp example
		+
		+	node 'host2' {
		+	class { 'apache': } # use apache module
		+	apache::vhost { 'example.com': # define vhost resource
		+	port => '80',
		+	docroot => '/var/www/html'
		+	}
		+	}
		+
		+	# node default {} # uncomment this line if it doesn't already exist in your manifest
		+
		+	Save and exit. Now the next time Puppet updates host2, it will install the Apache package, and configure a virtual host called "example.com", listening on port 80, and with a document root /var/www/html.
		+
		+	On host2, run the following command:
		+
		+	sudo /opt/puppetlabs/bin/puppet agent --test

← Older revision		Revision as of 17:29, 5 May 2016
Line 67:		Line 67:

	/opt/puppetlabs/bin/puppet agent --test		/opt/puppetlabs/bin/puppet agent --test
		+
		+	'''Specify a Node'''
		+
		+	If you want to define a resource for specific nodes, define a node in the manifest.
		+
		+	On the master, edit site.pp:
		+
		+	sudo vi /etc/puppetlabs/code/environments/production/manifests/site.pp
		+
		+	Now add the following lines:<br>
		+	site.pp example
		+
		+	node 'ns1', 'ns2' { # applies to ns1 and ns2 nodes
		+	file {'/tmp/dns': # resource type file and filename
		+	ensure => present, # make sure it exists
		+	mode => '0644',
		+	content => "Only DNS servers get this file.\n",
		+	}
		+	}
		+
		+	node default {} # applies to nodes that aren't explicitly defined

← Older revision		Revision as of 17:24, 5 May 2016
Line 61:		Line 61:

	sudo touch /etc/puppetlabs/code/environments/production/manifests/site.pp		sudo touch /etc/puppetlabs/code/environments/production/manifests/site.pp
		+
		+	'''Immediate Execution on a Particular Agent Node'''
		+
		+	It is also possible to initiate the check for a particular agent node manually, by running the following command (on the agent node in question):
		+
		+	/opt/puppetlabs/bin/puppet agent --test

← Older revision		Revision as of 17:19, 5 May 2016
Line 55:		Line 55:

	/opt/puppetlabs/bin/facter		/opt/puppetlabs/bin/facter
		+
		+	'''Main Manifest File'''
		+
		+	Puppet uses a domain-specific language to describe system configurations, and these descriptions are saved to files called "manifests", which have a .pp file extension. The default main manifest file is located on your Puppet master server at /etc/puppetlabs/code/environments/production/manifests/site.pp. Let's will create a placeholder file for now:
		+
		+	sudo touch /etc/puppetlabs/code/environments/production/manifests/site.pp

← Older revision		Revision as of 17:18, 5 May 2016
Line 1:		Line 1:
		+	Reference - https://www.digitalocean.com/community/tutorials/how-to-install-puppet-4-in-a-master-agent-setup-on-ubuntu-14-04<br>
	'''Ubuntu 14.04'''<br>		'''Ubuntu 14.04'''<br>
	timedatectl list-timezones<br>		timedatectl list-timezones<br>

← Older revision		Revision as of 17:17, 5 May 2016
Line 50:		Line 50:
	If you want to view all of the requests, signed and unsigned, run the following command:		If you want to view all of the requests, signed and unsigned, run the following command:
	sudo /opt/puppetlabs/bin/puppet cert list --all		sudo /opt/puppetlabs/bin/puppet cert list --all
		+
		+	To see a list of facts that are automatically being gathered on your agent node, run the following command:
		+
		+	/opt/puppetlabs/bin/facter