[Beaker-devel] Feedback regarding implementing BZ#989924

Nick Coghlan ncoghlan at redhat.com
Mon Aug 26 02:39:08 UTC 2013


On 08/26/2013 12:34 PM, Amit Saha wrote:
> 
> 
> ----- Original Message -----
>> From: "Nick Coghlan" <ncoghlan at redhat.com>
>> To: beaker-devel at lists.fedorahosted.org
>> Sent: Monday, August 26, 2013 12:31:26 PM
>> Subject: Re: [Beaker-devel] Feedback regarding implementing BZ#989924
>>
>> On 08/26/2013 12:17 PM, Amit Saha wrote:
>>> Regarding implementing [1], the two main changes are:
>>>
>>> 1. Adding support for a new ks_meta option. For eg. <recipe
>>> ks_meta="auth='--useshadow --enablemd5'">
>>> 2. And having support for reading it in the template:
>>>
>>> +{% if auth %}
>>> +auth {{ auth }}
>>> +{% endif %}
>>>
>>> When the ks_meta option is not specified, the generated kickstart doesn't
>>> get a 'auth' command entry.
>>>
>>> Does this look fine?
>>
>> For older RHEL versions, we may want to keep the non-empty auth by
>> default. Work out when shadow and md5-or-better became the default, and
>> keep forcing them up until then. Alternatively, as a research-free
>> alternative, I'm happy to go with "keep the kickstart customisation for
>> RHEL3 and RHEL4, switch to using the anaconda defaults for RHEL5 and later".
> 
> Do you mean, we keep the Beaker enforced defaults for RHEL3 and RHEL4?
> 
> And use Anaconda defaults (unless overridden from ks_meta) for RHEL5+ and Fedora ?

Yeah. Although I wouldn't complain if you wanted to check the defaults
for RHEL3 and RHEL4 to see if we could use the OS defaults there, too :)

Cheers,
Nick.

-- 
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane

Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)


More information about the Beaker-devel mailing list