similar to: Kickstarting several *different* setups

On Tue, Jan 20, 2015 at 10:41 AM, Tom Grace <lists-in at deathbycomputers.co.uk> wrote: > On 20/01/2015 16:29, Ashley M. Kirchner wrote: >> >> So my question is, is there some way do determine via kickstart, what to >> install on that machine based on some criteria, possibly the IP that's >> being assigned to it, or MAC address, or something ... > > If

On 01/20/2015 08:41 AM, Tom Grace wrote: > I would suggest that the "right way" would be to kickstart all your > machines the same way, and then use a configuration management tool > (like Puppet or Chef) to customize them Seconded. Personally, I recommend either ansible or bcfg2 over other tools. Puppet has a larger user base, but when I talk to users at conferences (such

Tom: Thanks for the suggestion. I'll look into those tools. Mark: Yes, they are using pxeboot. Right now when they boot up, the pxe config offers two options, 32- and 64bit. Are you suggesting I create multiple entries that one selects based on what the machine is going to be? Is there a way to have this done automatically so I don't have to physically have to do that for each machine,

Ansible, Bcfg2, Chef, Cobbler, Puppet, and Salt; I notice that Spacewalk is not mentioned. Any particular reason that it gets no recommendations? What about CFEngine? Any comments on this one? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive

On Tue, Jan 20, 2015 at 11:13 AM, Ashley M. Kirchner <ashley at pcraft.com> wrote: > Tom: Thanks for the suggestion. I'll look into those tools. > > Mark: Yes, they are using pxeboot. Right now when they boot up, the pxe > config offers two options, 32- and 64bit. Are you suggesting I create > multiple entries that one selects based on what the machine is going to be? >

On 20/01/2015 16:29, Ashley M. Kirchner wrote: > So my question is, is there some way do determine via kickstart, what to > install on that machine based on some criteria, possibly the IP that's > being assigned to it, or MAC address, or something ... If you just want to use kickstart, it would be pretty simple to serve these via HTTP, and have a simple script in PHP or similar that

On Tue, Jan 20, 2015 at 3:14 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > >> I would suggest that the "right way" would be to kickstart all your >> machines the same way, and then use a configuration management tool >> (like Puppet or Chef) to customize them > > > Seconded. > > Personally, I recommend either ansible or bcfg2 over

On Thu, 26 Feb 2015 13:42:57 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > And after picking this back up this morning .... still no dice. I have > now > blacklisted the one module that would enumerate the add-in ethernet port > so > that is no longer an issue during the kickstart process, however the > following is now happening: > > - kickstart

On Wed, 25 Feb 2015 17:11:02 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > Add "rdblacklist=MODULE_NAME" to your append line in pxelinux.conf file. >> > > Trying that next. It'll have to wait till tomorrow as we're under a > serious > blizzard/snow event right now and I'd like to get home before all of hell > freezes over.

I have a Dell server that has two built-in ethernet devices. When I kickstart the machine, they are correctly identified as eth0 and eth1 (correctly meaning they correspond to the physical device ports 1 and 2). I need a third one and want that to come up as eth2. After adding the hardware, kickstart now fails because for some reason it goes through a rename process where it makes the newly added

Starting back in RHEL/Cent 5 I found that the only way to make sure your interface enumeration was consistent after install with what you had during install was to create a udev rules file using the mac addresses as the key. It is easy to run a short script in postinstall to create it based on how anaconda has seen them. In order for this to work on Cent 6 you have to set biosdevname=0

Define out of order in this case just so I know for sure what you mean. What my solution does, or at least does reliably in my case, is make sure the interfaces are in the same order once installed as the install kernel saw them. It won't re-order them to be sequential based on bus, mac or driver. I am working on that but it will also include naming the devices based on the module

<overly trimmed> On 02/25/2015 01:56 PM, Ashley M. Kirchner wrote: > Ok, so some of this now works, but I'm still having problems. With the > bootif option, the system now correctly configures and uses the same > interface to get its kickstart file. However, when the system is done and > boots up, the interfaces are still messed up. So this is what I have in the >

Here is my script for post install if you want to try it. In order for the shuffling to not occur you do need to create the udev rules file somehow. I am not sure how mangled this will be in email but it is worth a try. It should run OK with nothing else. I have a better version in the works but the enhancements are mainly useful for Fedora 19-21. I did forget to say I also block

Is there a way to use kickstart to boot a machine into a manual setup process? Basically what I'm getting to is this, the machine doesn't not have a CD drive in it (nor can I add one), but I can boot it via kickstart. The install media is on the network. What I'd like to do is boot this machine up and rather than have kickstart do everything for me as far as installing the OS and

Hi, we see a growing need for a better Configuration management for our servers. Are there any known good resources for a comparison of e.g. Puppet, Chef, Ansible etc? What would you suggest and why? :) Thanks and Regards . G?tz

Gotcha. Thanks all! You guys gave me the answers I needed to know and hear. For the immediate futre I will likely go with multiple pxeboot options which then picks the specific kickstart file. It's easy for me to put a label on the server that says 'web' or 'mail' etc. Then just pick the same from the menu. Eventually I'll delve deeper into custom and automated setups. On

Hey folks, A week or two ago someone mentioned something about using their own home-grown RPMs for managing config info on their boxes. I really like this idea and would like to learn more about it. Are there some examples out there? I have lots of custom config info and think this would be an ideal way to manage it. Others mentioned puppet and CF engine which probably have their merits as

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple kickstart files, one per machine. Anyway, lspci reports this: 00:19.0 Ethernet controller: Intel