<div dir="ltr">I can also give my personal opinion. Responses inline.<div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Oct 12, 2013 at 8:54 AM, Tim Moody <span dir="ltr"><<a href="mailto:tim@timmoody.com" target="_blank">tim@timmoody.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Everyone will be shy to respond, but here's my take. First, the motivation is that the benefit of a school server, especially in non or occasionally connected environments, is assumed. Secondly, let's be clear that you asked about goals, not what we've accomplished.<br>
<br>
The goal of the XSCE project is to continue development of the OLPC XS project along the following lines:<br>
<br>
1. Absorb features from all the various incarnations of XS including 0.7, Nepal, Australia, and any others and make it available on a variety of platforms including intel, but also incredibly cheap and incredibly low power devices, such as the XO but also raspi, trimslice, cubox, and others as they come to market. These features fall into three broad categories, infrastructure such as routing, support for XO specific services, and general (web) server based applications and content.<br>
<br>
2. Move installation and configuration from something that happens along with the OS installation to something an end user could do using a gui whenever she likes, if required.<br>
<br>
3. Provide a mechanism whereby features can be contributed by interested members of the community without rebuilding a disk image or an rpm.<br>
<br></blockquote><div><br></div><div>I had contacted various deployments over the summer, and through conversations with them, compiled a list of considerations:</div><div><br></div><div><a href="https://sugardextrose.org/projects/xsce/wiki/primary_considerations">https://sugardextrose.org/projects/xsce/wiki/primary_considerations</a><br>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Answers to specific questions below.<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
-----Original Message----- From: Tony Anderson Sent: Friday, October 11, 2013 11:10 AM To: <a href="mailto:xsce-devel@googlegroups.com" target="_blank">xsce-devel@googlegroups.com</a> Subject: Re: [XSCE]<div class="im"><br>
Hi, All<br>
<br>
Help me understand a little about where this project is going.<br>
<br>
I understood XSCE initially as an attempt to use an XO as the school server. This was motivated by two requirements: (1) support for deployments which were constrained to use XO and (2) use of the XO-1.75 as the school server to enable use of the lower power ARM architecture.<br>
<br></div></blockquote></blockquote><div><br></div><div>and also make use of various other low power ARM hardware, like trimslice, etc.</div><div><br></div><div>There is no "constraint", that the XSCE is limited to just these platforms. It is intended to run on generic x86 equally well.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
Apparently one outcome is that the XS-0.7 install procedure was replaced by a requirement to add school server capabilities to a previously installed build (e.g. 13.2).<br>
<br>
The XS architecture separated the disk into two partitions: root and library. The intent was to separate software (root) from content (library). This would support backup of the library partition since the root partition could be restored by a new install followed by simple copy of the backup to the library partition. Does XSCE maintain this architecture?<br>
</div></blockquote>
<br>
XSCE requires that the OS be pre-installed, so the disk partitioning is a priori. However, some of us have encouraged people to place content in the /library directory so that it can take advantage of a separate partition if there is one. It would certainly be possible to mount external devices as /library.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
The XO build is installed as a copy of an image from a usb drive to the internal store.<br>
</blockquote>
<br></div>
Work is being done on this installation mechanism, but up to now server content has been installed as an rpm, which has dependencies on other rpms and scripts to do various work like configuring networking, etc. The repositories can be remote or local. The new ansible install still operates at the time of initial installation, but avoids having to build rpms and holds the promise of incremental configuration.<div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
The XS install is a normal OS install in which a minimal Linux OS executes a script from a ramdisk to access the USB flash drive, decompress files and to copy them to the newly created partitions.<br>
<br>
Apparently, XSCE is installed by the previously installed OS (13.2). What is the dependency of XSCE on this OS? Does the XSCE install replace it?<br>
</blockquote>
<br></div>
In the rpm and ansible scenarios it does not replace the OS on the XO or any other device.<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Naturally, the XO software build is for a client machine. It is based on graphical user interface, keyboard, and track pad.<br>
<br>
A server is intended to supply services to other computers (clients) via a network. As such, it is intended to be operated headless. Control of the server is normally by a remote login and command line operations.<br>
<br>
How does XSCE handle the change from a client machine to a server? Does it require a monitor and keyboard (or touchscreen)?<br>
</blockquote>
<br></div>
Like XS, XSCE requires a monitor and keyboard (built into the XO) for installation, but can be basically headless thereafter. Most of us turn on sshd and do the entire install remotely. Probably other devices can come up with sshd capability already on and be entirely headless, if you can figure out their ip address.<div class="im">
<br></div></blockquote><div><br></div><div>+1 The intent is to install and update on headless hardware.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
There is discussion of a home page. In XS-0.7 there is no home page. The only way to interact with the server is via ssh. Is this home page in XSCE the portal to a web site supported by XSCE or an administrative interface to XSCE?<br>
</blockquote>
<br></div>
My experience of XS is that the home page is moodle. I have been working on a high level home page aimed at end users from which there would be links to installed services. It is intended to support local languages.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
For historical reasons, server administration is done in English (similar to the fact that air traffic control is done in English).<br>
I assume from this that a multi-language home page is the home page of a web site on the server, not server administration.<br>
</blockquote>
<br></div>
yes. however, several web-based administration tools are in the works.<div class="im"><br></div></blockquote><div><br></div><div>In Dextrose Server (downstream of XSCE), we are experimenting with Ajenti (<a href="http://ajenti.org/">http://ajenti.org/</a>). It is written in python, and allows easy addition/removal/configuration of plugins. So far, things look promising. We even experimented with network bandwidth throttling, which is configured through Ajenti (on the frontend), and uses wondershaper <a href="http://lartc.org/wondershaper/">http://lartc.org/wondershaper/</a> (as a backend). We hope to upstream these to XSCE in this development cycle.</div>
<div><br></div><div>Here's a link to a slightly dated and choppy video demonstrating Ajenti on a XO-1.75 school server. We are working to remove all unnecessary modules, fix bugs and speed it up since then. The good news is that the upstream Ajenti developer is extremely responsive.</div>
<div><a href="http://www.youtube.com/watch?v=-LbPRVc5Bv4&feature=share&t=2m35s">http://www.youtube.com/watch?v=-LbPRVc5Bv4&feature=share&t=2m35s</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
There has been much discussion of Ansible (vs Puppet). Is Ansible intended as a means to implement the build process for XSCE or as a means to implement and customize the install of XSCE or as a means to administer an XSCE installation?<br>
</blockquote>
<br></div>
The implementer of ansible cleverly added an rpm build mechanism, but it is really aimed at installation, and, I hope, eventually at administration, either remote or local.<div class="im"><br></div></blockquote><div><br>
</div><div>+1. rpm has been provided as a simple way to get started. After that ansible takes over, installation, configuration and updating.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
The general philosophy of XS is to build a single installable version of the software (currently XS-0.7). After installation, scripts are<br>
provided to configure the software, primarily to match the local network.<br>
<br>
I think the assumption is that the server has ample disk capacity so that there is no need to limit the installed software packages to those that the deployment actually uses. For example, Moodle is installed but rarely used. XS-0.7 sets up a root partition of 8GB and the rest of the available capacity is given to the library partion.<br>
<br>
It is certainly understandable that this assumption would not apply to a school server based on an XO laptop.<br>
<br>
However, it has always been clear that the XO is a terrible choice for a server platform to be used only as a last resort. The primary reason for a school server is to give access to content beyond the limited capacity of the XO.<br>
<br>
Even though the OLPC project is intended to address the problem of the 'digital divide', many developers seem to assume that deployed XOs have the same access to the internet as they themselves have. Even if a school has a DSL line shared by 100 XOs, that is not the same as a developer with access to a broadband network shared among a handful of users.<br>
<br>
I think it is important that the XSCE project define its goals and assumptions clearly.<br>
<br>
In the case of the XS-0.7, the assumptions are that the deployment has limited or no access to the internet, that it has a school server with large disk capacity, the server can support a local wifi network, the server can operate without system administration (essentially unattended except for power on and power off) for a full school year, the server can share internet access when connected to a WAN (ISP) with the XOs connected on the local network, and that the software on the school server be stable and updated at most once between school sessions.<br>
</blockquote>
<br></div>
I think the XSCE community assumes that all of the above represents the most common scenario. I grant that the requirement for large disk capacity, which I know you take to be axiomatic, is not met by all of our target platforms in ways that we find satisfactory yet.<div class="">
<div class="h5"><span style="color:rgb(34,34,34)"> </span><br></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Tony<br>
<br>
<br></blockquote></div></div></blockquote><div><br></div><div>Anish</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On 10/11/2013 09:58 AM, George Hunt wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
for Haiti, I just disabled multiviews in<br>
/etc/httpd/conf.d/xs-portal.<u></u>conf (commented out)<br>
<br>
<br>
On Fri, Oct 11, 2013 at 9:14 AM, Tim Moody <<a href="mailto:tim@timmoody.com" target="_blank">tim@timmoody.com</a><br>
<mailto:<a href="mailto:tim@timmoody.com" target="_blank">tim@timmoody.com</a>>> wrote:<br>
<br>
just before I left for travels there were problems at the Haiti<br>
deployment with the multilingual home page I put together. Can<br>
someone summarize where that currently stands? Was it simply<br>
commented out and not used? I want to sort this out.<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br></div></div><span class=""><font color="#888888">
-- <br>
Sig inserted by AutoHotkey ver. 1.1.11.01 (signature - first line)<br>
WLMail QuoteFix -> <a href="http://www.dusko-lolic.from.hr/" target="_blank">http://www.dusko-lolic.from.<u></u>hr/</a> (signature - second line) <br>
</font></span></blockquote></div><br></div></div>