From member at linkedin.com Tue Jan 4 05:51:31 2011 From: member at linkedin.com (Nauman yousuf via LinkedIn) Date: Tue, 4 Jan 2011 05:51:31 +0000 (UTC) Subject: Nauman yousuf wants to stay in touch on LinkedIn Message-ID: <739238325.54722248.1294120291015.JavaMail.app@ela4-bed35.prod> LinkedIn ------------Nauman yousuf requested to add you as a connection on LinkedIn: ------------------------------------------ prasad, I'd like to add you to my professional network on LinkedIn. - Nauman yousuf Accept invitation from Nauman yousuf http://www.linkedin.com/e/gqo4xa-giidt39a-6r/uDOOeOoBcDnu7cRsgtmHGao4wzLdPX8f936x8gS/blk/I37992535_25/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_dj9vdjcRczAVdPd9bS93dQRUjmpMbPwMc3sOejgUc38LrCBxbOYWrSlI/EML_comm_afe/ View invitation from Nauman yousuf http://www.linkedin.com/e/gqo4xa-giidt39a-6r/uDOOeOoBcDnu7cRsgtmHGao4wzLdPX8f936x8gS/blk/I37992535_25/0RcBYRcPkOejATcQALqnpPbOYWrSlI/svi/ ------------------------------------------ DID YOU KNOW LinkedIn can help you find the right service providers using recommendations from your trusted network? Using LinkedIn Services, you can take the risky guesswork out of selecting service providers by reading the recommendations of credible, trustworthy members of your network. http://www.linkedin.com/e/gqo4xa-giidt39a-6r/svp/inv-25/ -- (c) 2010, LinkedIn Corporation -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtheisen at nexcess.net Thu Jan 13 01:27:58 2011 From: dtheisen at nexcess.net (Daniel Theisen) Date: Wed, 12 Jan 2011 20:27:58 -0500 Subject: Static IP on Kickstart Message-ID: <20110112202758.91b133d8.dtheisen@nexcess.net> Hello all, I've been struggling with an issue with my kickstart configuration for a while now. My current installation procedure: 1. Insert kickstart CD into server and boot 2. Select which kickstart to config from menu 3. Server grabs a DHCP address off a local LAN, gets install data off of a local mirror 4. Coffee while it installs 5. Server reboots 6. Log in and manually run network configuration script (written in %post section) to configure new static IP What I would like to do is move step 6 to after step 4. I want to be able to run some kind of network installation at the very end of the install process, but before the first reboot. Our current situation is this. We do server installs on a daily basis, when we kickstart a machine, we plug it into our office VLAN and boot it. It then grabs a DHCP address from our office router and proceeds with a network installation. Setting a static IP at the beginning of the install is not an option, because we have many different VLAN's for each of our subnets. Some of the VLAN's are offsite and going to our othr site to install a server is not ideal. Static DHCP is also not an option for multiple reasons. Firtly, we have over 1000 servers already configured with static IP addresses. Although there's no conflict issues, we'd just like to keep IP addresses purely static for consistancy reasons. Secondly, there's the previous VLAN issue. Finally, there's the issue that we have some servers with 20+ IP addresses. Baasically, it'd just be very nice to be able to configure a static IP address on a server during the actual install process. Here is my current kickstart script: auth --useshadow --enablemd5 bootloader --location=mbr zerombr clearpart --all --initlabel text firewall --enabled --port=22:tcp firstboot --disable keyboard us lang en_US logging --level=info url --url=http://mirror.nexcess.net/CentOS/5.5/os/x86_64/ reboot --eject rootpw --iscrypted xx selinux --enforcing skipx timezone --isUtc America/Detroit install part /boot --bytes-per-inode=4096 --fstype="ext3" --size=512 --ondisk=sda part swap --bytes-per-inode=4096 --fstype="swap" --size=2048 --ondisk=sda part / --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sda part /backup --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sdb network --bootproto=dhcp --device=eth0 %packages --nobase @core system-config-network-tui %post echo "nameserver 4.2.2.1" > /etc/resolv.conf echo "nameserver 8.8.8.8" >> /etc/resolv.conf # write netconfig script cat << EOF > /bin/netconfig #!/bin/bash # check if user is root if [[ \$EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1 fi # run system-config-network-tui /usr/sbin/system-config-network-tui # set variables eth0f="/etc/sysconfig/network-scripts/ifcfg-eth0" eth1f="/etc/sysconfig/network-scripts/ifcfg-eth1" netcfg="/etc/sysconfig/network" # turn on eth1 if it has an address, remove gateway.. shouldn't be set here # anyways if [ -f "\$eth1f" ]; then if grep -q "IPADDR" \$eth1f; then sed -i 's/ONBOOT=no/ONBOOT=yes/' \$eth1f sed -i '/^GATEWAY/d' \$eth1f sed -i '/^HOTPLUG/d' \$eth1f fi fi # move gateway from ifcfg-eth0 to /etc/sysconfig/network if [ -f "\$eth0f" ]; then e0gw=\$(grep "GATEWAY" \$eth0f) sed -i '/^GATEWAY/d' \$eth0f # check to see if the gateway is already set. if it is, delete it first if ! grep -q "GATEWAY" /etc/sysconfig/network; then echo \$e0gw >> \$netcfg else sed -i '/^GATEWAY/d' \$netcfg echo \$e0gw >> \$netcfg fi fi EOF chmod +x /bin/netconfig At the moment, I have a not-so-elegant script written to the server to be run manually after install. I began using system-config-network-tui vanilla, but realized it had some differences from the network configuration tool in anaconda (net.c?) I tried my best to correct those differences with my netconfig script. I've already tried running system-config-network-tui in the %post section, but it doesn't seem to work. If anyone has had experience in dealing with a scenario such as this, any help would be greatly appreciated. Thanks, Daniel Theisen From mad at comsoft.de Thu Jan 13 15:36:13 2011 From: mad at comsoft.de (mad) Date: Thu, 13 Jan 2011 16:36:13 +0100 Subject: --gid??? Message-ID: <201101131636.13637.mad@comsoft.de> Hi! When using the option 'user' I can choose additional groups with '--groups'. But is there a possibility to set the initial group of the user? Like '--gid' with 'useradd'? Thanks, mad From feng.tan at oracle.com Thu Jan 13 15:47:03 2011 From: feng.tan at oracle.com (feng.tan at oracle.com) Date: Thu, 13 Jan 2011 07:47:03 -0800 (PST) Subject: Auto Reply: --gid??? Message-ID: <60aa9639-eaa1-4374-a12c-53531c7d3843@default> ???????????????? Dear Sender, >From Jan. 13 ~ Jan. 14, I am in Vacation, if you have any query about the package transport, please contact Carson, mailto:carson.zhu at oracle.com If there is any urgent case, you can reach me at 135-010-88029 Thanks, Tan Feng From feng.tan at oracle.com Thu Jan 13 15:58:39 2011 From: feng.tan at oracle.com (feng.tan at oracle.com) Date: Thu, 13 Jan 2011 07:58:39 -0800 (PST) Subject: Auto Reply: Auto Reply: --gid??? Message-ID: <9f3feca2-db5b-4356-9cc6-a31b26144ccd@default> ???????????????? Dear Sender, >From Jan. 13 ~ Jan. 14, I am in Vacation, if you have any query about the package transport, please contact Carson, mailto:carson.zhu at oracle.com If there is any urgent case, you can reach me at 135-010-88029 Thanks, Tan Feng From bluethundr at gmail.com Sun Jan 16 05:49:43 2011 From: bluethundr at gmail.com (bluethundr) Date: Sun, 16 Jan 2011 00:49:43 -0500 Subject: trying to create dirs in kickstart Message-ID: hello kickstart! I am attempting to creating some mount points on the machines I kickstart and then mount those volumes using the mount command in teh %post section of my ks file. But that part of the kickstart isn't working. # Kickstart file automatically generated by anaconda. install # Use NFS installation media nfs --server=192.168.1.250 --dir=/mnt/DVD64-1 lang en_US.UTF-8 network --device eth0 --bootproto dhcp --nameserver 192.168.1.44,71.250.0.12,4.2.2.2 --hostname newhost rootpw --iscrypted $1$ptZMQiFw$hYQMhYk0XdOexGpc.bVWH/ firewall --enabled --port=22:tcp,80:tcp authconfig --enableshadow --enablemd5 selinux --disabled timezone America/New_York bootloader --location=mbr --driveorder=xvda --append="console=xvc0" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --initlabel part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=272 --grow --maxsize=544 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow %post # Create mount dir mkdir /mnt/config # Mount config dir mount nas.summitnjhome.com:/mnt/nas/config /mnt/config # transfer files rsync -avzp /mnt/config/etc/* /etc/ # Add repos # EPEL rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm # Remi rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-5.rpm # DAG rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS//rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm # CentALT rpm -Uvh http://centos.alt.ru/pub/repository/centos/5/i386/centalt-release-5-3.noarch.rpm # unmount config dir umount /mnt/config # remove config dir rm -rf /mnt/config #update the system yum repolist yum update -y yum upgrade -y %packages @base @cluster-storage @clustering @core @editors @legacy-network-server @mail-server @network-server @news-server @server-cfg @text-internet @web-server @smb-server koan puppet keyutils trousers fipscheck device-mapper-multipath kmod-gnbd-xen kmod-gfs-xen Could someone offer some advice? thanks! -- GPG me!! gpg --keyserver pgp.mit.edu --recv-keys F186197B From jamesaharrisonuk at yahoo.co.uk Sun Jan 16 12:08:13 2011 From: jamesaharrisonuk at yahoo.co.uk (jamesaharrisonuk at yahoo.co.uk) Date: Sun, 16 Jan 2011 12:08:13 +0000 Subject: trying to create dirs in kickstart In-Reply-To: References: Message-ID: <1347264540-1295179693-cardhu_decombobulator_blackberry.rim.net-702986227-@bda2469.bisx.prod.on.blackberry> Hi. Have you tried using the IP address of your nas.summitnjhome.com device? In my experience the IP address will always work. James Sent from my Verizon Wireless BlackBerry -----Original Message----- From: bluethundr Sender: kickstart-list-bounces at redhat.com Date: Sun, 16 Jan 2011 00:49:43 To: Reply-To: Discussion list about Kickstart Subject: trying to create dirs in kickstart hello kickstart! I am attempting to creating some mount points on the machines I kickstart and then mount those volumes using the mount command in teh %post section of my ks file. But that part of the kickstart isn't working. # Kickstart file automatically generated by anaconda. install # Use NFS installation media nfs --server=192.168.1.250 --dir=/mnt/DVD64-1 lang en_US.UTF-8 network --device eth0 --bootproto dhcp --nameserver 192.168.1.44,71.250.0.12,4.2.2.2 --hostname newhost rootpw --iscrypted $1$ptZMQiFw$hYQMhYk0XdOexGpc.bVWH/ firewall --enabled --port=22:tcp,80:tcp authconfig --enableshadow --enablemd5 selinux --disabled timezone America/New_York bootloader --location=mbr --driveorder=xvda --append="console=xvc0" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --initlabel part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=272 --grow --maxsize=544 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow %post # Create mount dir mkdir /mnt/config # Mount config dir mount nas.summitnjhome.com:/mnt/nas/config /mnt/config # transfer files rsync -avzp /mnt/config/etc/* /etc/ # Add repos # EPEL rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm # Remi rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-5.rpm # DAG rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS//rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm # CentALT rpm -Uvh http://centos.alt.ru/pub/repository/centos/5/i386/centalt-release-5-3.noarch.rpm # unmount config dir umount /mnt/config # remove config dir rm -rf /mnt/config #update the system yum repolist yum update -y yum upgrade -y %packages @base @cluster-storage @clustering @core @editors @legacy-network-server @mail-server @network-server @news-server @server-cfg @text-internet @web-server @smb-server koan puppet keyutils trousers fipscheck device-mapper-multipath kmod-gnbd-xen kmod-gfs-xen Could someone offer some advice? thanks! -- GPG me!! gpg --keyserver pgp.mit.edu --recv-keys F186197B _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From chris.rouch at gmail.com Mon Jan 17 11:14:36 2011 From: chris.rouch at gmail.com (Chris Rouch) Date: Mon, 17 Jan 2011 12:14:36 +0100 Subject: trying to create dirs in kickstart In-Reply-To: <1347264540-1295179693-cardhu_decombobulator_blackberry.rim.net-702986227-@bda2469.bisx.prod.on.blackberry> References: <1347264540-1295179693-cardhu_decombobulator_blackberry.rim.net-702986227-@bda2469.bisx.prod.on.blackberry> Message-ID: On 16 January 2011 13:08, wrote: > Hi. > Have you tried using the IP address of your ?nas.summitnjhome.com device? In my experience the IP address will always work. I have this in my %post mkdir -p /mnt/source /bin/mount -o nolock -t nfs 192.168.6.7:/data/distros/f14/cdrom /mnt/source This also works for f13. I think i tried without the "-o nolock" option on f13 and it failed. Regards, Chris > > James > Sent from my Verizon Wireless BlackBerry > > -----Original Message----- > From: bluethundr > Sender: kickstart-list-bounces at redhat.com > Date: Sun, 16 Jan 2011 00:49:43 > To: > Reply-To: Discussion list about Kickstart > Subject: trying to create dirs in kickstart > > hello kickstart! > > ?I am attempting to creating some mount points on the machines I > kickstart and then mount those volumes using the mount command in teh > %post section of my ks file. But that part of the kickstart isn't > working. > > # Kickstart file automatically generated by anaconda. > > install > # Use NFS installation media > nfs --server=192.168.1.250 --dir=/mnt/DVD64-1 > lang en_US.UTF-8 > network --device eth0 --bootproto dhcp --nameserver > 192.168.1.44,71.250.0.12,4.2.2.2 --hostname newhost > rootpw --iscrypted $1$ptZMQiFw$hYQMhYk0XdOexGpc.bVWH/ > firewall --enabled --port=22:tcp,80:tcp > authconfig --enableshadow --enablemd5 > selinux --disabled > timezone America/New_York > bootloader --location=mbr --driveorder=xvda --append="console=xvc0" > # The following is the partition information you requested > # Note that any partitions you deleted are not expressed > # here so unless you clear all partitions first, this is > # not guaranteed to work > clearpart --all --initlabel > part /boot --fstype ext3 --size=100 --ondisk=xvda > part pv.2 --size=0 --grow --ondisk=xvda > volgroup VolGroup00 --pesize=32768 pv.2 > logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 > --size=272 --grow --maxsize=544 > logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow > > %post > # Create mount dir > mkdir /mnt/config > > # Mount config dir > mount nas.summitnjhome.com:/mnt/nas/config /mnt/config > > # transfer files > rsync -avzp /mnt/config/etc/* /etc/ > > # Add repos > # EPEL > rpm -Uvh http://download.fedora.redhat.com/pub/epel/5/i386/epel-release-5-4.noarch.rpm > > # Remi > rpm -Uvh http://rpms.famillecollet.com/enterprise/remi-release-5.rpm > > # DAG > rpm -Uhv http://apt.sw.be/redhat/el5/en/x86_64/rpmforge/RPMS//rpmforge-release-0.3.6-1.el5.rf.x86_64.rpm > > # CentALT > rpm -Uvh http://centos.alt.ru/pub/repository/centos/5/i386/centalt-release-5-3.noarch.rpm > > # unmount config dir > umount /mnt/config > > # remove config dir > rm -rf /mnt/config > > #update the system > yum repolist > yum update -y > yum upgrade -y > > > %packages > @base > @cluster-storage > @clustering > @core > @editors > @legacy-network-server > @mail-server > @network-server > @news-server > @server-cfg > @text-internet > @web-server > @smb-server > koan > puppet > keyutils > trousers > fipscheck > device-mapper-multipath > kmod-gnbd-xen > kmod-gfs-xen > > Could someone offer some advice? > > thanks! > > -- > GPG me!! > > gpg --keyserver pgp.mit.edu --recv-keys F186197B > > _______________________________________________ > 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 > From rvandolson at esri.com Tue Jan 18 19:49:20 2011 From: rvandolson at esri.com (Ray Van Dolson) Date: Tue, 18 Jan 2011 11:49:20 -0800 Subject: RHEL6, kickstart, rootpw and interactive Message-ID: <20110118194919.GA15053@esri.com> Creating a kickstart for RHEL6 and am using "interactive" mode (though I'm not sure if this is an allowed keyword any longer...). We are pre defining a default root password as follows: authconfig --enableshadow --passalgo=md5 rootpw --iscrypted $1$bMbfjfHm$en8pkGIBBERISHyBGIBwx/ But in the graphical, stage 2 installer when we get to the root password dialog, the dialog is blank and we're forced to enter a password in. Obviously, Anaconda can't derive from the PW hash what the real password provided to rootpw is, but it should give a way to continue on past this dialog if a default password has been given to rootpw. The user should be able to override or change it if they like... This is how it used to work with RHEL5's installer -- am I doing something wrong or misunderstanding a change? Thanks, Ray From rvandolson at esri.com Tue Jan 18 20:15:23 2011 From: rvandolson at esri.com (Ray Van Dolson) Date: Tue, 18 Jan 2011 12:15:23 -0800 Subject: RHEL6, kickstart, rootpw and interactive In-Reply-To: <20110118194919.GA15053@esri.com> References: <20110118194919.GA15053@esri.com> Message-ID: <20110118201522.GA16769@esri.com> On Tue, Jan 18, 2011 at 11:49:20AM -0800, Ray Van Dolson wrote: > Creating a kickstart for RHEL6 and am using "interactive" mode (though > I'm not sure if this is an allowed keyword any longer...). We are pre > defining a default root password as follows: > > authconfig --enableshadow --passalgo=md5 > rootpw --iscrypted $1$bMbfjfHm$en8pkGIBBERISHyBGIBwx/ > > But in the graphical, stage 2 installer when we get to the root > password dialog, the dialog is blank and we're forced to enter a > password in. > > Obviously, Anaconda can't derive from the PW hash what the real > password provided to rootpw is, but it should give a way to continue on > past this dialog if a default password has been given to rootpw. The > user should be able to override or change it if they like... > > This is how it used to work with RHEL5's installer -- am I doing > something wrong or misunderstanding a change? After poking around in the Anaconda sources a bit -- in RHEL6 we have: # we might have a root password already if not self.rootPassword['isCrypted']: self.pw.set_text(self.rootPassword['password']) self.confirm.set_text(self.rootPassword['password']) And in RHEL5: # check if we already have a crypted password from kickstart if self.rootPassword["isCrypted"]: return None (These are both in account_gui.py). So the behavior I'm seeing makes sense, however it would be nice to handle a default password that is crypted as well. Ray From chip.shabazian at bankofamerica.com Tue Jan 18 23:21:03 2011 From: chip.shabazian at bankofamerica.com (Shabazian, Chip) Date: Tue, 18 Jan 2011 17:21:03 -0600 Subject: Static IP on Kickstart In-Reply-To: <20110112202758.91b133d8.dtheisen@nexcess.net> References: <20110112202758.91b133d8.dtheisen@nexcess.net> Message-ID: <2FA17BA1CC9A9B408927E72E9FA4A1ED0124EBA531@ex2k.bankofamerica.com> You could put the static info on the boot: line, then source it and use it in the %post. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Daniel Theisen Sent: Wednesday, January 12, 2011 5:28 PM To: kickstart-list at redhat.com Subject: Static IP on Kickstart Hello all, I've been struggling with an issue with my kickstart configuration for a while now. My current installation procedure: 1. Insert kickstart CD into server and boot 2. Select which kickstart to config from menu 3. Server grabs a DHCP address off a local LAN, gets install data off of a local mirror 4. Coffee while it installs 5. Server reboots 6. Log in and manually run network configuration script (written in %post section) to configure new static IP What I would like to do is move step 6 to after step 4. I want to be able to run some kind of network installation at the very end of the install process, but before the first reboot. Our current situation is this. We do server installs on a daily basis, when we kickstart a machine, we plug it into our office VLAN and boot it. It then grabs a DHCP address from our office router and proceeds with a network installation. Setting a static IP at the beginning of the install is not an option, because we have many different VLAN's for each of our subnets. Some of the VLAN's are offsite and going to our othr site to install a server is not ideal. Static DHCP is also not an option for multiple reasons. Firtly, we have over 1000 servers already configured with static IP addresses. Although there's no conflict issues, we'd just like to keep IP addresses purely static for consistancy reasons. Secondly, there's the previous VLAN issue. Finally, there's the issue that we have some servers with 20+ IP addresses. Baasically, it'd just be very nice to be able to configure a static IP address on a server during the actual install process. Here is my current kickstart script: auth --useshadow --enablemd5 bootloader --location=mbr zerombr clearpart --all --initlabel text firewall --enabled --port=22:tcp firstboot --disable keyboard us lang en_US logging --level=info url --url=http://mirror.nexcess.net/CentOS/5.5/os/x86_64/ reboot --eject rootpw --iscrypted xx selinux --enforcing skipx timezone --isUtc America/Detroit install part /boot --bytes-per-inode=4096 --fstype="ext3" --size=512 --ondisk=sda part swap --bytes-per-inode=4096 --fstype="swap" --size=2048 --ondisk=sda part / --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sda part /backup --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sdb network --bootproto=dhcp --device=eth0 %packages --nobase @core system-config-network-tui %post echo "nameserver 4.2.2.1" > /etc/resolv.conf echo "nameserver 8.8.8.8" >> /etc/resolv.conf # write netconfig script cat << EOF > /bin/netconfig #!/bin/bash # check if user is root if [[ \$EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1 fi # run system-config-network-tui /usr/sbin/system-config-network-tui # set variables eth0f="/etc/sysconfig/network-scripts/ifcfg-eth0" eth1f="/etc/sysconfig/network-scripts/ifcfg-eth1" netcfg="/etc/sysconfig/network" # turn on eth1 if it has an address, remove gateway.. shouldn't be set here # anyways if [ -f "\$eth1f" ]; then if grep -q "IPADDR" \$eth1f; then sed -i 's/ONBOOT=no/ONBOOT=yes/' \$eth1f sed -i '/^GATEWAY/d' \$eth1f sed -i '/^HOTPLUG/d' \$eth1f fi fi # move gateway from ifcfg-eth0 to /etc/sysconfig/network if [ -f "\$eth0f" ]; then e0gw=\$(grep "GATEWAY" \$eth0f) sed -i '/^GATEWAY/d' \$eth0f # check to see if the gateway is already set. if it is, delete it first if ! grep -q "GATEWAY" /etc/sysconfig/network; then echo \$e0gw >> \$netcfg else sed -i '/^GATEWAY/d' \$netcfg echo \$e0gw >> \$netcfg fi fi EOF chmod +x /bin/netconfig At the moment, I have a not-so-elegant script written to the server to be run manually after install. I began using system-config-network-tui vanilla, but realized it had some differences from the network configuration tool in anaconda (net.c?) I tried my best to correct those differences with my netconfig script. I've already tried running system-config-network-tui in the %post section, but it doesn't seem to work. If anyone has had experience in dealing with a scenario such as this, any help would be greatly appreciated. Thanks, Daniel Theisen _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. From wohlgemuth_erik at bah.com Tue Jan 18 23:30:52 2011 From: wohlgemuth_erik at bah.com (Wohlgemuth, Erik [USA]) Date: Tue, 18 Jan 2011 18:30:52 -0500 Subject: Static IP on Kickstart In-Reply-To: <2FA17BA1CC9A9B408927E72E9FA4A1ED0124EBA531@ex2k.bankofamerica.com> References: <20110112202758.91b133d8.dtheisen@nexcess.net> <2FA17BA1CC9A9B408927E72E9FA4A1ED0124EBA531@ex2k.bankofamerica.com> Message-ID: I have a similar situation. The server grabs a DHCP address to begin but in the %post section I have the following line to set a static IP address: network --device eth0 --bootproto=static --ip=1.1.1.1 --netmask=255.255.255.0 --hostname=host I believe this IP address that is set statically is not used until you reboot. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Tuesday, January 18, 2011 6:21 PM To: Discussion list about Kickstart Subject: RE: Static IP on Kickstart You could put the static info on the boot: line, then source it and use it in the %post. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Daniel Theisen Sent: Wednesday, January 12, 2011 5:28 PM To: kickstart-list at redhat.com Subject: Static IP on Kickstart Hello all, I've been struggling with an issue with my kickstart configuration for a while now. My current installation procedure: 1. Insert kickstart CD into server and boot 2. Select which kickstart to config from menu 3. Server grabs a DHCP address off a local LAN, gets install data off of a local mirror 4. Coffee while it installs 5. Server reboots 6. Log in and manually run network configuration script (written in %post section) to configure new static IP What I would like to do is move step 6 to after step 4. I want to be able to run some kind of network installation at the very end of the install process, but before the first reboot. Our current situation is this. We do server installs on a daily basis, when we kickstart a machine, we plug it into our office VLAN and boot it. It then grabs a DHCP address from our office router and proceeds with a network installation. Setting a static IP at the beginning of the install is not an option, because we have many different VLAN's for each of our subnets. Some of the VLAN's are offsite and going to our othr site to install a server is not ideal. Static DHCP is also not an option for multiple reasons. Firtly, we have over 1000 servers already configured with static IP addresses. Although there's no conflict issues, we'd just like to keep IP addresses purely static for consistancy reasons. Secondly, there's the previous VLAN issue. Finally, there's the issue that we have some servers with 20+ IP addresses. Baasically, it'd just be very nice to be able to configure a static IP address on a server during the actual install process. Here is my current kickstart script: auth --useshadow --enablemd5 bootloader --location=mbr zerombr clearpart --all --initlabel text firewall --enabled --port=22:tcp firstboot --disable keyboard us lang en_US logging --level=info url --url=http://mirror.nexcess.net/CentOS/5.5/os/x86_64/ reboot --eject rootpw --iscrypted xx selinux --enforcing skipx timezone --isUtc America/Detroit install part /boot --bytes-per-inode=4096 --fstype="ext3" --size=512 --ondisk=sda part swap --bytes-per-inode=4096 --fstype="swap" --size=2048 --ondisk=sda part / --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sda part /backup --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sdb network --bootproto=dhcp --device=eth0 %packages --nobase @core system-config-network-tui %post echo "nameserver 4.2.2.1" > /etc/resolv.conf echo "nameserver 8.8.8.8" >> /etc/resolv.conf # write netconfig script cat << EOF > /bin/netconfig #!/bin/bash # check if user is root if [[ \$EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1 fi # run system-config-network-tui /usr/sbin/system-config-network-tui # set variables eth0f="/etc/sysconfig/network-scripts/ifcfg-eth0" eth1f="/etc/sysconfig/network-scripts/ifcfg-eth1" netcfg="/etc/sysconfig/network" # turn on eth1 if it has an address, remove gateway.. shouldn't be set here # anyways if [ -f "\$eth1f" ]; then if grep -q "IPADDR" \$eth1f; then sed -i 's/ONBOOT=no/ONBOOT=yes/' \$eth1f sed -i '/^GATEWAY/d' \$eth1f sed -i '/^HOTPLUG/d' \$eth1f fi fi # move gateway from ifcfg-eth0 to /etc/sysconfig/network if [ -f "\$eth0f" ]; then e0gw=\$(grep "GATEWAY" \$eth0f) sed -i '/^GATEWAY/d' \$eth0f # check to see if the gateway is already set. if it is, delete it first if ! grep -q "GATEWAY" /etc/sysconfig/network; then echo \$e0gw >> \$netcfg else sed -i '/^GATEWAY/d' \$netcfg echo \$e0gw >> \$netcfg fi fi EOF chmod +x /bin/netconfig At the moment, I have a not-so-elegant script written to the server to be run manually after install. I began using system-config-network-tui vanilla, but realized it had some differences from the network configuration tool in anaconda (net.c?) I tried my best to correct those differences with my netconfig script. I've already tried running system-config-network-tui in the %post section, but it doesn't seem to work. If anyone has had experience in dealing with a scenario such as this, any help would be greatly appreciated. Thanks, Daniel Theisen _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From dtheisen at nexcess.net Wed Jan 19 01:46:50 2011 From: dtheisen at nexcess.net (Daniel Theisen) Date: Tue, 18 Jan 2011 20:46:50 -0500 Subject: Static IP on Kickstart In-Reply-To: <2FA17BA1CC9A9B408927E72E9FA4A1ED0124EBA531@ex2k.bankofamerica.com> References: <20110112202758.91b133d8.dtheisen@nexcess.net> <2FA17BA1CC9A9B408927E72E9FA4A1ED0124EBA531@ex2k.bankofamerica.com> Message-ID: <20110118204650.94da3693.dtheisen@nexcess.net> This would probably solve the problem, but it'd really defeat the purpose of the install being "hands off." To make matters even worse, I'm using the vesamenu module in anaconda to choose which kickstart file to run. This makes it kind of hard to "implement" your solution. If it really comes down to it, I might have to tinker with anaconda its self. I'd really just like a more beautiful way of fixing this seemingly simple problem. -- Dan Theisen On Tue, 18 Jan 2011 17:21:03 -0600 "Shabazian, Chip" wrote: > You could put the static info on the boot: line, then source it and use it in the %post. > > -----Original Message----- > From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Daniel Theisen > Sent: Wednesday, January 12, 2011 5:28 PM > To: kickstart-list at redhat.com > Subject: Static IP on Kickstart > > Hello all, > I've been struggling with an issue with my kickstart configuration for a while now. > > My current installation procedure: > 1. Insert kickstart CD into server and boot > 2. Select which kickstart to config from menu > 3. Server grabs a DHCP address off a local LAN, gets install data off of a local mirror > 4. Coffee while it installs > 5. Server reboots > 6. Log in and manually run network configuration script (written in %post section) to configure new static IP > > What I would like to do is move step 6 to after step 4. I want to be able to run some kind of network installation at the very end of the install process, but before the first reboot. > > Our current situation is this. We do server installs on a daily basis, when we kickstart a machine, we plug it into our office VLAN and boot it. It then grabs a DHCP address from our office router and proceeds with a network installation. > > Setting a static IP at the beginning of the install is not an option, because we have many different VLAN's for each of our subnets. Some of the VLAN's are offsite and going to our othr site to install a server is not ideal. > > Static DHCP is also not an option for multiple reasons. Firtly, we have over 1000 servers already configured with static IP addresses. Although there's no conflict issues, we'd just like to keep IP addresses purely static for consistancy reasons. Secondly, there's the previous VLAN issue. Finally, there's the issue that we have some servers with 20+ IP addresses. > > Baasically, it'd just be very nice to be able to configure a static IP address on a server during the actual install process. > > Here is my current kickstart script: > > auth --useshadow --enablemd5 > bootloader --location=mbr > zerombr > clearpart --all --initlabel > text > firewall --enabled --port=22:tcp > firstboot --disable > keyboard us > lang en_US > logging --level=info > url --url=http://mirror.nexcess.net/CentOS/5.5/os/x86_64/ > reboot --eject > rootpw --iscrypted xx > selinux --enforcing > skipx > timezone --isUtc America/Detroit > install > > part /boot --bytes-per-inode=4096 --fstype="ext3" --size=512 --ondisk=sda > part swap --bytes-per-inode=4096 --fstype="swap" --size=2048 --ondisk=sda > part / --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sda > part /backup --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sdb > > network --bootproto=dhcp --device=eth0 > > %packages --nobase > @core > system-config-network-tui > > %post > echo "nameserver 4.2.2.1" > /etc/resolv.conf > echo "nameserver 8.8.8.8" >> /etc/resolv.conf > > # write netconfig script > cat << EOF > /bin/netconfig > #!/bin/bash > # check if user is root > if [[ \$EUID -ne 0 ]]; then > echo "This script must be run as root" 1>&2 > exit 1 > fi > # run system-config-network-tui > /usr/sbin/system-config-network-tui > # set variables > eth0f="/etc/sysconfig/network-scripts/ifcfg-eth0" > eth1f="/etc/sysconfig/network-scripts/ifcfg-eth1" > netcfg="/etc/sysconfig/network" > # turn on eth1 if it has an address, remove gateway.. shouldn't be set here > # anyways > if [ -f "\$eth1f" ]; then > if grep -q "IPADDR" \$eth1f; then > sed -i 's/ONBOOT=no/ONBOOT=yes/' \$eth1f > sed -i '/^GATEWAY/d' \$eth1f > sed -i '/^HOTPLUG/d' \$eth1f > fi > fi > # move gateway from ifcfg-eth0 to /etc/sysconfig/network > if [ -f "\$eth0f" ]; then > e0gw=\$(grep "GATEWAY" \$eth0f) > sed -i '/^GATEWAY/d' \$eth0f > # check to see if the gateway is already set. if it is, delete it first > if ! grep -q "GATEWAY" /etc/sysconfig/network; then > echo \$e0gw >> \$netcfg > else > sed -i '/^GATEWAY/d' \$netcfg > echo \$e0gw >> \$netcfg > fi > fi > EOF > chmod +x /bin/netconfig > > At the moment, I have a not-so-elegant script written to the server to be run manually after install. I began using system-config-network-tui vanilla, but realized it had some differences from the network configuration tool in anaconda (net.c?) I tried my best to correct those differences with my netconfig script. I've already tried running system-config-network-tui in the %post section, but it doesn't seem to work. > > If anyone has had experience in dealing with a scenario such as this, any help would be greatly appreciated. > > Thanks, > Daniel Theisen > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > ---------------------------------------------------------------------- > This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. > Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. > The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. > > References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: > http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list -- Daniel Theisen From skebi69 at gmail.com Wed Jan 19 15:52:07 2011 From: skebi69 at gmail.com (John Kennedy) Date: Wed, 19 Jan 2011 15:52:07 +0000 Subject: Static IP on Kickstart In-Reply-To: <20110112202758.91b133d8.dtheisen@nexcess.net> References: <20110112202758.91b133d8.dtheisen@nexcess.net> Message-ID: <4D3708A7.10301@gmail.com> On 01/13/2011 01:27 AM, Daniel Theisen wrote: > Hello all, > I've been struggling with an issue with my kickstart configuration for a while now. > > My current installation procedure: > 1. Insert kickstart CD into server and boot > 2. Select which kickstart to config from menu > 3. Server grabs a DHCP address off a local LAN, gets install data off of a local mirror > 4. Coffee while it installs > 5. Server reboots > 6. Log in and manually run network configuration script (written in %post section) to configure new static IP > > What I would like to do is move step 6 to after step 4. I want to be able to run some kind of network installation at the very end of the install process, but before the first reboot. > > Our current situation is this. We do server installs on a daily basis, when we kickstart a machine, we plug it into our office VLAN and boot it. It then grabs a DHCP address from our office router and proceeds with a network installation. > > Setting a static IP at the beginning of the install is not an option, because we have many different VLAN's for each of our subnets. Some of the VLAN's are offsite and going to our othr site to install a server is not ideal. > > Static DHCP is also not an option for multiple reasons. Firtly, we have over 1000 servers already configured with static IP addresses. Although there's no conflict issues, we'd just like to keep IP addresses purely static for consistancy reasons. Secondly, there's the previous VLAN issue. Finally, there's the issue that we have some servers with 20+ IP addresses. > > Baasically, it'd just be very nice to be able to configure a static IP address on a server during the actual install process. > > Here is my current kickstart script: > > auth --useshadow --enablemd5 > bootloader --location=mbr > zerombr > clearpart --all --initlabel > text > firewall --enabled --port=22:tcp > firstboot --disable > keyboard us > lang en_US > logging --level=info > url --url=http://mirror.nexcess.net/CentOS/5.5/os/x86_64/ > reboot --eject > rootpw --iscrypted xx > selinux --enforcing > skipx > timezone --isUtc America/Detroit > install > > part /boot --bytes-per-inode=4096 --fstype="ext3" --size=512 --ondisk=sda > part swap --bytes-per-inode=4096 --fstype="swap" --size=2048 --ondisk=sda > part / --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sda > part /backup --bytes-per-inode=4096 --fstype="ext3" --grow --size=1 --ondisk=sdb > > network --bootproto=dhcp --device=eth0 > > %packages --nobase > @core > system-config-network-tui > > %post > echo "nameserver 4.2.2.1"> /etc/resolv.conf > echo "nameserver 8.8.8.8">> /etc/resolv.conf > > # write netconfig script > cat<< EOF> /bin/netconfig > #!/bin/bash > # check if user is root > if [[ \$EUID -ne 0 ]]; then > echo "This script must be run as root" 1>&2 > exit 1 > fi > # run system-config-network-tui > /usr/sbin/system-config-network-tui > # set variables > eth0f="/etc/sysconfig/network-scripts/ifcfg-eth0" > eth1f="/etc/sysconfig/network-scripts/ifcfg-eth1" > netcfg="/etc/sysconfig/network" > # turn on eth1 if it has an address, remove gateway.. shouldn't be set here > # anyways > if [ -f "\$eth1f" ]; then > if grep -q "IPADDR" \$eth1f; then > sed -i 's/ONBOOT=no/ONBOOT=yes/' \$eth1f > sed -i '/^GATEWAY/d' \$eth1f > sed -i '/^HOTPLUG/d' \$eth1f > fi > fi > # move gateway from ifcfg-eth0 to /etc/sysconfig/network > if [ -f "\$eth0f" ]; then > e0gw=\$(grep "GATEWAY" \$eth0f) > sed -i '/^GATEWAY/d' \$eth0f > # check to see if the gateway is already set. if it is, delete it first > if ! grep -q "GATEWAY" /etc/sysconfig/network; then > echo \$e0gw>> \$netcfg > else > sed -i '/^GATEWAY/d' \$netcfg > echo \$e0gw>> \$netcfg > fi > fi > EOF > chmod +x /bin/netconfig > > At the moment, I have a not-so-elegant script written to the server to be run manually after install. I began using system-config-network-tui vanilla, but realized it had some differences from the network configuration tool in anaconda (net.c?) I tried my best to correct those differences with my netconfig script. I've already tried running system-config-network-tui in the %post section, but it doesn't seem to work. > > If anyone has had experience in dealing with a scenario such as this, any help would be greatly appreciated. > > Thanks, > Daniel Theisen > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list There is an undocumented option to the bootproto directive called query. This will pause the kickstart process and ask you for the network info. This happens just after the kickstart process starts. Another option would be to configure DHCP to set static IP addresses. It would be an extra step in the configuration process but takes out the need to configure network info. John -- John Kennedy From gianluca.varenni at gmail.com Wed Jan 19 22:05:10 2011 From: gianluca.varenni at gmail.com (Gianluca Varenni) Date: Wed, 19 Jan 2011 14:05:10 -0800 Subject: help with network configuration Message-ID: <001c01cbb824$f1c27ea0$d5477be0$@gmail.com> Hello all. Is there a way in the kickstart configuration file to tell anaconda to configure the network interfaces with some parameters (e.g. DHCP vs static IP, onboot.) but do *not* bring them up during installation (so in practice just write the ifcfg-ethX files)? I tried with network --bootproto=dhcp --device=eth0 --onboot=on -hostname=myhost but the problem is that during the installation it tries to bring eth0 up and get the IP address (eventually timing out). If I don't put that line in the kickstart file, all the interfaces are silently configured for DHCP and onboot=yes, and the hostname is not configured. Thanks! Have a nice day GV -------------- next part -------------- An HTML attachment was scrubbed... URL: From Moray.Henderson at ict-software.org Fri Jan 21 16:26:08 2011 From: Moray.Henderson at ict-software.org (Moray Henderson) Date: Fri, 21 Jan 2011 16:26:08 +0000 Subject: help with network configuration In-Reply-To: <001c01cbb824$f1c27ea0$d5477be0$@gmail.com> References: <001c01cbb824$f1c27ea0$d5477be0$@gmail.com> Message-ID: <000001cbb987$e9893d00$bc9bb700$@Henderson@ict-software.org> From: Gianluca Varenni [mailto:gianluca.varenni at gmail.com] Is there a way in the kickstart configuration file to tell anaconda to configure the network interfaces with some parameters (e.g. DHCP vs static IP, onboot?) but do *not* bring them up during installation (so in practice just write the ifcfg-ethX files)? I tried with network --bootproto=dhcp --device=eth0 --onboot=on ?hostname=myhost but the problem is that during the installation it tries to bring eth0 up and get the IP address (eventually timing out). If I don?t put that line in the kickstart file, all the interfaces are silently configured for DHCP and onboot=yes, and the hostname is not configured. Don?t configure the network in the kickstart and write the hostname configuration from the %post section; or configure a dummy IP with the network option then edit the network configuration in %post? Moray. "To err is human. To purr, feline" -------------- next part -------------- An HTML attachment was scrubbed... URL: From gianluca.varenni at gmail.com Fri Jan 21 19:00:30 2011 From: gianluca.varenni at gmail.com (Gianluca Varenni) Date: Fri, 21 Jan 2011 11:00:30 -0800 Subject: help with network configuration In-Reply-To: <000001cbb987$e9893d00$bc9bb700$@Henderson@ict-software.org> References: <001c01cbb824$f1c27ea0$d5477be0$@gmail.com> <000001cbb987$e9893d00$bc9bb700$@Henderson@ict-software.org> Message-ID: <008c01cbb99d$7a215540$6e63ffc0$@gmail.com> That's what I ended up doing. I change the host name in /etc/hosts and /etc/sysconfig/network, and I manually reconfigure ethX by playing with the /etc/sysconfig/network-scripts/ifcfg-ethX files. Everything is done in a %post section. I just wished there was an easier way to configure networking in the kickstart configuration file. Have a nice day GV From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Moray Henderson Sent: Friday, January 21, 2011 8:26 AM To: 'Discussion list about Kickstart' Subject: RE: help with network configuration From: Gianluca Varenni [mailto:gianluca.varenni at gmail.com] Is there a way in the kickstart configuration file to tell anaconda to configure the network interfaces with some parameters (e.g. DHCP vs static IP, onboot.) but do *not* bring them up during installation (so in practice just write the ifcfg-ethX files)? I tried with network --bootproto=dhcp --device=eth0 --onboot=on -hostname=myhost but the problem is that during the installation it tries to bring eth0 up and get the IP address (eventually timing out). If I don't put that line in the kickstart file, all the interfaces are silently configured for DHCP and onboot=yes, and the hostname is not configured. Don't configure the network in the kickstart and write the hostname configuration from the %post section; or configure a dummy IP with the network option then edit the network configuration in %post? Moray. "To err is human. To purr, feline" -------------- next part -------------- An HTML attachment was scrubbed... URL: From waj at mycluster.cn Sun Jan 23 14:37:19 2011 From: waj at mycluster.cn (engine) Date: Sun, 23 Jan 2011 22:37:19 +0800 (CST) Subject: help with network configuration In-Reply-To: <008c01cbb99d$7a215540$6e63ffc0$@gmail.com> References: <008c01cbb99d$7a215540$6e63ffc0$@gmail.com> <001c01cbb824$f1c27ea0$d5477be0$@gmail.com> <000001cbb987$e9893d00$bc9bb700$@Henderson@ict-software.org> Message-ID: <5fc3d846.49f2.12db34ec395.Coremail.waj@mycluster.cn> maybe there is something wrong with your spell,please verify '?hostname',it '--' not '?' That?s what I ended up doing. I change the host name in /etc/hosts and /etc/sysconfig/network, and I manually reconfigure ethX by playing with the /etc/sysconfig/network-scripts/ifcfg-ethX files. Everything is done in a %post section. I just wished there was an easier way to configure networking in the kickstart configuration file. Have a nice day GV From:kickstart-list-bounces at redhat.com[mailto:kickstart-list-bounces at redhat.com]On Behalf OfMoray Henderson Sent:Friday, January 21, 2011 8:26 AM To:'Discussion list about Kickstart' Subject:RE: help with network configuration From:Gianluca Varenni [mailto:gianluca.varenni at gmail.com] Is there a way in the kickstart configuration file to tell anaconda to configure the network interfaces with some parameters (e.g. DHCP vs static IP, onboot?) but do *not* bring them up during installation (so in practice just write the ifcfg-ethX files)? I tried with network --bootproto=dhcp --device=eth0 --onboot=on ?hostname=myhost but the problem is that during the installation it tries to bring eth0 up and get the IP address (eventually timing out). If I don?t put that line in the kickstart file, all the interfaces are silently configured for DHCP and onboot=yes, and the hostname is not configured. Don?t configure the network in the kickstart and write the hostname configuration from the %post section; or configure a dummy IP with thenetworkoption then edit the network configuration in %post? Moray. "To err is human. To purr, feline" -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonas.hagberg at it.uu.se Mon Jan 24 15:09:08 2011 From: jonas.hagberg at it.uu.se (Jonas Hagberg) Date: Mon, 24 Jan 2011 16:09:08 +0100 Subject: Anaconda sometimes fails SL linux 55 Message-ID: <4D3D9614.5080401@it.uu.se> I have a problems that sometimes occur. It sometimes occur more often when I trying to kickstart more nodes. Sometimes it happens only to one node several times. Often it helps to just reboot and start again. Sometimes not. This is the error message I get. Running anaconda, the Scientific Linux system installer - please wait... Traceback (most recent call last): File "/usr/bin/anaconda", line 604, in ? instClass = getInstClass(opts) File "/usr/bin/anaconda", line 358, in getInstClass from kickstart import Kickstart File "/usr/lib/anaconda/kickstart.py", line 17, in ? from installclass import BaseInstallClass, availableClasses, getBaseInstallClass File "/usr/lib/anaconda/installclass.py", line 581, in ? baseclass = getBaseInstallClass() File "/usr/lib/anaconda/installclass.py", line 566, in getBaseInstallClass allavail = availableClasses(showHidden = 1) File "/usr/lib/anaconda/installclass.py", line 519, in availableClasses exec(cmd) File "", line 1, in ? File "/usr/lib/anaconda/installclasses/rhel.py", line 18, in ? class InstallClass(BaseInstallClass): File "/usr/lib/anaconda/installclasses/rhel.py", line 28, in InstallClass repos = { "Scientific Linux Security Updates": ("ftp://ftp.scientificlinux.org/linux/scientific/5rolling/%s/updates/security" %(rpmUtils.arch.getBaseArch() ,), None) } NameError: name 'rpmUtils' is not defined install exited abnormally [1/1] sending termination signals...done Any hints? -- ------------------------------------------- Jonas Hagberg jonas.hagberg at it.uu.se Systemexpert Projektledare UPPNEX UPPMAX tel 018 - 471 1026 fax: 018 - 51 19 25 Uppsala universitet Box 337, L?gerhyddsv 2E, Hus 4, room 4111 751 05 Uppsala www.uppmax.uu.se ------------------------------------------- From bluethundr at gmail.com Sun Jan 30 17:54:02 2011 From: bluethundr at gmail.com (Tim Dunphy) Date: Sun, 30 Jan 2011 12:54:02 -0500 Subject: koan and puppet via kickstart Message-ID: Hello list! I am attempting to install puppet and koan via kickstart so that they are available on first boot. I am booting xen images via cobbler. This is my packages section of my ks file: %packages @base @cluster-storage @clustering @core @editors @legacy-network-server @mail-server @network-server @news-server @server-cfg @text-internet @web-server @smb-server koan puppet screen keyutils trousers fipscheck device-mapper-multipath kmod-gnbd-xen kmod-gfs-xen The only two packages that the initial setup process complains about are koan and puppet. Yet if I attempt to install these packages via the command: yum install -y koan puppet it works! how can I address what is really the only flaw in my current kickstart process? thanks in advance! -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B From chip.shabazian at bankofamerica.com Mon Jan 31 16:34:09 2011 From: chip.shabazian at bankofamerica.com (Shabazian, Chip) Date: Mon, 31 Jan 2011 10:34:09 -0600 Subject: koan and puppet via kickstart In-Reply-To: References: Message-ID: <2FA17BA1CC9A9B408927E72E9FA4A1ED01272D3C5B@ex2k.bankofamerica.com> Do they install properly via the %post? -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Tim Dunphy Sent: Sunday, January 30, 2011 9:54 AM To: kickstart-list at redhat.com Subject: koan and puppet via kickstart Hello list! I am attempting to install puppet and koan via kickstart so that they are available on first boot. I am booting xen images via cobbler. This is my packages section of my ks file: %packages @base @cluster-storage @clustering @core @editors @legacy-network-server @mail-server @network-server @news-server @server-cfg @text-internet @web-server @smb-server koan puppet screen keyutils trousers fipscheck device-mapper-multipath kmod-gnbd-xen kmod-gfs-xen The only two packages that the initial setup process complains about are koan and puppet. Yet if I attempt to install these packages via the command: yum install -y koan puppet it works! how can I address what is really the only flaw in my current kickstart process? thanks in advance! -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing. From Pablo.Iranzo at redhat.com Mon Jan 31 17:03:41 2011 From: Pablo.Iranzo at redhat.com (=?utf-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Mon, 31 Jan 2011 12:03:41 -0500 (EST) Subject: koan and puppet via kickstart In-Reply-To: <2FA17BA1CC9A9B408927E72E9FA4A1ED01272D3C5B@ex2k.bankofamerica.com> Message-ID: <8796940.821.1296493442546.JavaMail.iranzo@iranzo.usersys.redhat.com> Hi ----- Mensaje original ----- > De: "Chip Shabazian" > Para: "Discussion list about Kickstart" > Enviados: Lunes, 31 de Enero 2011 17:34:09 > Asunto: RE: koan and puppet via kickstart > Do they install properly via the %post? > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Tim Dunphy > Sent: Sunday, January 30, 2011 9:54 AM > To: kickstart-list at redhat.com > Subject: koan and puppet via kickstart > > Hello list! > > I am attempting to install puppet and koan via kickstart so that they > are available on first boot. I am booting xen images via cobbler. > > This is my packages section of my ks file: > > %packages > @base > @cluster-storage > @clustering > @core > @editors > @legacy-network-server > @mail-server > @network-server > @news-server > @server-cfg > @text-internet > @web-server > @smb-server > koan > puppet > screen > keyutils > trousers > fipscheck > device-mapper-multipath > kmod-gnbd-xen > kmod-gfs-xen > > > The only two packages that the initial setup process complains about > are koan and puppet. Yet if I attempt to install these packages via > the command: > > yum install -y koan puppet > > it works! how can I address what is really the only flaw in my current > kickstart process? Are your koan and puppet packages on the same repo as the remaining the packages or an additional repo defined somewhere in ks? Regards Pablo -- Pablo Iranzo G?mez (Pablo.Iranzo at redhat.com) Senior Global Profesional Services Consultant (RHCA, RHCSS, RHCDS, RHCVA, RHCE, RHCSP) #804006196923216 Phone: +34 645 01 01 49 (CET/CEST) GnuPG KeyID: 0xFAD3CF0D