Re: Location of lts.conf file
Floris Bos <bos-2Bwqp0C+fZnAjeZApIleJ/[email protected]> Tue, 26 Feb 2013 16:49:30 +0100
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============0266179371946792175==
Content-Type: multipart/alternative;
boundary="------------010107010502070303070405"
This is a multi-part message in MIME format.
--------------010107010502070303070405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On 02/26/2013 11:39 AM, Veli-Matti Lintu wrote:
>> Since in LTSP 6 we'll have to rewrite most of our code base,
>> and all LDM_* variables won't be supported anymore due to libpam_sshauth
>> / LightDM,
>> so sysadmins will have to revisit their configuration anyway,
>> (and it's a good chance to break backwards compatibility wrt
>> configuration, removing ancient or undocumented stuff),
>>
>> I'm pretty much in favor of not using TFTP as the basis of our
>> configuration system anymore, but instead to switch to using a (probably
>> python-based) daemon that reads configuration files from the server
>> /etc/ltsp/config.d/, and exports them to the clients upon request.
>>
>> E.g. a client could do from the initramfs:
>> wget
>> http://server:1234/config?phase=initramfs&arch=i386&ip=xxx&mac=xxx&hostname=xxx&...
>> -O config
>> . config
> We wrote our own TFTP server to overcome some boottime problems in LTSP
> environments. We have some thin/fat clients that need special kernels and/or
> kernel parameters to work correctly. Since we have too many clients to so
> that it would be practical to modify pxelinux.cfg files manually, we have
> now a hook script for our TFTP server that fetches the kernel information
> from LDAP when the client requests the pxelinux.cfg during boot.
Another option to easily provide custom kernel (parameters) would be to
trade in pxelinux for iPXE ( http://www.ipxe.org/ )
It can fetch its boot script over HTTP, as in
http://server/script_that_generates_boot_instructions.php
We use it in a product that remotely provisions servers in datacenters,
and it works very well.
--
Yours sincerely,
Floris Bos
--------------010107010502070303070405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/26/2013 11:39 AM, Veli-Matti
Lintu wrote:<br>
</div>
<blockquote
cite="mid:1802774017.1999.1361875164875.JavaMail.root-Wdv/[email protected]"
type="cite">
<blockquote type="cite">
<pre wrap="">Since in LTSP 6 we'll have to rewrite most of our code base,
and all LDM_* variables won't be supported anymore due to libpam_sshauth
/ LightDM,
so sysadmins will have to revisit their configuration anyway,
(and it's a good chance to break backwards compatibility wrt
configuration, removing ancient or undocumented stuff),
I'm pretty much in favor of not using TFTP as the basis of our
configuration system anymore, but instead to switch to using a (probably
python-based) daemon that reads configuration files from the server
/etc/ltsp/config.d/, and exports them to the clients upon request.
E.g. a client could do from the initramfs:
wget
<a class="moz-txt-link-freetext" href="http://server:1234/config?phase=initramfs&arch=i386&ip=xxx&mac=xxx&hostname=xxx&">http://server:1234/config?phase=initramfs&arch=i386&ip=xxx&mac=xxx&hostname=xxx&</a>...
-O config
. config
</pre>
</blockquote>
<pre wrap="">
We wrote our own TFTP server to overcome some boottime problems in LTSP
environments. We have some thin/fat clients that need special kernels and/or
kernel parameters to work correctly. Since we have too many clients to so
that it would be practical to modify pxelinux.cfg files manually, we have
now a hook script for our TFTP server that fetches the kernel information
from LDAP when the client requests the pxelinux.cfg during boot.
</pre>
</blockquote>
<br>
Another option to easily provide custom kernel (parameters) would be
to trade in pxelinux for iPXE (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://www.ipxe.org/">http://www.ipxe.org/</a> )<br>
It can fetch its boot script over HTTP, as in
<a class="moz-txt-link-freetext" href="http://server/script_that_generates_boot_instructions.php">http://server/script_that_generates_boot_instructions.php</a><br>
<br>
We use it in a product that remotely provisions servers in
datacenters, and it works very well.<br>
<br>
<pre class="moz-signature" cols="72">
--
Yours sincerely,
Floris Bos
</pre>
</body>
</html>
--------------010107010502070303070405--
--===============0266179371946792175==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
--===============0266179371946792175==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_____________________________________________________________________
Ltsp-developer mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help, try #ltsp channel on irc.freenode.net
--===============0266179371946792175==--