Foreman - Revision history

Leo at 22:01, 14 June 2020

2020-06-14T22:01:20Z

← Older revision		Revision as of 22:01, 14 June 2020
Line 259:		Line 259:

	{{Navbox Linux}}[[Category:Linux]]		{{Navbox Linux}}[[Category:Linux]]
			[[Category:LinuxUtilities]]

Leo: Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

2019-09-01T06:22:05Z

Text replacement - "Category:Linux{{Navbox Linux}}" to "{{Navbox Linux}}Category:Linux"

← Older revision		Revision as of 06:22, 1 September 2019
Line 258:		Line 258:
	* https://theforeman.org/api/1.8/index.html		* https://theforeman.org/api/1.8/index.html

	[[Category:Linux]]~~{{Navbox Linux}}~~		{{Navbox Linux}}[[Category:Linux]]

Leo: Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

2019-09-01T05:08:57Z

Text replacement - "Category:Linux" to "Category:Linux{{Navbox Linux}}"

← Older revision		Revision as of 05:08, 1 September 2019
Line 258:		Line 258:
	* https://theforeman.org/api/1.8/index.html		* https://theforeman.org/api/1.8/index.html

	[[Category:Linux]]		[[Category:Linux]]{{Navbox Linux}}

Leo: Text replacement - "{\| " to "{| class="wikitable" "

2019-09-01T01:37:45Z

Text replacement - "{\| " to "{| class="wikitable" "

← Older revision		Revision as of 01:37, 1 September 2019
Line 183:		Line 183:

	Ensure that each host group has the following parameter:		Ensure that each host group has the following parameter:
	{\|		{\| class="wikitable"
	! Name		! Name
	! Value		! Value

Leo: /* Default PXE Menu */

2018-06-15T18:11:20Z

Default PXE Menu

← Older revision		Revision as of 18:11, 15 June 2018
Line 204:		Line 204:
	=== Default PXE Menu ===		=== Default PXE Menu ===

	The default PXE menu that is shown is configured by the {{code\|/var/lib/tftpboot/pxelinux.cfg/default}} file. This file is generated by Foreman using the default template "PXELinux default ~~local boot~~" when you click on the "Build PXE Default" button on the Provisioning Template page on all (?) smart proxies that have been configured with TFTP.		The default PXE menu that is shown is configured by the {{code\|/var/lib/tftpboot/pxelinux.cfg/default}} file. This file is generated by Foreman using the default template "PXELinux global default" when you click on the "Build PXE Default" button on the Provisioning Template page on all (?) smart proxies that have been configured with TFTP.

	== Troubleshooting ==		== Troubleshooting ==

Leo at 17:51, 15 June 2018

2018-06-15T17:51:21Z

← Older revision		Revision as of 17:51, 15 June 2018
Line 253:		Line 253:
	If it still doesn't work, try clearing the puppet environment classes and try again. {{code\|DELETE FROM "environment_classes";}}		If it still doesn't work, try clearing the puppet environment classes and try again. {{code\|DELETE FROM "environment_classes";}}


			== See Also ==
			API reference
			* https://theforeman.org/api/1.8/index.html

	[[Category:Linux]]		[[Category:Linux]]

Leo: /* Configuration */

2018-06-11T17:35:29Z

Configuration

← Older revision		Revision as of 17:35, 11 June 2018
Line 198:		Line 198:
	\|-		\|-
	\| package_groups0 \|\| cpsc-base		\| package_groups0 \|\| cpsc-base
			\|-
			\| remote_execution_ssh_keys \|\| authorized_keys for root
	\|}		\|}

Leo: /* Configuration */

2018-06-11T17:29:44Z

Configuration

← Older revision		Revision as of 17:29, 11 June 2018
Line 170:		Line 170:

	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	puppet module install puppetlabs-ntp --version 7.1.1		# puppet module install puppetlabs-ntp --version 7.1.1
	}}		}}

Line 192:		Line 192:
	\|-		\|-
	\| ntp-server\|\| ntp.cpsc.ucalgary.ca		\| ntp-server\|\| ntp.cpsc.ucalgary.ca
			\|-
			\| time-zone \|\| America/Edmonton
	\|-		\|-
	\| salt_master \|\| salt.cs.ucalgary.ca		\| salt_master \|\| salt.cs.ucalgary.ca

Leo: /* Configuration */

2018-06-11T17:03:45Z

Configuration

← Older revision		Revision as of 17:03, 11 June 2018
Line 179:		Line 179:
	If importing an environment succeeds but doesn't actually import anything, make sure that all hosts do not have an environment set and try again.		If importing an environment succeeds but doesn't actually import anything, make sure that all hosts do not have an environment set and try again.

			==== Host Groups ====
			This is specific to computer science.

			Ensure that each host group has the following parameter:
			{\|
			! Name
			! Value
			\|-
			\| install_type \|\| text
			\|-
			\| system_type \|\| text
			\|-
			\| ntp-server\|\| ntp.cpsc.ucalgary.ca
			\|-
			\| salt_master \|\| salt.cs.ucalgary.ca
			\|-
			\| package_groups0 \|\| cpsc-base
			\|}

	=== Default PXE Menu ===		=== Default PXE Menu ===

Leo at 17:01, 11 June 2018

2018-06-11T17:01:09Z

← Older revision		Revision as of 17:01, 11 June 2018
Line 66:		Line 66:
	This stage takes a while. Make a note of the user credentials after installation succeeds.		This stage takes a while. Make a note of the user credentials after installation succeeds.

	Allow ~~certain ports~~ through the firewall.		Allow the foreman webservice, puppet, and optionally the database (for debugging purposes) through the firewall using the {{code\|firewall-cmd}} command.
	{{~~Todo~~
	\|~~1=Configure the~~ firewall ~~properly~~
	~~\|2=Add the proper commands to configure the firewall appropriately.~~
	}}
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
	# ~~systemctl disable firewalld~~		## HTTP / HTTPS
	# ~~systemctl stop firewalld~~		# firewall-cmd --permanent --add-port=80/tcp
			# firewall-cmd --permanent --add-port=443/tcp
			## Puppet
			# firewall-cmd --permanent --add-port=8140/tcp
			## Postgresql (only if remote connection is needed)
			# firewall-cmd --permanent --add-port=5432/tcp

			## Reload the firewall
			# firewall-cmd --reload
	}}		}}

	You may also want to disable SELinux ~~as it might cause issues with Foreman from working properly.~~		You may also want to disable SELinux to simplify the debugging step on a test environment.
	~~{{Todo~~
	~~\|1=Verify that this is actually accurate~~
	~~\|2=I think foreman should work with SELinux. Issues I had might be related~~ to the ~~firewall~~.
	}}
	{{highlight\|lang=terminal\|code=		{{highlight\|lang=terminal\|code=
			## Do so only if you really want to disable SELinux. Foreman should work with SELinux enabled.
	# setenforce 0		# setenforce 0
	# vi /etc/selinux/config		# vi /etc/selinux/config
Line 89:		Line 90:

	=== Smart Proxy ===		=== Smart Proxy ===
	A Foreman Smart Proxy provides a RESTful interface that interacts with certain services such as DHCP or DNS. Installing only the Foreman Smart Proxy requires the installation of the {{code\|foreman-proxy}} package.		A Foreman Smart Proxy provides a RESTful interface that interacts with certain services such as DHCP or DNS.

			The foreman-installer can be used to install the smart proxy. Ensure that the installer does not install foreman by disabling that feature.

			You may wish to use this answers file to configure a smart proxy to handle DHCP, DNS (on a remote AD server), and TFTP: https://paste.steamr.com/view/8cff58b8

			Alternatively, you may install the smart proxy using the {{code\|foreman-proxy}} package and then configuring the proxy manually by editing {{code\|/etc/foreman-proxy/settings.yml}}.

			<!--
			To install the smart proxy manually:
			Installing only the Foreman Smart Proxy requires the installation of the {{code\|foreman-proxy}} package.

	To set up a Smart Proxy that handles DHCP and DNS on a separate server, run:		To set up a Smart Proxy that handles DHCP and DNS on a separate server, run:
Line 110:		Line 121:
	# /usr/share/foreman-proxy/bin/smart-proxy		# /usr/share/foreman-proxy/bin/smart-proxy
	}}		}}
			-->


Line 126:		Line 137:

	=== Foreman ===		=== Foreman ===
	A few things that should be done on a clean install:		A few things that should be done after a clean install:

	# Add smart proxies		# Add smart proxies
Line 154:		Line 165:
	}}		}}
	#* Each with package_groupX		#* Each with package_groupX

			==== Puppet ====
			Puppet modules can be installed on the puppet master (on foreman) by running:

			{{highlight\|lang=terminal\|code=
			puppet module install puppetlabs-ntp --version 7.1.1
			}}

			If it is working, the module should be placed in {{code\|/etc/puppetlabs/code/environments/production/modules}}.

			Since installing this module changed the contents in the 'production' environment, you can 'sync' the changes by importing it through the foreman web interface under 'Configure' -> 'Environments'.

			If importing an environment succeeds but doesn't actually import anything, make sure that all hosts do not have an environment set and try again.


Line 201:		Line 225:

	You're trying to boot a UEFI program while in legacy BIOS mode. You probably selected GRUB2-EFI as the boot loader rather than legacy BIOS when setting up your host.		You're trying to boot a UEFI program while in legacy BIOS mode. You probably selected GRUB2-EFI as the boot loader rather than legacy BIOS when setting up your host.

			=== Cannot import Puppet Environment ===
			If importing an environment succeeds but doesn't actually import anything, make sure that all hosts do not have an environment set and try again.

			If it still doesn't work, try clearing the puppet environment classes and try again. {{code\|DELETE FROM "environment_classes";}}


	[[Category:Linux]]		[[Category:Linux]]