Re: Centos7 : some ( official )help wanted

--===============5787141533793830334==
Content-Type: multipart/alternative; boundary=001a1135f1a63a261a0519e6a1b6

--001a1135f1a63a261a0519e6a1b6
Content-Type: text/plain; charset=UTF-8

On Wed, Jul 1, 2015 at 12:10 PM, Jim Kinney <[email protected]> wrote:

> Warren,
>
> Then it should say on the site " no developer wants to do the work".
> Now it says K12Linux is legacy.
>
> And Warren, I am grateful for the work that you put in for K12Linux.
>
> What I'm saying here, and I think what Radek is saying, is it's not
> legacy, It works.
>
>
> Legacy doesn't mean it doesn't work. It simply means no further
> development will be done for that particular setup. Sometimes a program
> becomes legacy because no one is working on it. Sometimes because it get
> superseded by newer projects.
>
> K12Linux on CentOS 6 is a great tool. But porting it to be fully CentOS 7
> ready will require development from people other than Warren. K12Linux will
> be around for many more years since CentOS 6 will be around as well.
>

Thank you.  You understand the situation exactly.

CentOS 7 actually contains all the same components as CentOS 6 but in a
different form.  It would be theoretically possible to adapt those pieces
to work in the same manner as CentOS 6.  There would be drawbacks though
... like CentOS 7 is x86_64 only, so the client OS would no longer be able
to be built from the same OS as the server.


>
> I think it's time to look at alternate methods of achieving a similar
> result. The PXE boot aspect will need to stay but the server platform needs
> to be revisited. The IT world has embraced virtual machines. Maybe a thin
> client should be running a VM client that provides console to a remote VM
> running on a server farm. The spice client is remarkably light and can push
> screen bits as well if not better than NX and RDP (and way faster than X
> over SSH or VNC). Using a management tool like Ovirt would allow tech
> support to build and maintain student machines as pool devices and thus
> only require updates to a single machine. Some coding is required to
> provide a single sign on screen that would connect to the next available VM
> console (which then auto-mounts the students home directory). The VM client
> (spice) can be 32 bit as well as 64 so it will run on older client hardware
> and it supports USB pass through for thumb drives. Sound also works.
>
> 3 years ago I was doing a demo talk of Ovirt and connected through 2
> layers of VPNs back to my work lab to show both windows and Linux desktops.
> I started a browser and went to YouTube and the flash video played smoothly
> and with sound synched to the video.
>
> As KVM, the technology behind Ovirt virtual machines, supports "memory
> ballooning", different VMs that need to use the same block of memory can
> share the block (read only - best for OS and application memory) and thus
> can perform similar types of resource sharing that K12Linux provided. Best
> of all, each user is truly isolated from all the others so an application
> crash (ahem - flash) will only affect the single user even with shared
> memory.
>
>
KVM would be quite nice as the SPICE remote desktop protocol is
significantly better than X.  SPICE would handle remote USB, full screen
video and sound in a better way than X/ltspfs/pulseaudio had done in the
past.  It however has major drawbacks in memory overhead compared to the
old LTSP model, existing servers would be able to handle far fewer clients.

Warren Togami

--001a1135f1a63a261a0519e6a1b6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jul 1, 2015 at 12:10 PM, Jim Kinney <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:[email protected]" target=3D"_blank">[email protected]</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div><span class=3D""><block=
quote type=3D"cite"><div style=3D"font-family:Verdana,Arial,Helvetica,sans-=
serif;font-size:10pt;color:#000000"><div style=3D"color:#000;font-weight:no=
rmal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,san=
s-serif;font-size:12pt"><div class=3D"gmail_extra"><div class=3D"gmail_quot=
e"><div>Warren,<br></div><div><br></div><div>Then it should say on the site=
 &quot; no developer wants to do the work&quot;.<br></div><div>Now it says =
K12Linux is legacy.<br></div><div><br></div><div>And Warren, I am grateful =
for the work that you put in for K12Linux.<br></div><div><br></div><div>Wha=
t I&#39;m saying here, and I think what Radek is saying, is it&#39;s not le=
gacy, It works.<br></div></div></div></div></div></blockquote><div><br></di=
v></span><div>Legacy doesn&#39;t mean it doesn&#39;t work. It simply means =
no further development will be done for that particular setup. Sometimes a =
program becomes legacy because no one is working on it. Sometimes because i=
t get superseded by newer projects.</div><div><br></div><div>K12Linux on Ce=
ntOS 6 is a great tool. But porting it to be fully CentOS 7 ready will requ=
ire development from people other than Warren. K12Linux will be around for =
many more years since CentOS 6 will be around as well.</div></div></blockqu=
ote><div><br></div><div>Thank you.=C2=A0 You understand the situation exact=
ly.</div><div><br></div><div>CentOS 7 actually contains all the same compon=
ents as CentOS 6 but in a different form.=C2=A0 It would be theoretically p=
ossible to adapt those pieces to work in the same manner as CentOS 6.=C2=A0=
 There would be drawbacks though ... like CentOS 7 is x86_64 only, so the c=
lient OS would no longer be able to be built from the same OS as the server=
.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br></div>=
<div>I think it&#39;s time to look at alternate methods of achieving a simi=
lar result. The PXE boot aspect will need to stay but the server platform n=
eeds to be revisited. The IT world has embraced virtual machines. Maybe a t=
hin client should be running a VM client that provides console to a remote =
VM running on a server farm. The spice client is remarkably light and can p=
ush screen bits as well if not better than NX and RDP (and way faster than=
=C2=A0X over SSH or VNC). Using a management tool like Ovirt would allow te=
ch support to build and maintain student machines as pool devices and thus =
only require updates to a single machine. Some coding is required to provid=
e a single sign on screen that would connect to the next available VM conso=
le (which then auto-mounts the students home directory). The VM client (spi=
ce) can be 32 bit as well as 64 so it will run on older client hardware and=
 it supports USB pass through for thumb drives. Sound also works.</div><div=
><br></div><div>3 years ago I was doing a demo talk of Ovirt and connected =
through 2 layers of VPNs back to my work lab to show both windows and Linux=
 desktops. I started a browser and went to YouTube and the flash video play=
ed smoothly and with sound synched to the video.</div><div><br></div><div>A=
s KVM, the technology behind Ovirt virtual machines, supports &quot;memory =
ballooning&quot;, different VMs that need to use the same block of memory c=
an share the block (read only - best for OS and application memory) and thu=
s can perform similar types of resource sharing that K12Linux provided. Bes=
t of all, each user is truly isolated from all the others so an application=
 crash (ahem - flash) will only affect the single user even with shared mem=
ory.</div><span class=3D""><div><br></div></span></div></blockquote><div><b=
r></div><div>KVM would be quite nice as the SPICE remote desktop protocol i=
s significantly better than X.=C2=A0 SPICE would handle remote USB, full sc=
reen video and sound in a better way than X/ltspfs/pulseaudio had done in t=
he past.=C2=A0 It however has major drawbacks in memory overhead compared t=
o the old LTSP model, existing servers would be able to handle far fewer cl=
ients.</div><div><br></div><div>Warren Togami</div></div></div></div>

--001a1135f1a63a261a0519e6a1b6--


--===============5787141533793830334==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
K12OSN mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>
--===============5787141533793830334==--