Your SlideShare is downloading. ×
XO Laptop School Server (John Watlington)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

XO Laptop School Server (John Watlington)

1,129
views

Published on

OLPC Country Meetings May 21, 2008. …

OLPC Country Meetings May 21, 2008.
http://wiki.laptop.org/go/Presentations/May_2008_Country_Workshop

Published in: Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,129
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. One Laptop per Child School Server May 20, 2008 One Laptop per Child
  • 2. School Server
    • A set of software which provides:
      • A Network Gateway
      • Centralized school services
      • Content services
    • (future) A reference design for a low power, low cost server hardware platform
  • 3. School Server
    • Networking
    • Services
    • Hardware
  • 4.  
  • 5. A Network Gateway
    • Provides the connection between the school network and the “Internet”
    • Allows the school server to provide:
      • Network filtering
      • Content caching
    • Not required for larger school w. dedicated network infrastructure
  • 6. Networking Services
    • Full function IPv4 network gateway
    • Address assignment (DHCP)
    • Name resolution (DNS)
    • HTTP Caching
      • Maximizes use of Internet connection
  • 7. School Server
    • Networking
    • Services
    • Hardware
  • 8. Services (now)
    • Time
    • Registration
      • Associates a laptop with a school
    • Presence & Collaboration
      • Centralized service needed when more than 30 laptops together
    • HTTP caching
      • Efficient use of Internet connection
  • 9. Registration
    • One-time process linking a laptop and a school
    • Essential for a student to collaborate in school
    • Currently in menu ->
    • Automatic in future laptop releases
  • 10. School Collaboration
    • In a school, a centralized presence service aids presence and collaboration
    • Without service, collaboration limited to small number (< 15-30) of laptops
    • Currently XMPP (jabber) based
    • Laptops may collaborate remotely, if:
      • They are registered to the same school, and
      • They can both connect to presence service
  • 11. Services (3Q 2008)
    • Laptop backup to XS
    • Moodle
      • User/Group management
      • Partially Sugar-ized UI
      • Web-based collaborative activities
    • MediaWiki
      • Editable copy of Wikipedia slice
      • Content updates
    • Tools for bundling HTML content
  • 12. Services (2009)
    • Smarter HTTP proxy behavior
    • HTTP Filtering
    • Cross-school content sharing
    • Some support for disconnected operations
    • Bitfrost-integrated white/blacklisting
  • 13. School Server Administration
    • (Future releases)
    • Tools for a Network Operations Center
    • Remote school server management and monitoring
    • Software and content updates
    • Backup of school server
    • Scalable --- small network operations team can handle a large server base
    • Bitfrost blacklist/whitelist maintenance
  • 14. School Server
    • Networking
    • Services
    • Hardware
  • 15. Server Hardware
    • No single solution provided by OLPC
    • Currently recommending off-the-shelf hardware:
      • 1+ GHz x86 processor
      • 1 Gbyte of RAM
      • Two network interfaces
      • Four USB 2.0 ports
      • 400+ GB of Hard Drive
  • 16. Rural School Server
    • Difficult to find low cost hardware for environmental extremes
    • Water drip resistant
    • 50C operation
    • No critical fans
    • Little economies of scale