Re: Suggestion on how to improve the client-building proocess
Άλκης Γεωργόπουλος <[email protected]> Sat, 6 Oct 2018 18:35:22 +0300
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <CAORUW4nOU7PCuD7z=+rONUxvSA5x3TJp+LAVyqOAWe3KY-tOig@mail.gmail.com> |
--===============2882912682677329836== Content-Type: multipart/alternative; boundary="0000000000008ff34005779123ea" --0000000000008ff34005779123ea Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You can just install a distro in a vm in bridged mode, and use that for the ltsp server. I don't see any reason to make things more complicated than that. =CE=A3=CF=84=CE=B9=CF=82 =CE=A3=CE=AC=CE=B2, 6 =CE=9F=CE=BA=CF=84 2018 - 17= :20 =CE=BF =CF=87=CF=81=CE=AE=CF=83=CF=84=CE=B7=CF=82 Franz Dietrich < [email protected]> =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > Hey all, > > I truely dislike the idea of having a "forced" same setup for server and > clients - which is why I'm having a chroot setup... > however I do understand, that many teachers would like to install and > maintain graphically. > > An alternative approach to the current would be to maintain a qemu-vm of > the client image and package this quemu as bootimage. > So the workflow for the server woud be: > > 1. install packages (graphically), > 2. launch "manage-client" > 3. get a window with a virtual machine that will then be installed > 4. do all the setup etc. > 5. on shutdown of the vm the image is built/updated > > Any thoughts on the feasability, time needed to implement this? > > My guess is that this approach would be much cleaner and would require > not too much additional code - though a lot would be needed to change. > I also think it would be less confusing for those who only maintain the > image without deeper linux knowledge. > > All the best > Franz (enaut in irc) > > Am 05.10.2018 um 22:42 schrieb Dashamir Hoxha: > > Hi, > > > > I noticed recently that whatever I install on the ltsp-server > > ends up running on the ltsp-clients as well (with chrootless mode). > > Actually this is a well-known fact, but I didn't think there was > > anything wrong with it, until I realized that apache2, and tomcat, > > and mysql were running on the client too, eating up a lot of ram! > > > > As a workaround I changed the order of scripts so that the image > > of the ltsp-client is generated as soon as possible, and then we > > proceed with the other installations and configurations, with > > guacamole, etc. > > > > However this solution has the drawback that afterwards you cannot > > install any more packages on the client image (if you need to). > > The only way is to rebuild the ltsp-server from scratch, and this takes > > a lot of time (about one hour), since lots of things have to be > > downloaded and installed (sometimes even compiled from source). > > > > Is it possible to unpack the image of a chrootless client to a director= y, > > to chroot to this directory and install any additional packages, and > > then to pack it back again? This could be much faster than rebuilding > > the whole server from scratch (and also more elegant). > > > > Thanks, > > Dashamir > > > > > > > > > > > > _____________________________________________________________________ > > 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 > > > > _____________________________________________________________________ > 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 > --0000000000008ff34005779123ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"auto">You can just install a distro in a vm in bridged mode, an= d use that for the ltsp server.<div dir=3D"auto">I don't see any reason= to make things more complicated than that.</div></div><br><div class=3D"gm= ail_quote"><div dir=3D"ltr">=CE=A3=CF=84=CE=B9=CF=82 =CE=A3=CE=AC=CE=B2, 6 = =CE=9F=CE=BA=CF=84 2018 - 17:20 =CE=BF =CF=87=CF=81=CE=AE=CF=83=CF=84=CE=B7= =CF=82 Franz Dietrich <<a href=3D"mailto:[email protected]">dietr= [email protected]</a>> =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5:<br></div>= <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex">Hey all,<br> <br> I truely dislike the idea of having a "forced" same setup for ser= ver and<br> clients - which is why I'm having a chroot setup...<br> however I do understand, that many teachers would like to install and<br> maintain graphically.<br> <br> An alternative approach to the current would be to maintain a qemu-vm of<br= > the client image and package this quemu as bootimage.<br> So the workflow for the server woud be:<br> =C2=A0=C2=A0<br> =C2=A0=C2=A0=C2=A0 1. install packages (graphically),<br> =C2=A0=C2=A0=C2=A0 2. launch "manage-client"<br> =C2=A0=C2=A0=C2=A0 3. get a window with a virtual machine that will then be= installed<br> =C2=A0=C2=A0=C2=A0 4. do all the setup etc.<br> =C2=A0=C2=A0=C2=A0 5. on shutdown of the vm the image is built/updated<br> <br> Any thoughts on the feasability, time needed to implement this?<br> <br> My guess is that this approach would be much cleaner and would require<br> not too much additional code - though a lot would be needed to change.<br> I also think it would be less confusing for those who only maintain the<br> image without deeper linux knowledge.<br> <br> All the best<br> Franz (enaut in irc)<br> <br> Am 05.10.2018 um 22:42 schrieb Dashamir Hoxha:<br> > Hi,<br> ><br> > I noticed recently that whatever I install on the ltsp-server<br> > ends up running on the ltsp-clients as well (with chrootless mode).<br= > > Actually this is a well-known fact, but I didn't think there was<b= r> > anything wrong with it, until I realized that apache2, and tomcat,<br> > and mysql were running on the client too, eating up a lot of ram!<br> ><br> > As a workaround I changed the order of scripts so that the image<br> > of the ltsp-client is generated as soon=C2=A0as possible, and then we<= br> > proceed with the other installations and configurations, with<br> > guacamole, etc.<br> ><br> > However this solution has the drawback that afterwards you cannot<br> > install any more packages on the client image (if you need to).<br> > The only way is to rebuild the ltsp-server from scratch, and this take= s<br> > a lot of time (about one hour), since lots of things have to be<br> > downloaded and installed (sometimes even compiled from source).<br> ><br> > Is it possible to unpack the image of a chrootless client to a directo= ry,<br> > to chroot to this directory and install any additional packages, and<b= r> > then to pack it back again? This could be much faster than rebuilding<= br> > the whole server from scratch (and also more elegant).<br> ><br> > Thanks,<br> > Dashamir<br> ><br> ><br> ><br> ><br> ><br> > _____________________________________________________________________<= br> > Ltsp-developer mailing list.=C2=A0 =C2=A0To un-subscribe, or change pr= efs, goto:<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://lists.sourceforge.net/lis= ts/listinfo/ltsp-developer" rel=3D"noreferrer noreferrer" target=3D"_blank"= >https://lists.sourceforge.net/lists/listinfo/ltsp-developer</a><br> > For additional LTSP help,=C2=A0 =C2=A0try #ltsp channel on <a href=3D"= http://irc.freenode.net" rel=3D"noreferrer noreferrer" target=3D"_blank">ir= c.freenode.net</a><br> <br> <br> <br> _____________________________________________________________________<br> Ltsp-developer mailing list.=C2=A0 =C2=A0To un-subscribe, or change prefs, = goto:<br> =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://lists.sourceforge.net/lists/listinf= o/ltsp-developer" rel=3D"noreferrer noreferrer" target=3D"_blank">https://l= ists.sourceforge.net/lists/listinfo/ltsp-developer</a><br> For additional LTSP help,=C2=A0 =C2=A0try #ltsp channel on <a href=3D"http:= //irc.freenode.net" rel=3D"noreferrer noreferrer" target=3D"_blank">irc.fre= enode.net</a><br> </blockquote></div> --0000000000008ff34005779123ea-- --===============2882912682677329836== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============2882912682677329836== 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 --===============2882912682677329836==--