SCIENTIFIC-LINUX-USERS Archives

January 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Thu, 14 Jan 2016 20:36:07 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
On Thu, Jan 14, 2016 at 2:37 PM, David Sommerseth
<[log in to unmask]> wrote:
> On 14/01/16 15:21, Loris Bennett wrote:
>> Hi Benjamin,
>>
>> Benjamin Lefoul <[log in to unmask]> writes:
>>
>>> Hi all,
>>>
>>> I am actually interested in the automated install topic (currently
>>> taking place in the other discussion, but I don't want to feed the
>>> troll so I'll start a new one).
>>>
>>> Someone just mentioned Cobbler, and the fact that it's RH's baby. Is
>>> this in any way linked to the recent acquisition of Ansible ?  In
>>> fact, I never really understood what Ansible was, and does it have its
>>> place in automated install? Can it replace Kickstart?
>>>
>>> As you can see I am pretty naive about the topic...
>>
>> I don't know very much about kickstart
>
> As a rough crash-course .... checkout /root/anaconda-ks.cfg on a freshly
> installed system.  If you want to do the exact same installation once
> more, you copy this file to a medium or web server and provide the URI
> to this file on the kernel command line before starting the installer.
> If anaconda picks it up, you'll have an automated install running instantly.

Really, you don't. "anaconda-ks.cfg" is the anaconda pardsed results
of the deployment procedure, and lacks many critical feautres of a
robust kickstart file for PXE or other common kickstart setups.

* The default installaiton labels partitions by the DHCP or otherwise
configured hostname, which is confusing on multiple hosts using the
same kickstart file.
* It comments out the disk configuration stanza.
* It includes distinct comments and layouts from
"system-config-kickstart" or other constructed kickstart tools.
* It does not correctly handle multple '%pre', '%post', or '%post
--nochroot' stanzas.

If you want to use a consistent kickstart, and have each published
host have a reference copy of its actual upstream kickstart file for
future reference, add this stanza to your published kickstart files
before using them.

    %pre --nochroot
    cp /tmp/ks.cfg /mnt/sysimage/root/ks.cfg

>
>
> --
> kind regards,
>
> David Sommerseth

ATOM RSS1 RSS2