Hi Chris. I am glad to receive this email from you. I have been working on Linux OS (especially on RH Linux) side from quite some time. I am happy to say it is very flexible. One of the challenge I always face is remote installation in specific scenario. General practice at the big players like Data center, Carrier network operators etc is. Hardware vendor will deliver the hardware at the operator premises, racks it up, and do the cabling as per the network design/diagram and leave the premises. Because of the security reasons and other obvious reasons, it is always hard to get the physical access in those live environment. Customer will provide only the access to BMC, iLO, iLOM type of access to get the remote console to install the customized OS. This is very common practice in the industry. If person is sitting geographically remote location it is hard to mount the ISO remotely and perform installation. Some time back we tried to create the Kickstart with below option. 1. New hardware will be pre-installed with standard RHEL OS while delivering the hardware to customer from hardware vendor. 2. Configure the IP address to one of the Ethernet interface from remote console and ask customer to FTP the customized ISO to the new server. 3. We will have very small custom ISO created which we use only to boot the system, push the Kickstart and create the ramdisk from pre install step and copy the existing ISO from server hard disk partition and copy it to ramdisk and ask Kickstart installer to use the ISO from ramdisk. Step explained in #3 is works well with debian precede installer but not with Redhat Kickstart installer. Is it possible to provide the flexibility to read the ISO from ramdisk from Kickstart installer? Thanks Ganesh -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Chris Lumens Sent: Wednesday, March 02, 2016 10:24 PM To: kickstart-list@xxxxxxxxxx Subject: moving kickstart forward Hey everyone, I've been maintaining pykickstart and kickstart support in anaconda in general for a very long time now, though I've not been very active on this list. I'm going to be looking at kickstart exclusively for the forseeable future. Specifically, my focus is going to be on widening its adoption and making it more useful to everyone. The first step in this process is information gathering. Here's what I would like to know from you guys: * How do you use kickstart right now? What work flows do you have around it? Do you generate kickstart files from some process? Do you store them in version control? * What do you do in your kickstart files? Do you have extensive %pre and %post sections? If so, what kinds of things are you doing in them? Are you doing anything that would be generally useful that I should be doing for you? Do you ever use %traceback? Do you have unusual stuff going on in %packages? * What can I do to make your life easier? What annoys you about kickstart right now? What do you wish it did? What do you wish it didn't do? Would making it more like a language be helpful? Would making it easier to define site-specific commands be helpful? I know this is all really vague stuff, but I am just starting out on this project. I don't even really know where this is going to take me yet. I'd also like to emphasize that whatever I end up doing, I want to keep compatibility with kickstart as it exists today. That's something I take seriously in pykickstart. - Chris _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
