We should get you access to TeamWiki. We do need some space for
common notes that
isn't published to the world at large...
Here are the minutes:
---
School Server Meeting Minutes, 2007-09-12
Attending: Scott, Michail, Alex, Kim, Wad, Walter
* Jabber needs to be packaged
* Apache is not going to work as transparent proxy (can be proxy
and cache). We would have to change the browser config behind a
school server. Squid only supports IPv4, not a good solution, maybe
the only short term solution.
* Can test registration on official build school servers (Kim
and SJ have one; we may be able to get one for RH).
o If you run more than one school server in a location for
testing purposes, you should use blinding tables. If you are in 1CC,
please also use channel 6 or 11.
o A Wiki page has info on how to set these tables up (mesh-
debug).
There are 3 scenarios when we need to recover/restore from school
server backup:
* Update requires a backup; followed by restore of entire laptop
* Catastrophic failure; restore entire laptop
* Lost/Deleted file; Individual file by file restore
* In the Trial3 scenario, we get a sharing mechanism for free:
individually 'restore' someone else's files
For restore we need to publish the backup directory (schoolserver/
share/SN) and this will regenerate the link that includes the
nickname. Click on a file and it will download it into the journal.
* We had some good discussions on what our journal and library
might look like in the future and how we might access 'published'
files/activities, and 'example' files. There is still alot of
planning to do for this 3 year vision.
* We also discussed what we can do today for FRS: we need to
first define what gets stored, where, and whether it needs to be
backed up.
* FRS Picture
o What currently lives in Lib is textbook and demo stuff;
shouldn't be backed up
o User owns everything in /home and /security
o Need to maintain a manifest of items downloaded to be
able to restore them.
o Shouldn't be system things in home/olpc
o We decided to give Jim the task to document and
communicate where things must be stored; what will be preserved over
upgrade; what will be backed up to school server. This needs
widespread communications once it is decided.
ACTION ITEMS:
* Backup doesn't work unless ssh to ss first, bug 2974
* Registration should be automatic; and logged
* Backup should be automatic; and logged [Dan Williams?]
* Backup should use user-friendly file names [Marco?]
* Backup dir should be published on SS, Wad/Scott
* Wad will create changes to school server links for user data;
need user friendly nick names
* Jim will sort out where user data (of all sorts) need to be
stored and backed up depending on backup mechanism.
On Sep 18, 2007, at 11:41 AM, Marco Pesenti Gritti wrote:
Looks like I don't have access to that part of teamwiki... Are you
planning to make this public?
Marco
On 9/18/07, John Watlington [EMAIL PROTECTED] wrote:
Marco,
I apologize that this was discussed at a school server meeting
and we didn't
point you at the results.
Details are at:
http://laptop.org/teamwiki/index.php/Team:SS_Meeting_2007-09-12
On Sep 18, 2007, at 4:21 AM, Marco Pesenti Gritti wrote:
On 9/18/07, Kim Quirk [EMAIL PROTECTED] wrote:
Do we have another solution for being able to find a file after
the journal
has saved it to the school server?
How are backups to the school server going to be handled for
trial-3?
It think the proper long term solution the remote datastore stuff
Ben
has been thinking about (and designed the datastore to support), but
clearly that's not going to be ready for trial-3.
Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
