From 886ac430791ac507842fddd145c607e86b62403e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michal=20Kone=C4=8Dn=C3=BD?= Date: Fri, 3 Sep 2021 10:53:23 +0200 Subject: [PATCH] Review kickstarts SOP MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Michal Konečný --- modules/sysadmin_guide/nav.adoc | 2 +- modules/sysadmin_guide/pages/kickstarts.adoc | 39 ++++++++++---------- 2 files changed, 20 insertions(+), 21 deletions(-) diff --git a/modules/sysadmin_guide/nav.adoc b/modules/sysadmin_guide/nav.adoc index 8be5efe..06753b7 100644 --- a/modules/sysadmin_guide/nav.adoc +++ b/modules/sysadmin_guide/nav.adoc @@ -57,7 +57,7 @@ ** xref:iscsi.adoc[iSCSI - SOP] ** xref:jenkins-fedmsg.adoc[Jenkins Fedmsg - SOP] ** xref:kerneltest-harness.adoc[Kerneltest-harness - SOP] -** xref:kickstarts.adoc[kickstarts - SOP in review ] +** xref:kickstarts.adoc[Kickstart Infrastructure - SOP] ** xref:koji.adoc[koji - SOP in review ] ** xref:koji-archive.adoc[koji-archive - SOP in review ] ** xref:koji-builder-setup.adoc[koji-builder-setup - SOP in review ] diff --git a/modules/sysadmin_guide/pages/kickstarts.adoc b/modules/sysadmin_guide/pages/kickstarts.adoc index ae0decf..c0be6db 100644 --- a/modules/sysadmin_guide/pages/kickstarts.adoc +++ b/modules/sysadmin_guide/pages/kickstarts.adoc @@ -19,10 +19,10 @@ Purpose:: == Introduction -Our kickstart infrastructure lives on batcave01. All install media and -kickstart scripts are located on batcave01. Because the RHEL binaries +Our kickstart infrastructure lives on _batcave01_. All install media and +kickstart scripts are located on _batcave01_. Because the RHEL binaries are not public we have these bits blocked. You can add needed IPs to -(from batcave01): +(from _batcave01_): .... ansible/roles/batcave/files/allows @@ -31,7 +31,6 @@ ansible/roles/batcave/files/allows == Physical Machine (kvm virthost) [NOTE] -.Note ==== PXE Booting: If PXE booting just follow the prompt after doing the pxe boot (most hosts will pxeboot via console hitting f12). @@ -42,12 +41,12 @@ hosts will pxeboot via console hitting f12). This only works on an already booted box, many boxes at our colocations may have to be rebuilt by the people in those locations first. Also make sure the IP you are about to boot to install from is allowed to our IP -restricted infrastructure.fedoraproject.org as noted above (in +restricted _infrastructure.fedoraproject.org_ as noted above (in Introduction). Download the vmlinuz and initrd images. -for a rhel6 install: +For a rhel6 install: .... wget https://infrastructure.fedoraproject.org/repo/rhel/RHEL6-x86_64/images/pxeboot/vmlinuz \ @@ -62,14 +61,14 @@ grubby --add-kernel=/boot/vmlinuz-install \ --title="install el6" --initrd=/boot/initrd-install.img .... -for a rhel7 install: +For a rhel7 install: .... wget https://infrastructure.fedoraproject.org/repo/rhel/RHEL7-x86_64/images/pxeboot/vmlinuz -O /boot/vmlinuz-install wget https://infrastructure.fedoraproject.org/repo/rhel/RHEL7-x86_64/images/pxeboot/initrd.img -O /boot/initrd-install.img .... -For phx2 hosts: +For iad2 hosts: .... grubby --add-kernel=/boot/vmlinuz-install \ @@ -82,7 +81,7 @@ grubby --add-kernel=/boot/vmlinuz-install \ (You will need to setup the br1 device if any after install) -For non phx2 hosts: +For non iad2 hosts: .... grubby --add-kernel=/boot/vmlinuz-install \ @@ -105,25 +104,25 @@ as your kickstart If you know the number of hard drives the system has there are other kickstarts which can be used. -2 disk system:::: +2 disk system:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-02disk -or external:::: +or external:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-02disk-ext -4 disk system:::: +4 disk system:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-04disk -or external:::: +or external:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-04disk-ext -6 disk system:::: +6 disk system:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-06disk -or external:::: +or external:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-06disk-ext -8 disk system:::: +8 disk system:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-08disk -or external:::: +or external:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-08disk-ext -10 disk system:::: +10 disk system:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-10disk -or external:::: +or external:: ks=https://infrastructure.fedoraproject.org/repo/rhel/ks/hardware-rhel-7-10disk-ext Double and triple check your configuration settings (On RHEL-6 @@ -152,7 +151,7 @@ Once the box logs you out, start pinging the IP address. It will disappear and come back. Once you can ping it again, try to open up a VNC session. It can take a couple of minutes after the box is back up for it to actually allow vnc sessions. The VNC password is in the -kickstart script on batcave01: +kickstart script on _batcave01_: .... grep vnc /mnt/fedora/app/fi-repo/rhel/ks/hardware-rhel-7-nohd