Sean McGrath wrote: > Dave Miner stated: >> Sean McGrath wrote: >>> Dave Miner stated: >>>> Jack wrote: >>>>> Hi Gurus, >>>>> >>>>> While comparing with the anaconda, I found that we're lack of a way to >>>>> dynamically configure storage. For example, I like to install Solaris >>>>> onto an iSCSI storaget (as I'm working on the iSCSI booting) but >>>>> currently there is just no way to do it. Just to raise a request and >>>>> start a thread to discuss if the requirements can be met with caiman. >>>>> >>>> My primary reaction is that this the most common use case seems likely to >>>> be using iSCSI targets in automated installation, not the interactive >>>> installer. How does Red Hat provide this in Kickstart? >>> Kickstart configs.. >>> >>> Its a flat file which doesn't seem to have well defined sections etc, just >>> sections seperated by %<keywords> >>> >>> Anyway for pre and post installs these sections of a Kickstart are located >>> with %pre and %post keywords. Theres nothing to say when these sections >>> end other than another section starting with a %<keyword> >>> >>> For example we (perfpit) have this as the pre and post sections: >>> >>> %pre >>> #!/bin/sh >>> rcp NFSSERVER:DISKCONFIG /tmp/diskcfg >>> rsh NFSSERVER /dom/pxe-linux SYSNAME del >>> >>> %post >>> rcp NFSSERVER:/auto/ifcfg_Linux/autofs/auto.* /etc >>> ... >>> >>> ... other bits. >>> >>> >>> the words NFSSERVER and DISKCONFIG are Kickstart keywords, replaced with >>> what ones install server etc are. >>> >>> The packages section is defined by a %packages like: >>> >>> %packages -resolvedeps >>> @ Server >>> @ X Window System >>> @ GNOME Desktop Environment >>> @ Web Server >>> @ Windows File Server >>> rsh-server >>> >>> >>> These packages with '@' are meta-packages, similar to say gcc-dev in IPS. >>> >> So, if I'm understanding you right, Kickstart doesn't have any actual >> support for iSCSI, you just get to work around it with your own scripting. >> Classic. > > Err sorry I was just describing the pre/post methods. > (Can't read this evening.) > > For iscsi Anaconda supports two options/commands: > scsi and iscsiname > > From http://fedoraproject.org/wiki/Anaconda/Kickstart > > iscsi (optional) > > iscsi --ipaddr= [options] > --target= > --port= > --user= > --password= > > iscsiname (optional) > > and use like: > > iscsiname foo > iscsi --ipaddr 192.168.1.6 --user "alice" --password "bob" > > (from examples via google) > > Hope that makes more sense. >
Yeah, it does, thanks for the info, Sean! Dave
