From jebi01 at handelsbanken.se Mon Mar 9 14:02:53 2015 From: jebi01 at handelsbanken.se (Jerry Billing) Date: Mon, 9 Mar 2015 15:02:53 +0100 Subject: Kickstart - Partitioning....possible to use whole disk for LVM without creating a LVM partition In-Reply-To: References: Message-ID: Hi For virtual servers it is nice to use the whole disk for LVM instead of creating a LVM partition on the disk. Then you can just increase the size of the disk in VMware and later extend the file system instead of having to add another disk and extend. Is it possible to use this setup in the kickstart? What syntax do one use if it is possible? If I have done it manually it whould have been like this: pvcreate /dev/sdb (instead of using a LVM partition called /dev/sdb1) vgcreate DataVG /dev/sdb lvcreate -n DataLV -l 100%FREE DataVG DataLV At the moment I have the following partitioning script in my kickstart file for RHEL6/7 as a pre script: DISK_TYPE=$(parted -s /dev/sda print |grep Model | awk '{print $2}') echo "Disk type = $DISK_TYPE" if [ "$DISK_TYPE" = "VMware" ] then echo "This is a VMware server, disk type=$DISK_TYPE" cat > /tmp/partitioning.cfg < /tmp/partitioning.cfg < From jamesaharrisonuk at yahoo.co.uk Mon Mar 9 15:21:14 2015 From: jamesaharrisonuk at yahoo.co.uk (James Harrison) Date: Mon, 9 Mar 2015 15:21:14 +0000 (UTC) Subject: Kickstart - Partitioning....possible to use whole disk for LVM without creating a LVM partition In-Reply-To: References: Message-ID: <457791549.2009821.1425914474927.JavaMail.yahoo@mail.yahoo.com> Hi,From what I remember,it depends on the use of the disk. If its a boot disk, you have to have one DOS boot partition to start the system. However, if the disk is a second disk, then the whole disk can be folded into LVM. Thanks James On Monday, 9 March 2015, 14:18, Jerry Billing wrote: Hi For virtual servers it is nice to usethe whole disk for LVM instead of creating a LVM partition on the disk.Then you can just increase the size of the disk in VMware and later extendthe file system instead of having to add another disk and extend. Is it possible to use this setup inthe kickstart? What syntax do one use if it is possible? If I have done it manually it whouldhave been like this: pvcreate /dev/sdb (instead of usinga LVM partition called /dev/sdb1) vgcreate DataVG /dev/sdb lvcreate -n DataLV -l 100%FREE DataVGDataLV At the moment I have the following partitioningscript in my kickstart file for RHEL6/7 as a pre script: DISK_TYPE=$(parted -s /dev/sda print|grep Model | awk '{print $2}') echo "Disk type = $DISK_TYPE" if [ "$DISK_TYPE" = "VMware"] then echo "This is a VMware server,disk type=$DISK_TYPE" cat > /tmp/partitioning.cfg < /tmp/partitioning.cfg < From simpsonar77 at gmail.com Mon Mar 9 16:55:31 2015 From: simpsonar77 at gmail.com (Andrew Simpson) Date: Mon, 9 Mar 2015 12:55:31 -0400 Subject: Kickstart - Partitioning....possible to use whole disk for LVM without creating a LVM partition In-Reply-To: References: Message-ID: I use kernel options that are set in the grub (i.e. isolinux/syslinux cfg files ) I pass in @vm on the append line, then in the kickstart, I parse /proc/cmdline for all the options. Following that, I check if [[ $"opt_vm" == "1" ]]; then..... i then have each partition size set as a variable ( SIZE_ROOT = 20000, SIZE_VAR = 1024, etc...). otherwise, I have another set of partition sizes. But basically, yes you can setup different partitioning schemes based off of variables in your kickstart. I do this by dumping the partitioning information into a file (pre.ks), which is included via %include /ks/pre.ks at the beginning of the kickstart. Makes it fairly dynamic. Andrew Simpson On Mon, Mar 9, 2015 at 10:02 AM, Jerry Billing wrote: > Hi > > For virtual servers it is nice to use the whole disk for LVM instead of > creating a LVM partition on the disk. Then you can just increase the size > of the disk in VMware and later extend the file system instead of having to > add another disk and extend. > Is it possible to use this setup in the kickstart? What syntax do one use > if it is possible? > > If I have done it manually it whould have been like this: > pvcreate /dev/sdb (instead of using a LVM partition called /dev/sdb1) > vgcreate DataVG /dev/sdb > lvcreate -n DataLV -l 100%FREE DataVG DataLV > > At the moment I have the following partitioning script in my kickstart > file for RHEL6/7 as a pre script: > > DISK_TYPE=$(parted -s /dev/sda print |grep Model | awk '{print $2}') > echo "Disk type = $DISK_TYPE" > > if [ "$DISK_TYPE" = "VMware" ] > > then > echo "This is a VMware server, disk type=$DISK_TYPE" > cat > /tmp/partitioning.cfg < part /boot --fstype="xfs" --size=1024 --ondisk=sda > part pv.01 --size=10240 --grow --ondisk=sda > volgroup VGos pv.01 > logvol / --vgname=VGos --name=LVroot --size=10240 --grow > logvol swap --vgname=VGos --name=LVswap --recommended > part pv.02 --size=1000 --grow --ondisk=sdb > volgroup VGdata pv.02 > logvol /usr/users --vgname=VGdata --name=LVhome --size=20480 > logvol /app --vgname=VGdata --name=LVapp --size=1000 --grow > EOF > > else > echo "This is a Physical server, disk type=$DISK_TYPE" > cat > /tmp/partitioning.cfg < part /boot --fstype="xfs" --size=1024 --ondisk=sda > part pv.01 --size=10240 --grow --ondisk=sda > volgroup VGos pv.01 > logvol / --vgname=VGos --name=LVroot --size=10240 --grow > logvol swap --vgname=VGos --name=LVswap --recommended > logvol /var --vgname=VGos --name=LVvar --size=20480 > EOF > > fi > > > Regards Jerry > _______________________________________________ > 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 jebi01 at handelsbanken.se Mon Mar 9 20:22:02 2015 From: jebi01 at handelsbanken.se (Jerry Billing) Date: Mon, 9 Mar 2015 21:22:02 +0100 Subject: Kickstart - Partitioning....possible to use whole disk for LVM without creating a LVM partition In-Reply-To: <457791549.2009821.1425914474927.JavaMail.yahoo@mail.yahoo.com> References: <457791549.2009821.1425914474927.JavaMail.yahoo@mail.yahoo.com> Message-ID: Hi My main question was if it is possible to use a whole disk using LVM without creating a seperate LVM partition in kickstart? If you create a partition on the disk you can?t easily extend the disk by increasing the disk size in VMware. Then you have to add another disk and extend your volume group. If you use the whole disk by initialize the disk using "pvcreate /dev/disk", it can easily be resized. I am not an expert on LVM so please correct me if I am wrong :) Is it possible to use standard LVM commands in kickstart? As I understand you can just use part and logvol? By reading the manuls for theese commands I cannot find a solution for this. I use the following commands in my kickstart file, and the partitioning script I presented in my first mail is included in the kickstart using the %include statement below. zerombr clearpart --all bootloader --location=mbr --boot-drive=sda %include /tmp/partitioning.cfg By the way we are running Satellite 5.7. Regards Jerry From: James Harrison To: Discussion list about Kickstart , Cc: Anette Hagelin Date: 2015-03-09 16:29 Subject: Re: Kickstart - Partitioning....possible to use whole disk for LVM without creating a LVM partition Sent by: kickstart-list-bounces at redhat.com Hi, >From what I remember,it depends on the use of the disk. If its a boot disk, you have to have one DOS boot partition to start the system. However, if the disk is a second disk, then the whole disk can be folded into LVM. Thanks James On Monday, 9 March 2015, 14:18, Jerry Billing wrote: Hi For virtual servers it is nice to use the whole disk for LVM instead of creating a LVM partition on the disk. Then you can just increase the size of the disk in VMware and later extend the file system instead of having to add another disk and extend. Is it possible to use this setup in the kickstart? What syntax do one use if it is possible? If I have done it manually it whould have been like this: pvcreate /dev/sdb (instead of using a LVM partition called /dev/sdb1) vgcreate DataVG /dev/sdb lvcreate -n DataLV -l 100%FREE DataVG DataLV At the moment I have the following partitioning script in my kickstart file for RHEL6/7 as a pre script: DISK_TYPE=$(parted -s /dev/sda print |grep Model | awk '{print $2}') echo "Disk type = $DISK_TYPE" if [ "$DISK_TYPE" = "VMware" ] then echo "This is a VMware server, disk type=$DISK_TYPE" cat > /tmp/partitioning.cfg < /tmp/partitioning.cfg < From rvandolson at esri.com Mon Mar 9 21:02:32 2015 From: rvandolson at esri.com (Ray Van Dolson) Date: Mon, 9 Mar 2015 14:02:32 -0700 Subject: Kickstart - Partitioning....possible to use whole disk for LVM without creating a LVM partition In-Reply-To: References: <457791549.2009821.1425914474927.JavaMail.yahoo@mail.yahoo.com> Message-ID: <20150309210232.GA7495@esri.com> On Mon, Mar 09, 2015 at 09:22:02PM +0100, Jerry Billing wrote: > Hi > > My main question was if it is possible to use a whole disk using LVM without > creating a seperate LVM partition in kickstart? If you create a partition on > the disk you can?t easily extend the disk by increasing the disk size in > VMware. Then you have to add another disk and extend your volume group. > If you use the whole disk by initialize the disk using "pvcreate /dev/disk", it > can easily be resized. I am not an expert on LVM so please correct me if I am > wrong :) You should still be able to expand relatively easily: - Expand the disk as you normally would in VMware, then use parted to expand the LVM partition. - Add another virtual disk and introduce it as a new PV into your VG and expand that way. > Is it possible to use standard LVM commands in kickstart? As I understand you > can just use part and logvol? By reading the manuls for theese commands I > cannot find a solution for this. > > I use the following commands in my kickstart file, and the partitioning script > I presented in my first mail is included in the kickstart using the %include > statement below. > > zerombr > clearpart --all > bootloader --location=mbr --boot-drive=sda > %include /tmp/partitioning.cfg > > By the way we are running Satellite 5.7. > > Regards Jerry Ray From petro at cpetro.us Mon Mar 16 17:12:39 2015 From: petro at cpetro.us (Christopher Petro) Date: Mon, 16 Mar 2015 11:12:39 -0600 Subject: I need to build a couple modules into an ISO Message-ID: My team has around 450 servers (and increasing) distributed around the US in batches of 2 to 12 servers, and we install/reinstall them by uploading a ISO into "vflash" (or mounting via NFS/HTTP over the OOB interface. PXE is not really an option) and then telling the hardware to boot off that. We are using Intel 10G ethernet cards that use the ixgbe driver, but the one built into RHEL6.x doesn't work so we need to use the kmod-ixgbe ( see https://rhn.redhat.com/errata/RHEA-2011-1347.html ) We usually install our servers in batches of 7 to 15, so we prefer to automate the process as much as possible (mounting a driver disk is problematic in our environment). Thus I would like to build this into the kickstart initrd or image.img (or wherever) so that the interfaces can be lit up (additional problem, we're using bonding) during install. One way I have thought of doing this is to unpackage the RPM (rpm2cpio) and manually ifup the interface, but that would be sort ugly. Any suggestions or pointers to documents? Regards, Petro. :wq -------------- next part -------------- An HTML attachment was scrubbed... URL: From spikewhitetx at gmail.com Wed Mar 18 01:26:00 2015 From: spikewhitetx at gmail.com (Spike White) Date: Tue, 17 Mar 2015 20:26:00 -0500 Subject: Kickstart-list Digest, Vol 130, Issue 3 In-Reply-To: References: Message-ID: This URL you posted seems to indicate this is a RHEL 6.1-specific problem. Have you tried a more recent RHEL6 version? We boot just fine off 10 GbE-capable ethernet cards (X520s or X540s). We image to RHEL 6.3 and 6.5. The *only* quirkness I've seen w/ this ixgbe / Intel 10 GbE NIC combo is if the switch port is configured for 1 GbE. Then the card seems to take a while to auto-neg down to 1 GbE. So we have to put a link delay in the ifcfg-eth* file. And all is good. I believe the syntax is: LINKDELAY=10 or some such. We never experienced this problem when kickstarting. But even if we had, I believe there's equiv syntax in the ks.cfg to do this. If the switch port is set to 10 GbE, I've seen no quirkness on the RHEL 6.3 or 6.5 ixgbe driver. And we've imaged hundred of servers at this point to RHEL 6.3 or 6.5, all with Intel NICs. Long ago, I had a similar problem on SLES 10, I had to crack open the boot media and put in a more recent raid controller driver. That was when vmlinuz was in the old format; I wouldn't know how to do that now. And even back then, it was quite painful. That's why popping up your RHEL 6.x version seems to be an easier fix. Spike On Tue, Mar 17, 2015 at 11:00 AM, wrote: > Send Kickstart-list mailing list submissions to > kickstart-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/kickstart-list > or, via email, send a message with subject or body 'help' to > kickstart-list-request at redhat.com > > You can reach the person managing the list at > kickstart-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Kickstart-list digest..." > > Today's Topics: > > 1. I need to build a couple modules into an ISO (Christopher Petro) > > > ---------- Forwarded message ---------- > From: Christopher Petro > To: kickstart-list at redhat.com > Cc: > Date: Mon, 16 Mar 2015 11:12:39 -0600 > Subject: I need to build a couple modules into an ISO > My team has around 450 servers (and increasing) distributed around the US > in batches of 2 to 12 servers, and we install/reinstall them by uploading a > ISO into "vflash" (or mounting via NFS/HTTP over the OOB interface. PXE is > not really an option) and then telling the hardware to boot off that. > > We are using Intel 10G ethernet cards that use the ixgbe driver, but the > one built into RHEL6.x doesn't work so we need to use the kmod-ixgbe ( see > https://rhn.redhat.com/errata/RHEA-2011-1347.html ) > > We usually install our servers in batches of 7 to 15, so we prefer to > automate the process as much as possible (mounting a driver disk is > problematic in our environment). > > Thus I would like to build this into the kickstart initrd or image.img (or > wherever) so that the interfaces can be lit up (additional problem, we're > using bonding) during install. > > One way I have thought of doing this is to unpackage the RPM (rpm2cpio) > and manually ifup the interface, but that would be sort ugly. > > Any suggestions or pointers to documents? > > Regards, > Petro. > :wq > > > _______________________________________________ > 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 petro at cpetro.us Wed Mar 18 02:58:06 2015 From: petro at cpetro.us (Petro) Date: Tue, 17 Mar 2015 20:58:06 -0600 Subject: Kickstart-list Digest, Vol 130, Issue 3 In-Reply-To: References: Message-ID: <5508E9BE.4050801@cpetro.us> On 15/3/17 7:26 PM, Spike White wrote: > This URL you posted seems to indicate this is a RHEL 6.1-specific > problem. > > Have you tried a more recent RHEL6 version? We boot just fine off 10 > GbE-capable ethernet cards (X520s or X540s). We image to RHEL 6.3 and 6.5. I'm working with 6.5 and now 6.6. I'm not PXE booting, or "booting off the card" (we have a huge and hugely complex network. Getting the PXE helper set up and maintained across the network Aegean Stables level of work.). I'll be checking again tomorrow, but the stock ixgbe driver doesn't seem to come up (another problem not mentioned in my first email is that we're using bonding). I can get the network configured, but the interfaces aren't up. I'll try again tomorrow. > If the switch port is set to 10 GbE, I've seen no quirkness on the > RHEL 6.3 or 6.5 ixgbe driver. And we've imaged hundred of servers at > this point to RHEL 6.3 or 6.5, all with Intel NICs. We also routinely go straight in to routers--these servers will push 20Gb (well, about 17.5 for the bond. After that stuff starts getting problematic). Anyway, I'll try again with the stock driver and see if it will do the needful, but it hasn't so far. Regards, Petro. :wq