From gczarcinski at ec.rr.com Thu Dec 4 16:25:00 2014 From: gczarcinski at ec.rr.com (Gene Czarcinski) Date: Thu, 04 Dec 2014 11:25:00 -0500 Subject: Kickstart Install Live Images Message-ID: <54808ADC.4050503@ec.rr.com> This describes basically how to do kickstart Lime Image install: http://fedoraproject.org/wiki/Anaconda/Kickstart/KickstartingFedoraLiveInstallation If you stick with network-only for locations of the install image, this also works for Fedora 20. However, for the full capability of network or USB Flash Drive for the location of the image, the Fedora 21 is needed. Optionally, I have an updates.img available for anaconda-20.25.16-1 here: http://czarc.org/fedora/updates/ As described here: http://fedoraproject.org/wiki/Anaconda/Kickstart#liveimg > > |liveimg --url= [--proxy=] [--checksum=] > [--noverifyssl]| > > Install a disk image instead of packages. The image can be the > squashfs.img from a Live iso, or any filesystem mountable by the > install media (eg. ext4). Anaconda expects the image to contain > utilities it needs to complete the system install so the best way > to create one is to use livemedia-creator to make the disk image. > If the image contains /LiveOS/*.img (this is how squashfs.img is > structured) the first *img file inside LiveOS will be mounted and > used to install the target system. As of Anaconda 21.29 the URL > may point to a tarfile of the root filesystem. The file must end > in .tar, .tbz, .tgz, .txz, .tar.bz2, tar.gz, tar.xz > You can also kickstart install with liveimg pointing to a tarball as or anaconda-21.29 ... well, sort-of. It basically works but there are a couple of problems. 1. The initramfs file for the rescue kernel is not created when doing a tarball install. The problem along with a patch to fix it has been bz'ed: https://bugzilla.redhat.com/show_bug.cgi?id=1170589 and the patch has also been submitted to anaconda-patches. Since it is unlikely that this update will make it into Fedora 21, I have created an updates.img for anaconda-21.48.21-1 which is available here: http://czarc.org/fedora/updates/ (the README.txt is the output of git-log showing what updates are applied). 2. Using the updates.img, you do a kickstart liveimg//install of a tarball. Everything is good ... sorry, no. I am not sure if this is a bug but installation using a tarball needs a full-system SELinux relabel. Fortunately, this is easy to handle by adding the following to your kickstart file: > %post > /usr/bin/touch /.autorelabel > %end Enjoy, Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: From f.krecmer at gmail.com Thu Dec 11 11:59:51 2014 From: f.krecmer at gmail.com (Frantisek Krecmer) Date: Thu, 11 Dec 2014 12:59:51 +0100 Subject: RHEL6.5 provisioning without DHCP Message-ID: Hello, I have following scenario: - need to install very large number of physical servers - RHEL repository is on the network filer (url install, NFS install available) - there is no DHCP available (and it is not possible to have one - long story) - I know serial number and IP for each server My idea was to boot from installation image rhel-server-6.5-x86_64-boot.iso where I modified following: - isolinux.cfg to load kickstart file label Project menu label Project menu default kernel vmlinuz append ks=cdrom:/isolinux/ks.cfg initrd=initrd.img add kickstart file containing network configuration in %pre script (get serial number from dmidecode, assign IP, install from network. + configure hw raid etc etc) Basically, something like this: install url --url 1.2.3.4.7/rhel-x86_64-server-6.5 ... %include /tmp/network %pre #!/bin/sh #------------------------------------------------------------------------------# # PRE-INSTALL NETWORK SETUP # #------------------------------------------------------------------------------# echo "network --bootproto=static --vlanid=123 --ip=1.2.3.4 --netmask=255.255.248.0 --gateway=1.2.3.5 --nameserver=1.2.3.6 --device=eth0" > /tmp/network But. System asks for network settings when booted. I understand that I need to have stage2 loaded before anaconda starts %pre section. So, I need it to use stage2 from iso. But it looks for stage2 on the network when there is url as source in kickstart file. Is there any way how to tell installer: - start Anaconda from CD (use local install.img), run %pre, download packages from url ? file copied to /tmp/ks.cfg setting up kickstart kickstart forcing text mode kickstartFromUrl results of url ks, url http://1.2.3.7/rhel-x86_64-server-6.5 trying to mount CD device /dev/sr0 on /mnt/stage2 drive status is CDC_DISC_OK transferring /mnt/stage2/images/install.img to /tmp mounted loopback device /mnt/runtime on /dev/loop0 as /tmp/install.img #Perfect Looking for updates in /mnt/stage2/images/updates.img Looking for product in /mnt/stage2/images/product.img mounted loopback device /tmp/product-disk on /dev/loop7 as /mnt/stage2/images/product.img umounting loopback /tmp/product-disk /dev/loop7 umounting loopback /mnt/runtime /dev/loop0 #Why?? no stage2= given, assuming http://1.2.3.7/rhel-x86_64-server-6.5/images/install.img #you have it in /tmp already! setting language to en_US.UTF-8 starting STEP_METHOD need to set up networking ... Do you have any idea if it possible to somehow change this stage2 behavior? I found Anaconda boot options but I am unable to set stage2 either by stage2= or inst.stage2=. (Any other idea how to set IP in ks.cfg and use it for packages downloading without DHCP would be also appreciated.) -------------- next part -------------- An HTML attachment was scrubbed... URL: From srobson at cadence.com Thu Dec 11 17:17:05 2014 From: srobson at cadence.com (Steve Robson) Date: Thu, 11 Dec 2014 17:17:05 +0000 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: References: Message-ID: <5489D191.1060108@cadence.com> A popular tool for configuring and automating the installation of Red Hat is a tool called "cobbler". See http://www.cobblerd.org/ Good luck! -Steve kickstart-list-request at redhat.com wrote: > 1. RHEL6.5 provisioning without DHCP (Frantisek Krecmer) > > Subject: RHEL6.5 provisioning without DHCP > From: Frantisek Krecmer > Date: 12/11/2014 11:59 AM > > To: "kickstart-list at redhat.com" > > Hello, > > I have following scenario: > - need to install very large number of physical servers > - RHEL repository is on the network filer (url install, NFS install > available) > - there is no DHCP available (and it is not possible to have one - long > story) > - I know serial number and IP for each server From Brandon.Ess at atk.com Thu Dec 11 17:36:01 2014 From: Brandon.Ess at atk.com (Ess, Brandon) Date: Thu, 11 Dec 2014 17:36:01 +0000 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: <5489D191.1060108@cadence.com> References: <5489D191.1060108@cadence.com> Message-ID: <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> May I ask why you cannot have a DHCP server? As far as Im aware DHCP is required for PXEboot to work. The PXE client with get an IP packet with other information such as where to TFTP the rest pf the pxe files. So in my environment, DHCP packets are received on our WAN gateway and then forwarded to the company's corporate DHCP servers. Since I do not have access to those DHCP servers and two DHCP servers on the same network does not work (sans proper VLANs) another solution needs to be developed; enter DHCPproxy and DNSmasq DNSmasq/DHCPproxy will only respond to DHCP packets from configured MAC address. I cannot remember off the top of my head what version but DHCPproxy is built into newer versions of dhcpd, and dnsmasq is a completely separate utility. The version of dhcpd shipped with RHEL6 does not support dhcpproxy, and therefore dnsmasq is required. Ubuntu 1404 and RHEL7 do support native dhcpproxy via dhcpd. Once you have PXEboot configured, you will point the pxelinux.cfg files to the RHEL6 netboot images, the iso will be loaded, and install via your KS files. https://wiki.debian.org/PXEBootInstall https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP Good luck :) -Brandon -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Steve Robson Sent: Thursday, December 11, 2014 9:17 AM To: kickstart-list at redhat.com Subject: Re: RHEL6.5 provisioning without DHCP A popular tool for configuring and automating the installation of Red Hat is a tool called "cobbler". See http://www.cobblerd.org/ Good luck! -Steve kickstart-list-request at redhat.com wrote: > 1. RHEL6.5 provisioning without DHCP (Frantisek Krecmer) > > Subject: RHEL6.5 provisioning without DHCP > From: Frantisek Krecmer > Date: 12/11/2014 11:59 AM > > To: "kickstart-list at redhat.com" > > Hello, > > I have following scenario: > - need to install very large number of physical servers > - RHEL repository is on the network filer (url install, NFS install > available) > - there is no DHCP available (and it is not possible to have one - > long > story) > - I know serial number and IP for each server _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From f.krecmer at gmail.com Thu Dec 11 17:40:41 2014 From: f.krecmer at gmail.com (Frantisek Krecmer) Date: Thu, 11 Dec 2014 18:40:41 +0100 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: <5489D191.1060108@cadence.com> References: <5489D191.1060108@cadence.com> Message-ID: Hello Steve, thanks! I already checked cobbler and hope we will use it one day. Unfortunately, it is using DHCP and PXE which is not an option in this particular case. By the way. I have correct answer for original question how to pass stage2= parameter to Anaconda: "stage2=hd:/dev/sr0:/images/install.img ks=cdrom" as boot option. (I somehow did not figure out that "hd:" part.) Big "thank you" goes to Marian Ganisin from RH. On Thu, Dec 11, 2014 at 6:17 PM, Steve Robson wrote: > A popular tool for configuring and automating the installation of Red Hat > is a tool called "cobbler". See http://www.cobblerd.org/ > > Good luck! > -Steve > > kickstart-list-request at redhat.com wrote: > >> 1. RHEL6.5 provisioning without DHCP (Frantisek Krecmer) >> >> Subject: RHEL6.5 provisioning without DHCP >> From: Frantisek Krecmer >> Date: 12/11/2014 11:59 AM >> >> To: "kickstart-list at redhat.com" >> >> Hello, >> >> I have following scenario: >> - need to install very large number of physical servers >> - RHEL repository is on the network filer (url install, NFS install >> available) >> - there is no DHCP available (and it is not possible to have one - long >> story) >> - I know serial number and IP for each server >> > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Fahrner at burlingtonstores.com Thu Dec 11 17:44:38 2014 From: Matt.Fahrner at burlingtonstores.com (Matt Fahrner) Date: Thu, 11 Dec 2014 17:44:38 +0000 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> References: <5489D191.1060108@cadence.com> <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> Message-ID: <225ABEF3D4A2C341B83807188760FCDCDFD801F5@EXMAIL01N3.win.coat.com> Yes, it requires DHCP: https://en.wikipedia.org/wiki/Preboot_Execution_Environment - Matt -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Ess, Brandon Sent: Thursday, December 11, 2014 12:36 PM To: Discussion list about Kickstart Subject: RE: RHEL6.5 provisioning without DHCP May I ask why you cannot have a DHCP server? As far as Im aware DHCP is required for PXEboot to work. The PXE client with get an IP packet with other information such as where to TFTP the rest pf the pxe files. So in my environment, DHCP packets are received on our WAN gateway and then forwarded to the company's corporate DHCP servers. Since I do not have access to those DHCP servers and two DHCP servers on the same network does not work (sans proper VLANs) another solution needs to be developed; enter DHCPproxy and DNSmasq DNSmasq/DHCPproxy will only respond to DHCP packets from configured MAC address. I cannot remember off the top of my head what version but DHCPproxy is built into newer versions of dhcpd, and dnsmasq is a completely separate utility. The version of dhcpd shipped with RHEL6 does not support dhcpproxy, and therefore dnsmasq is required. Ubuntu 1404 and RHEL7 do support native dhcpproxy via dhcpd. Once you have PXEboot configured, you will point the pxelinux.cfg files to the RHEL6 netboot images, the iso will be loaded, and install via your KS files. https://wiki.debian.org/PXEBootInstall https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP Good luck :) -Brandon -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Steve Robson Sent: Thursday, December 11, 2014 9:17 AM To: kickstart-list at redhat.com Subject: Re: RHEL6.5 provisioning without DHCP A popular tool for configuring and automating the installation of Red Hat is a tool called "cobbler". See http://www.cobblerd.org/ Good luck! -Steve kickstart-list-request at redhat.com wrote: > 1. RHEL6.5 provisioning without DHCP (Frantisek Krecmer) > > Subject: RHEL6.5 provisioning without DHCP > From: Frantisek Krecmer > Date: 12/11/2014 11:59 AM > > To: "kickstart-list at redhat.com" > > Hello, > > I have following scenario: > - need to install very large number of physical servers > - RHEL repository is on the network filer (url install, NFS install > available) > - there is no DHCP available (and it is not possible to have one - > long > story) > - I know serial number and IP for each server _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ________________________________ Notice: This communication, including attachments, may contain confidential or proprietary information to be conveyed solely for the intended recipient(s). If you are not the intended recipient, or if you otherwise received this message in error, please notify the sender immediately by return e-mail and promptly delete this e-mail, including attachments, without reading or saving them in any manner. The unauthorized use, dissemination, distribution, or reproduction of this e-mail, including attachments, is strictly prohibited and may be unlawful. From f.krecmer at gmail.com Thu Dec 11 17:46:26 2014 From: f.krecmer at gmail.com (Frantisek Krecmer) Date: Thu, 11 Dec 2014 18:46:26 +0100 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> References: <5489D191.1060108@cadence.com> <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> Message-ID: Hi Brandon, thank you for your answer. However I am not able to tell you why not DHCP. Servers (dhcp clients) have 10Gbit fibre cables and are connected to switch ports with VLAN tagging - maybe it is problem to configure it. Who knows. I am not network admin and working only with info I have ;) I have to discuss it with colleagues from IP services team. Anyway, now it is personal challenge to get it working even without DHCP ;) On Thu, Dec 11, 2014 at 6:36 PM, Ess, Brandon wrote: > May I ask why you cannot have a DHCP server? As far as Im aware DHCP is > required for PXEboot to work. The PXE client with get an IP packet with > other information such as where to TFTP the rest pf the pxe files. > > So in my environment, DHCP packets are received on our WAN gateway and > then forwarded to the company's corporate DHCP servers. Since I do not have > access to those DHCP servers and two DHCP servers on the same network does > not work (sans proper VLANs) another solution needs to be developed; enter > DHCPproxy and DNSmasq > > DNSmasq/DHCPproxy will only respond to DHCP packets from configured MAC > address. > > I cannot remember off the top of my head what version but DHCPproxy is > built into newer versions of dhcpd, and dnsmasq is a completely separate > utility. The version of dhcpd shipped with RHEL6 does not support > dhcpproxy, and therefore dnsmasq is required. Ubuntu 1404 and RHEL7 do > support native dhcpproxy via dhcpd. > > Once you have PXEboot configured, you will point the pxelinux.cfg files to > the RHEL6 netboot images, the iso will be loaded, and install via your KS > files. > > https://wiki.debian.org/PXEBootInstall > > https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP > > Good luck :) > > -Brandon > > -----Original Message----- > From: kickstart-list-bounces at redhat.com [mailto: > kickstart-list-bounces at redhat.com] On Behalf Of Steve Robson > Sent: Thursday, December 11, 2014 9:17 AM > To: kickstart-list at redhat.com > Subject: Re: RHEL6.5 provisioning without DHCP > > A popular tool for configuring and automating the installation of Red Hat > is a tool called "cobbler". See http://www.cobblerd.org/ > > Good luck! > -Steve > > kickstart-list-request at redhat.com wrote: > > 1. RHEL6.5 provisioning without DHCP (Frantisek Krecmer) > > > > Subject: RHEL6.5 provisioning without DHCP > > From: Frantisek Krecmer > > Date: 12/11/2014 11:59 AM > > > > To: "kickstart-list at redhat.com" > > > > Hello, > > > > I have following scenario: > > - need to install very large number of physical servers > > - RHEL repository is on the network filer (url install, NFS install > > available) > > - there is no DHCP available (and it is not possible to have one - > > long > > story) > > - I know serial number and IP for each server > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.j.smith at ieee.org Thu Dec 11 18:00:16 2014 From: b.j.smith at ieee.org (Bryan J Smith) Date: Thu, 11 Dec 2014 13:00:16 -0500 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: References: <5489D191.1060108@cadence.com> <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> Message-ID: On Thu, Dec 11, 2014 at 12:46 PM, Frantisek Krecmer wrote: > Hi Brandon, > thank you for your answer. However I am not able to tell you why not DHCP. > Servers (dhcp clients) have 10Gbit fibre cables and are connected to switch > ports with VLAN tagging - maybe it is problem to configure it. Who knows. I > am not network admin and working only with info I have ;) I have to discuss > it with colleagues from IP services team. > Anyway, now it is personal challenge to get it working even without DHCP ;) > ?This is why most Enterprises have ... - Dedicated deployment/management network - The default NIC of all servers connected to that network - The default NIC of all servers enabled for PXEboot first - An [semi-]automated process to enable DHCP with required options for network boot (MAC, nextserver, filename, etc...) But that aside ... There's no reason you cannot walk around with USB keys that solve the issue of lack of DHCP, yet still have the Kickstart/Cobbler profiles, media, etc... on the network. -- bjs -- Bryan J Smith - http://www.linkedin.com/in/bjsmith -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brandon.Ess at atk.com Thu Dec 11 18:01:15 2014 From: Brandon.Ess at atk.com (Ess, Brandon) Date: Thu, 11 Dec 2014 18:01:15 +0000 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: References: <5489D191.1060108@cadence.com> <801C33F0E4A1B8418D4A213ED77C1B1F37FBD6E8@mn05svcwem002.atk.com> Message-ID: <801C33F0E4A1B8418D4A213ED77C1B1F37FBD784@mn05svcwem002.atk.com> Good luck. If you find a way to remotely provision a server without PXE (PXE requires DHCP) let us know. If they are Dell Servers there is IDRAC. While I?ve never used the Enterprise features, it does support bare-metal provisioning but if I remember correctly the provisioning service is just a rebranded Cobbler service?.which requires DHCP. From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Frantisek Krecmer Sent: Thursday, December 11, 2014 9:46 AM To: Discussion list about Kickstart Subject: Re: RHEL6.5 provisioning without DHCP Hi Brandon, thank you for your answer. However I am not able to tell you why not DHCP. Servers (dhcp clients) have 10Gbit fibre cables and are connected to switch ports with VLAN tagging - maybe it is problem to configure it. Who knows. I am not network admin and working only with info I have ;) I have to discuss it with colleagues from IP services team. Anyway, now it is personal challenge to get it working even without DHCP ;) On Thu, Dec 11, 2014 at 6:36 PM, Ess, Brandon > wrote: May I ask why you cannot have a DHCP server? As far as Im aware DHCP is required for PXEboot to work. The PXE client with get an IP packet with other information such as where to TFTP the rest pf the pxe files. So in my environment, DHCP packets are received on our WAN gateway and then forwarded to the company's corporate DHCP servers. Since I do not have access to those DHCP servers and two DHCP servers on the same network does not work (sans proper VLANs) another solution needs to be developed; enter DHCPproxy and DNSmasq DNSmasq/DHCPproxy will only respond to DHCP packets from configured MAC address. I cannot remember off the top of my head what version but DHCPproxy is built into newer versions of dhcpd, and dnsmasq is a completely separate utility. The version of dhcpd shipped with RHEL6 does not support dhcpproxy, and therefore dnsmasq is required. Ubuntu 1404 and RHEL7 do support native dhcpproxy via dhcpd. Once you have PXEboot configured, you will point the pxelinux.cfg files to the RHEL6 netboot images, the iso will be loaded, and install via your KS files. https://wiki.debian.org/PXEBootInstall https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP Good luck :) -Brandon -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Steve Robson Sent: Thursday, December 11, 2014 9:17 AM To: kickstart-list at redhat.com Subject: Re: RHEL6.5 provisioning without DHCP A popular tool for configuring and automating the installation of Red Hat is a tool called "cobbler". See http://www.cobblerd.org/ Good luck! -Steve kickstart-list-request at redhat.com wrote: > 1. RHEL6.5 provisioning without DHCP (Frantisek Krecmer) > > Subject: RHEL6.5 provisioning without DHCP > From: Frantisek Krecmer > > Date: 12/11/2014 11:59 AM > > To: "kickstart-list at redhat.com" > > > Hello, > > I have following scenario: > - need to install very large number of physical servers > - RHEL repository is on the network filer (url install, NFS install > available) > - there is no DHCP available (and it is not possible to have one - > long > story) > - I know serial number and IP for each server _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry.brigman at gmail.com Thu Dec 11 18:21:55 2014 From: larry.brigman at gmail.com (Larry Brigman) Date: Thu, 11 Dec 2014 10:21:55 -0800 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: References: Message-ID: You can set the IP address from the boot line. You may need to know the mac address of the install interface if there is more than one interface on the server. On Dec 11, 2014 4:11 AM, "Frantisek Krecmer" wrote: > Hello, > > > I have following scenario: > - need to install very large number of physical servers > - RHEL repository is on the network filer (url install, NFS install > available) > - there is no DHCP available (and it is not possible to have one - long > story) > - I know serial number and IP for each server > > My idea was to boot from installation image > rhel-server-6.5-x86_64-boot.iso where I modified following: > - isolinux.cfg to load kickstart file > > label Project > menu label Project > menu default > kernel vmlinuz > append ks=cdrom:/isolinux/ks.cfg initrd=initrd.img > > add kickstart file containing network configuration in %pre script (get > serial number from dmidecode, assign IP, install from network. + configure > hw raid etc etc) > > Basically, something like this: > > > install > url --url 1.2.3.4.7/rhel-x86_64-server-6.5 > ... > > %include /tmp/network > > > %pre > #!/bin/sh > > #------------------------------------------------------------------------------# > # PRE-INSTALL NETWORK SETUP # > > #------------------------------------------------------------------------------# > > echo "network --bootproto=static --vlanid=123 --ip=1.2.3.4 > --netmask=255.255.248.0 --gateway=1.2.3.5 --nameserver=1.2.3.6 > --device=eth0" > /tmp/network > > But. System asks for network settings when booted. > I understand that I need to have stage2 loaded before anaconda starts %pre > section. So, I need it to use stage2 from iso. But it looks for stage2 on > the network when there is url as source in kickstart file. Is there any way > how to tell installer: > - start Anaconda from CD (use local install.img), run %pre, download > packages from url ? > > file copied to /tmp/ks.cfg > setting up kickstart > kickstart forcing text mode > kickstartFromUrl > results of url ks, url http://1.2.3.7/rhel-x86_64-server-6.5 > trying to mount CD device /dev/sr0 on /mnt/stage2 > drive status is CDC_DISC_OK > transferring /mnt/stage2/images/install.img to /tmp > mounted loopback device /mnt/runtime on /dev/loop0 as /tmp/install.img > #Perfect > Looking for updates in /mnt/stage2/images/updates.img > Looking for product in /mnt/stage2/images/product.img > mounted loopback device /tmp/product-disk on /dev/loop7 as > /mnt/stage2/images/product.img > umounting loopback /tmp/product-disk /dev/loop7 > umounting loopback /mnt/runtime /dev/loop0 #Why?? > no stage2= given, assuming > http://1.2.3.7/rhel-x86_64-server-6.5/images/install.img #you have it > in /tmp already! > setting language to en_US.UTF-8 > starting STEP_METHOD > need to set up networking > ... > > Do you have any idea if it possible to somehow change this stage2 > behavior? I found Anaconda boot options but I am unable to set stage2 > either by stage2= or inst.stage2=. > (Any other idea how to set IP in ks.cfg and use it for packages > downloading without DHCP would be also appreciated.) > > > > > > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.fisher at verizon.com Thu Dec 11 21:20:22 2014 From: rob.fisher at verizon.com (Fisher, Robert L (ROB)) Date: Thu, 11 Dec 2014 16:20:22 -0500 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: References: Message-ID: <9E58F88EC6E1D8489E6DE99CFAD21BDB12CBABCC66@FHDP1LUMXC7V11.us.one.verizon.com> I?ve been building servers using the ISO for 6 years now and we always use the following setup the networking in the isolinux/isolinux.cfg file: default remoteks prompt 10 timeout 100 display boot.msg F1 boot.msg F2 options.msg F3 general.msg F4 param.msg F5 rescue.msg F7 snake.msg label linux kernel vmlinuz append initrd=initrd.img ramdisk_size=124836 label localks kernel vmlinuz append ks=cdrom initrd=initrd.img text ramdisk_size=124836 label cdbuild kernel vmlinuz append ks=cdrom:/ks.cfg initrd=initrd.img netwait=60 lowres label remoteks kernel vmlinuz append ksdevice=eth0 netwait=60 blacklist=lpfc ks=http://100.1.1.1/ks.cfgs/ks.cfg.hostname ip=10.1.1.100 netmask=255.255.255.0 gateway=10.1.1.254 initrd=initrd.img The entry netwait=60 is a leftover from RHEL 5 but it hasn?t caused any problems with our RHEL 6 builds. This entry just give the network device 60 seconds to enable before it tried to start networking. We use blacklist=lpfc to make sure that the OS does not try to install on anything other than local devices. Good luck, Rob Fisher From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Larry Brigman Sent: Thursday, December 11, 2014 1:22 PM To: Discussion list about Kickstart Subject: Re: RHEL6.5 provisioning without DHCP You can set the IP address from the boot line. You may need to know the mac address of the install interface if there is more than one interface on the server. On Dec 11, 2014 4:11 AM, "Frantisek Krecmer" > wrote: Hello, I have following scenario: - need to install very large number of physical servers - RHEL repository is on the network filer (url install, NFS install available) - there is no DHCP available (and it is not possible to have one - long story) - I know serial number and IP for each server My idea was to boot from installation image rhel-server-6.5-x86_64-boot.iso where I modified following: - isolinux.cfg to load kickstart file label Project menu label Project menu default kernel vmlinuz append ks=cdrom:/isolinux/ks.cfg initrd=initrd.img add kickstart file containing network configuration in %pre script (get serial number from dmidecode, assign IP, install from network. + configure hw raid etc etc) Basically, something like this: install url --url 1.2.3.4.7/rhel-x86_64-server-6.5 ... %include /tmp/network %pre #!/bin/sh #------------------------------------------------------------------------------# # PRE-INSTALL NETWORK SETUP # #------------------------------------------------------------------------------# echo "network --bootproto=static --vlanid=123 --ip=1.2.3.4 --netmask=255.255.248.0 --gateway=1.2.3.5 --nameserver=1.2.3.6 --device=eth0" > /tmp/network But. System asks for network settings when booted. I understand that I need to have stage2 loaded before anaconda starts %pre section. So, I need it to use stage2 from iso. But it looks for stage2 on the network when there is url as source in kickstart file. Is there any way how to tell installer: - start Anaconda from CD (use local install.img), run %pre, download packages from url ? file copied to /tmp/ks.cfg setting up kickstart kickstart forcing text mode kickstartFromUrl results of url ks, url http://1.2.3.7/rhel-x86_64-server-6.5 trying to mount CD device /dev/sr0 on /mnt/stage2 drive status is CDC_DISC_OK transferring /mnt/stage2/images/install.img to /tmp mounted loopback device /mnt/runtime on /dev/loop0 as /tmp/install.img #Perfect Looking for updates in /mnt/stage2/images/updates.img Looking for product in /mnt/stage2/images/product.img mounted loopback device /tmp/product-disk on /dev/loop7 as /mnt/stage2/images/product.img umounting loopback /tmp/product-disk /dev/loop7 umounting loopback /mnt/runtime /dev/loop0 #Why?? no stage2= given, assuming http://1.2.3.7/rhel-x86_64-server-6.5/images/install.img #you have it in /tmp already! setting language to en_US.UTF-8 starting STEP_METHOD need to set up networking ... Do you have any idea if it possible to somehow change this stage2 behavior? I found Anaconda boot options but I am unable to set stage2 either by stage2= or inst.stage2=. (Any other idea how to set IP in ks.cfg and use it for packages downloading without DHCP would be also appreciated.) _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From psvdavey at sealand-systems.co.uk Thu Dec 11 22:28:33 2014 From: psvdavey at sealand-systems.co.uk (Peter Davey) Date: Thu, 11 Dec 2014 22:28:33 +0000 Subject: RHEL6.5 provisioning without DHCP In-Reply-To: <9E58F88EC6E1D8489E6DE99CFAD21BDB12CBABCC66@FHDP1LUMXC7V11.us.one.verizon.com> References: <9E58F88EC6E1D8489E6DE99CFAD21BDB12CBABCC66@FHDP1LUMXC7V11.us.one.verizon.com> Message-ID: Good to see the blacklist=lpfc We always disconnected Fibre Channel after a kickstart disk on the test system reformatted part of the SAN :( *Peter Davey* psvdavey at sealand-systems.co.uk *Tel: +44 1903 209367* *Gsm: +44 7802 651892*www.sealand-systems.co.uk/small On 11 December 2014 at 21:20, Fisher, Robert L (ROB) wrote: > I've been building servers using the ISO for 6 years now and we always use > the following setup the networking in the isolinux/isolinux.cfg file: > > > > default remoteks > > prompt 10 > > timeout 100 > > display boot.msg > > F1 boot.msg > > F2 options.msg > > F3 general.msg > > F4 param.msg > > F5 rescue.msg > > F7 snake.msg > > label linux > > kernel vmlinuz > > append initrd=initrd.img ramdisk_size=124836 > > label localks > > kernel vmlinuz > > append ks=cdrom initrd=initrd.img text ramdisk_size=124836 > > label cdbuild > > kernel vmlinuz > > append ks=cdrom:/ks.cfg initrd=initrd.img netwait=60 lowres > > label remoteks > > kernel vmlinuz > > append ksdevice=eth0 netwait=60 blacklist=lpfc ks= > http://100.1.1.1/ks.cfgs/ks.cfg.hostname ip=10.1.1.100 > netmask=255.255.255.0 gateway=10.1.1.254 initrd=initrd.img > > > > The entry netwait=60 is a leftover from RHEL 5 but it hasn't caused any > problems with our RHEL 6 builds. This entry just give the network device > 60 seconds to enable before it tried to start networking. > > We use blacklist=lpfc to make sure that the OS does not try to install on > anything other than local devices. > > > > Good luck, > > Rob Fisher > > *From:* kickstart-list-bounces at redhat.com [mailto: > kickstart-list-bounces at redhat.com] *On Behalf Of *Larry Brigman > *Sent:* Thursday, December 11, 2014 1:22 PM > *To:* Discussion list about Kickstart > *Subject:* Re: RHEL6.5 provisioning without DHCP > > > > You can set the IP address from the boot line. You may need to know the > mac address of the install interface if there is more than one interface on > the server. > > On Dec 11, 2014 4:11 AM, "Frantisek Krecmer" wrote: > > Hello, > > I have following scenario: > > - need to install very large number of physical servers > > - RHEL repository is on the network filer (url install, NFS install > available) > > - there is no DHCP available (and it is not possible to have one - long > story) > - I know serial number and IP for each server > > My idea was to boot from installation image > rhel-server-6.5-x86_64-boot.iso where I modified following: > > - isolinux.cfg to load kickstart file > > label Project > menu label Project > menu default > kernel vmlinuz > append ks=cdrom:/isolinux/ks.cfg initrd=initrd.img > > add kickstart file containing network configuration in %pre script (get > serial number from dmidecode, assign IP, install from network. + configure > hw raid etc etc) > > Basically, something like this: > > > install > url --url 1.2.3.4.7/rhel-x86_64-server-6.5 > ... > > %include /tmp/network > > > %pre > #!/bin/sh > > #------------------------------------------------------------------------------# > # PRE-INSTALL NETWORK SETUP # > > #------------------------------------------------------------------------------# > > echo "network --bootproto=static --vlanid=123 --ip=1.2.3.4 > --netmask=255.255.248.0 --gateway=1.2.3.5 --nameserver=1.2.3.6 > --device=eth0" > /tmp/network > > > > But. System asks for network settings when booted. > I understand that I need to have stage2 loaded before anaconda starts %pre > section. So, I need it to use stage2 from iso. But it looks for stage2 on > the network when there is url as source in kickstart file. Is there any way > how to tell installer: > > - start Anaconda from CD (use local install.img), run %pre, download > packages from url ? > > file copied to /tmp/ks.cfg > > setting up kickstart > > kickstart forcing text mode > > kickstartFromUrl > > results of url ks, url http://1.2.3.7/rhel-x86_64-server-6.5 > > trying to mount CD device /dev/sr0 on /mnt/stage2 > > drive status is CDC_DISC_OK > > transferring /mnt/stage2/images/install.img to /tmp > > mounted loopback device /mnt/runtime on /dev/loop0 as /tmp/install.img > #Perfect > > Looking for updates in /mnt/stage2/images/updates.img > > Looking for product in /mnt/stage2/images/product.img > > mounted loopback device /tmp/product-disk on /dev/loop7 as > /mnt/stage2/images/product.img > > umounting loopback /tmp/product-disk /dev/loop7 > > umounting loopback /mnt/runtime /dev/loop0 #Why?? > > no stage2= given, assuming > http://1.2.3.7/rhel-x86_64-server-6.5/images/install.img #you have it > in /tmp already! > > setting language to en_US.UTF-8 > > starting STEP_METHOD > > need to set up networking > ... > > Do you have any idea if it possible to somehow change this stage2 > behavior? I found Anaconda boot options but I am unable to set stage2 > either by stage2= or inst.stage2=. > > (Any other idea how to set IP in ks.cfg and use it for packages > downloading without DHCP would be also appreciated.) > > > > > > > > > > > > > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim at rossberry.com Fri Dec 12 02:50:50 2014 From: jim at rossberry.com (Jim Wildman) Date: Thu, 11 Dec 2014 21:50:50 -0500 (EST) Subject: RHEL6.5 provisioning without DHCP In-Reply-To: References: <9E58F88EC6E1D8489E6DE99CFAD21BDB12CBABCC66@FHDP1LUMXC7V11.us.one.verizon.com> Message-ID: As others have noted, you can absolutely do kickstarts without DHCP/PXE. If you don't have physical access to the boxes, then you will need a remote console such as DRAC or ILO with remote media capabilities. You will have to manually provide the ip, netmask, gateway, dns and select the correct network interface as each box boots. Even without DHCP/PXE, you can use cobbler to manage the kickstart profiles, either via a web server, or with the buildiso capability. On Thu, 11 Dec 2014, Peter Davey wrote > Good to see the blacklist=lpfc > > We always disconnected Fibre Channel after a kickstart disk on the test system reformatted part of the SAN :( > > Peter Davey > [Sealand204x109.png] > psvdavey at sealand-systems.co.uk > Tel: +44 1903 209367 > Gsm: +44 7802 651892 > www.sealand-systems.co.uk/small > > On 11 December 2014 at 21:20, Fisher, Robert L (ROB) wrote: > > I?ve been building servers using the ISO for 6 years now and we always use the following setup the > networking in the isolinux/isolinux.cfg file: > > ? > > default remoteks > > prompt 10 > > timeout 100 > > display boot.msg > > F1 boot.msg > > F2 options.msg > > F3 general.msg > > F4 param.msg > > F5 rescue.msg > > F7 snake.msg > > label linux > > ? kernel vmlinuz > > ? append initrd=initrd.img ramdisk_size=124836 > > label localks > > ? kernel vmlinuz > > ? append ks=cdrom initrd=initrd.img text ramdisk_size=124836 > > label cdbuild > > ? kernel vmlinuz > > ? append ks=cdrom:/ks.cfg initrd=initrd.img netwait=60 lowres > > label remoteks > > ? kernel vmlinuz > > ? append ksdevice=eth0 netwait=60 blacklist=lpfc ks=http://100.1.1.1/ks.cfgs/ks.cfg.hostname > ip=10.1.1.100 netmask=255.255.255.0 gateway=10.1.1.254 initrd=initrd.img > > ? > > The entry netwait=60 is a leftover from RHEL 5 but it hasn?t caused any problems with our RHEL 6 > builds.? This entry just give the network device 60 seconds to enable before it tried to start > networking. > > We use blacklist=lpfc to make sure that the OS does not try to install on anything other than local > devices. > > ? > > Good luck, > > Rob Fisher > > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Larry > Brigman > Sent: Thursday, December 11, 2014 1:22 PM > To: Discussion list about Kickstart > Subject: Re: RHEL6.5 provisioning without DHCP > > ? > > You can set the IP address from the boot line.? You may need to know the mac address of the install > interface if there is more than one interface on the server. > > On Dec 11, 2014 4:11 AM, "Frantisek Krecmer" wrote: > > Hello, > > I have following scenario: > > - need to install very large number of physical servers > > - RHEL repository is on the network filer (url install, NFS install available) > > - there is no DHCP available (and it is not possible to have one - long story) > - I know serial number and IP for each server > > My idea was to boot from installation image rhel-server-6.5-x86_64-boot.iso where I modified following: > > - isolinux.cfg to load kickstart file > > label Project > ? menu label Project > ? menu default > ? kernel vmlinuz > ? append ks=cdrom:/isolinux/ks.cfg initrd=initrd.img > > add kickstart file containing network configuration in %pre script (get serial number from dmidecode, assign > IP, install from network.? + configure hw raid etc etc) > > Basically, something like this: > > > install > url --url 1.2.3.4.7/rhel-x86_64-server-6.5 > ... > > %include /tmp/network > > > %pre > #!/bin/sh > #------------------------------------------------------------------------------# > #???????????????????? PRE-INSTALL NETWORK SETUP??????? # > #------------------------------------------------------------------------------# > > echo "network --bootproto=static --vlanid=123 --ip=1.2.3.4 --netmask=255.255.248.0 --gateway=1.2.3.5 > --nameserver=1.2.3.6 --device=eth0" > /tmp/network > > ? > > But. System asks for network settings when booted. > I understand that I need to have stage2 loaded before anaconda starts %pre section. So, I need it to use > stage2 from iso. But it looks for stage2 on the network when there is url as source in kickstart file. Is > there any way how to tell installer: > > - start Anaconda from CD (use local install.img), run %pre, download packages from url ? > > file copied to /tmp/ks.cfg > > setting up kickstart > > kickstart forcing text mode > > kickstartFromUrl > > results of url ks, url http://1.2.3.7/rhel-x86_64-server-6.5 > > trying to mount CD device /dev/sr0 on /mnt/stage2 > > drive status is CDC_DISC_OK > > transferring /mnt/stage2/images/install.img to /tmp > > mounted loopback device /mnt/runtime on /dev/loop0 as /tmp/install.img?? #Perfect > > Looking for updates in /mnt/stage2/images/updates.img > > Looking for product in /mnt/stage2/images/product.img > > mounted loopback device /tmp/product-disk on /dev/loop7 as /mnt/stage2/images/product.img > > umounting loopback /tmp/product-disk /dev/loop7? > > umounting loopback /mnt/runtime /dev/loop0????????????????????? #Why?? > > no stage2= given, assuming http://1.2.3.7/rhel-x86_64-server-6.5/images/install.img?? #you have it in /tmp > already! > > setting language to en_US.UTF-8 > > starting STEP_METHOD > > need to set up networking > ... > > Do you have any idea if it possible to somehow change this stage2 behavior? I found Anaconda boot options > but I am unable to set stage2 either by stage2= or inst.stage2=.? > > (Any other idea how to set IP in ks.cfg and use it for packages downloading without DHCP would be also > appreciated.) > > ? > > ? > > > > ? > > ? > > ? > > ? > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > ---------------------------------------------------------------------- Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.net "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine From spikewhitetx at gmail.com Fri Dec 12 16:16:57 2014 From: spikewhitetx at gmail.com (Spike White) Date: Fri, 12 Dec 2014 10:16:57 -0600 Subject: RHEL6.5 provisioning without DHCP (Ess, Brandon) Message-ID: Brandon, With Dell DRACs, you can "attach virtual media". I.e., either a CD image or a disk image. I'm guessing HP's remote access controller is similar. Using that, the original post (Frantisek) can do the CD-based install he wants. I.e., have the image on his local Windows or Linux desktop, attach that virtual media via DRAC. We customarily do that for 10 - 100 servers. I'm guessing a good engineer can image 5 servers per hour -- if the ks.cfg has all answers, so the install is non-interactive. There are some limitations. Because virtual media attachment is dog-slow. It's best to: 1. minimize the image size as much as possible. 2. have your desktop in a close network location to the servers you're imaging. For this second reason, we usually maintain "jump" servers in different geographic regions. For instance, when I'm imaging a server in Brazil, I'll remote (Windows) or XRDP (Linux) into a Brazil jump server, image from there. If by "large number of servers" is meant a few hundred or more, the original poster will either need PXE or a large array of heads-down engineers. Spike > From: "Ess, Brandon" > To: Discussion list about Kickstart > Cc: > Date: Thu, 11 Dec 2014 18:01:15 +0000 > Subject: RE: RHEL6.5 provisioning without DHCP > Good luck. If you find a way to remotely provision a server without PXE (PXE requires DHCP) let us know. > > If they are Dell Servers there is IDRAC. While I?ve never used the Enterprise features, it does support bare-metal provisioning but if I remember correctly the provisioning service is just a rebranded Cobbler service?.which requires DHCP. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brandon.Ess at atk.com Fri Dec 12 16:51:57 2014 From: Brandon.Ess at atk.com (Ess, Brandon) Date: Fri, 12 Dec 2014 16:51:57 +0000 Subject: RHEL6.5 provisioning without DHCP (Ess, Brandon) In-Reply-To: References: Message-ID: <801C33F0E4A1B8418D4A213ED77C1B1F37FBE310@mn05svcwem002.atk.com> Spike, Well said. I accomplish this in a similar way except I PXEboot to load the kernel and initrd, and then kickstart the OS installer in non-interactive install. I try to use a generic as possible KS files, and then once the install is accomplished the host shows up in Foreman and I select the most appropriate Puppet host group #RHEL-6.6 Workstation PuppetClient LABEL RHEL-6.6 (64-bit) Workstation PuppetClient MENU PASSWD HASHEDPASSWD MENU PASSPROMPT Enter Password: MENU PASSWORDMARGIN 26 MENU PASSWORDROW 12 KERNEL rhel/x86_64/6/vmlinuz APPEND ks=http://URL/ks/rhel6-workstation-puppetclient.ks initrd=rhel/x86_64/6/initrd.img ramdisk_size=10000 ksdevice=eth0 ip=dhcp Then in my KS file: url --url http://URL/rhel/6/x86_64/6.6/os -Brandon From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Spike White Sent: Friday, December 12, 2014 8:17 AM To: kickstart-list at redhat.com Subject: RE: RHEL6.5 provisioning without DHCP (Ess, Brandon) Brandon, With Dell DRACs, you can "attach virtual media". I.e., either a CD image or a disk image. I'm guessing HP's remote access controller is similar. Using that, the original post (Frantisek) can do the CD-based install he wants. I.e., have the image on his local Windows or Linux desktop, attach that virtual media via DRAC. We customarily do that for 10 - 100 servers. I'm guessing a good engineer can image 5 servers per hour -- if the ks.cfg has all answers, so the install is non-interactive. There are some limitations. Because virtual media attachment is dog-slow. It's best to: 1. minimize the image size as much as possible. 2. have your desktop in a close network location to the servers you're imaging. For this second reason, we usually maintain "jump" servers in different geographic regions. For instance, when I'm imaging a server in Brazil, I'll remote (Windows) or XRDP (Linux) into a Brazil jump server, image from there. If by "large number of servers" is meant a few hundred or more, the original poster will either need PXE or a large array of heads-down engineers. Spike > From: "Ess, Brandon" > > To: Discussion list about Kickstart > > Cc: > Date: Thu, 11 Dec 2014 18:01:15 +0000 > Subject: RE: RHEL6.5 provisioning without DHCP > Good luck. If you find a way to remotely provision a server without PXE (PXE requires DHCP) let us know. > > If they are Dell Servers there is IDRAC. While I?ve never used the Enterprise features, it does support bare-metal provisioning but if I remember correctly the provisioning service is just a rebranded Cobbler service?.which requires DHCP. -------------- next part -------------- An HTML attachment was scrubbed... URL: