Linux/Xen/DomU/CentOS/CentOS 7 - Revision history

Pyromania: /* Final Cleanup */

2019-02-16T19:50:07Z

Final Cleanup

← Older revision		Revision as of 11:50, 16 February 2019
Line 210:		Line 210:
	Zero out log files to save space.		Zero out log files to save space.

			<pre>
	echo '' > /var/log/dmesg		echo '' > /var/log/dmesg
	echo '' > /var/log/maillog		echo '' > /var/log/maillog
Line 216:		Line 217:
	echo '' > /var/log/cron		echo '' > /var/log/cron
	echo '' > /var/log/messages		echo '' > /var/log/messages
			</pre>

	Shutdown the virtual machine and you can start cloning this image.		Shutdown the virtual machine and you can start cloning this image.

Pyromania at 19:47, 16 February 2019

2019-02-16T19:47:34Z

← Older revision		Revision as of 11:47, 16 February 2019
Line 196:		Line 196:

	Change 'SELINUX=' to enforcing.		Change 'SELINUX=' to enforcing.


			====Final Cleanup====

			Remove the DHCP lease file for eth0

			rm /var/lib/dhclient/dhclient--eth0.lease

			Remove the SSH host keys so you don't get duplicates when cloning the image.

			rm /etc/ssh/ssh_host*

			Zero out log files to save space.

			echo '' > /var/log/dmesg
			echo '' > /var/log/maillog
			echo '' > /var/log/boot.log
			echo '' > /var/log/secure
			echo '' > /var/log/cron
			echo '' > /var/log/messages

			Shutdown the virtual machine and you can start cloning this image.

Pyromania: /* Building the compact image */

2019-02-16T19:42:49Z

Building the compact image

← Older revision		Revision as of 11:42, 16 February 2019
Line 146:		Line 146:
	rsync -avH /mnt/img/ /mnt/img2/		rsync -avH /mnt/img/ /mnt/img2/

	CentOS defaults to using the UUID ~~syntac~~ for /etc/fstab. This won't work since we copied the OS to a new ~~filesystem~~.		CentOS defaults to using the UUID syntax for /etc/fstab. This won't work since we copied the OS to a new file system.

	vi /mnt/img2/etc/fstab		vi /mnt/img2/etc/fstab
Line 154:		Line 154:
	/dev/sda1 / xfs defaults 0 0		/dev/sda1 / xfs defaults 0 0

			You can remove the UUID section from /mnt/img2/etc/sysconfig/network-scripts/ifcfg-eth0 since we won't be using NetworkManager.
			DHCP_HOSTNAME can also be removed.

	When the OS was copied to the compact image, the SELinux contexts were not copied over. If you were to try and boot the compact image now, things would fail to start and you would not be able to login because SELinux would prevent you from running a shell. So we need to set SELinux to permissive for the first boot so we can fix the contexts.		When the OS was copied to the compact image, the SELinux contexts were not copied over. If you were to try and boot the compact image now, things would fail to start and you would not be able to login because SELinux would prevent you from running a shell. So we need to set SELinux to permissive for the first boot so we can fix the contexts.
Line 183:		Line 185:
	root = "/dev/xvda1 ro"		root = "/dev/xvda1 ro"
	</syntaxhighlight>		</syntaxhighlight>


			Boot the compact image and log in. Then run the command,

			restorecon -R -v /

			This will reset all the SELinux contexts for the file system. When that finishes you can set SELinux back to enforcing.

			vi /etc/selinux/config

			Change 'SELINUX=' to enforcing.

Pyromania: /* Building the compact image */

2019-02-16T18:39:23Z

Building the compact image

← Older revision		Revision as of 10:39, 16 February 2019
Line 161:		Line 161:
	Change 'SELINUX=' to permissive.		Change 'SELINUX=' to permissive.

	<syntaxhighlight ~~type~~="bash">		<syntaxhighlight lang="bash">
	# This file controls the state of SELinux on the system.		# This file controls the state of SELinux on the system.
	# SELINUX= can take one of these three values:		# SELINUX= can take one of these three values:
Line 172:		Line 172:
	Create a basic Xen config so we can boot the image.		Create a basic Xen config so we can boot the image.

	<syntaxhighlight ~~type~~="python">		<syntaxhighlight lang="python">
	name="centos7base"		name="centos7base"
	vcpus=2		vcpus=2

Pyromania: /* Building the compact image */

2019-02-16T18:38:16Z

Building the compact image

@@ Line 146: / Line 146: @@
   rsync -avH /mnt/img/ /mnt/img2/
 When the OS was copied to the compact image, the SELinux contexts were not copied over. If you were to try and boot the compact image now, things would fail to start and you would not be able to login because SELinux would prevent you from running a shell. So we need to set SELinux to permissive for the first boot so we can fix the contexts.
@@ Line 159: / Line 168: @@
 #     disabled - No SELinux policy is loaded.
 SELINUX=permissive
 </syntaxhighlight>

Pyromania: /* Building the compact image */

2019-02-16T18:21:30Z

Building the compact image

← Older revision		Revision as of 10:21, 16 February 2019
Line 145:		Line 145:

	rsync -avH /mnt/img/ /mnt/img2/		rsync -avH /mnt/img/ /mnt/img2/

			When the OS was copied to the compact image, the SELinux contexts were not copied over. If you were to try and boot the compact image now, things would fail to start and you would not be able to login because SELinux would prevent you from running a shell. So we need to set SELinux to permissive for the first boot so we can fix the contexts.

			vi /mnt/img2/etc/selinux/config

			Change 'SELINUX=' to permissive.

			<syntaxhighlight type="bash">
			# This file controls the state of SELinux on the system.
			# SELINUX= can take one of these three values:
			# enforcing - SELinux security policy is enforced.
			# permissive - SELinux prints warnings instead of enforcing.
			# disabled - No SELinux policy is loaded.
			SELINUX=permissive
			</syntaxhighlight>

Pyromania: /* CentOS 7 */

2019-02-02T22:20:06Z

CentOS 7

@@ Line 117: / Line 117: @@
 The virtual machine should boot up and launch anaconda to begin the automated install process.
-You will get an error when it tries to install the bootloader. Since we don't use GRUB2 with Xen you can "yes" to continue the installation.
+You will get an error when it tries to install the bootloader. Since we don't use GRUB2 with Xen you can safely say "yes" to continue the installation.
-It will ask you to hit Return to finish and then the vitual machine will shutdown and halt.
+It will ask you to hit Return to finish and then the virtual machine will shutdown and halt.

Pyromania: /* Kickstart Xen Config */

2019-02-02T21:42:54Z

Kickstart Xen Config

← Older revision		Revision as of 13:42, 2 February 2019
Line 110:		Line 110:
	extra="inst.repo=http://mirror.centos.org/centos/7/os/x86_64/ ip=192.168.1.20::192.168.1.1:255.255.255.0:centos7ks:eth0:none nameserver=192.168.1.1 inst.ks=http://192.168.1.80/kickstart/centos_domu.cfg"		extra="inst.repo=http://mirror.centos.org/centos/7/os/x86_64/ ip=192.168.1.20::192.168.1.1:255.255.255.0:centos7ks:eth0:none nameserver=192.168.1.1 inst.ks=http://192.168.1.80/kickstart/centos_domu.cfg"
	</syntaxhighlight>		</syntaxhighlight>

			Boot the Xen config and access the console.

			xl create centos7_ks.cfg -c

			The virtual machine should boot up and launch anaconda to begin the automated install process.

			You will get an error when it tries to install the bootloader. Since we don't use GRUB2 with Xen you can "yes" to continue the installation.

			It will ask you to hit Return to finish and then the vitual machine will shutdown and halt.

Pyromania: /* CentOS 7 */

2019-02-02T21:11:54Z

CentOS 7

@@ Line 83: / Line 83: @@
 pwpolicy luks --minlen=6 --minquality=1 --notstrict --nochanges --notempty
 %end
 </syntaxhighlight>

Pyromania: /* CentOS 7 */

2019-01-20T23:01:20Z

CentOS 7

← Older revision		Revision as of 15:01, 20 January 2019
Line 18:		Line 18:
	Here is the kickstart config that will need to be put on a webserver.		Here is the kickstart config that will need to be put on a webserver.

	<syntaxhighlight lang="~~text~~">		<syntaxhighlight lang="bash">
	#version=1.0.0		#version=1.0.0