[Server-devel] Firstboot modules

[Martin Langhoff]

StPepper,

forget about anaconda :-)  I want to _reduce_ as much as reasonable
what we do in anaconda/kickstart.

Let's focus on this:

 - some stuff in current kickstart %post won't be needed for xs-0.7

 - some stuff in current kickstart can be sanely moved to a firstboot script

 - other stuff (like network config) should be handled somewhere else
-- and here I strongly prefer a combination of Moodle admin UI taking
the values and writing them to a pre-arranged file. Scripts running as
root can then read those files, check for sanity, and apply the
changes. We can use incrond to trigger those.

cheers,


m

On Thu, Aug 26, 2010 at 7:46 PM, SgtPepper <ncorrare at gmail.com> wrote:
> Martin,
> On one hand,
> Some stuff like Network Configuration, *could* be hacked into anaconda (we'd
> have to push, for instance, 3G modem config, or wireless card, or pppoe into
> anaconda), which is a major pain, but It might get upstream. That, at least,
> will require some human interaction.
>
> About setting it up with Moodle... I could try to code a moodle admin
> module, it should not be that hard. The moodle admin module could set up:
>
> - Squid ON/OFF + maybe a squid blacklist (so some schools can blacklist
> potentially dangerous sites).
> - Every future configurable thing we can think off.
>
> Anaconda already asks for the Hostname, we could hack it to only ask for the
> domain name, and always add schoolserver. in front of it, and then we could
> set the kickstart %post to run domain_config.
>
>
> 2010/8/26 Martin Langhoff <martin.langhoff at gmail.com>
>>
>> Hi SgtPepper,
>>
>> I am with mixed feelings about firstboot scripts.
>>
>> One one hand, some kickstart %post stuff can be done much better in a
>> non-interactive firstboot script.
>>
>> On the other hand, I would like to avoid interactive firstboot
>> scripts. Many XSs are headless, and I keep pushing deployments towards
>> headless XSs. The best rugged/embedded HW out there for XS is
>> headless.
>>
>> Are you open to a combination of
>>
>>  - non-interactive stuff in firstboot scripts
>>
>>  - interactive stuff configurable via Moodle "admin" pages, which
>> write to files monitored by incrond,  which in turn invokes privileged
>> scripts...
>>
>> cheers,
>>
>>
>> martin
>>
>>
>> On Thu, Aug 26, 2010 at 6:44 PM, SgtPepper <ncorrare at gmail.com> wrote:
>> > To simplify the setup of the XS, I was thinking on creating some custom
>> > firstboot modules, for some common setup operations such as:
>> >
>> > 1 - Network Configuration (Internet Side: DHCP/Statip IP/PPPoE)
>> > 2- A domain_config wrapper
>> > 3- Squid (ON or OFF)
>> > 4- Show Moodle admin password
>> > 5- Finish Screen
>> >
>> > Any suggestions on any more things to add?
>> >
>> >
>> > PS: Once I finish the rpm, where do I push it?
>> >
>> > _______________________________________________
>> > Server-devel mailing list
>> > Server-devel at lists.laptop.org
>> > http://lists.laptop.org/listinfo/server-devel
>> >
>> >
>>
>>
>>
>> --
>>  martin.langhoff at gmail.com
>>  martin at laptop.org -- School Server Architect
>>  - ask interesting questions
>>  - don't get distracted with shiny stuff  - working code first
>>  - http://wiki.laptop.org/go/User:Martinlanghoff
>
>



-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff