MassMaintenance

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2007-10-31 16:30:39 →
Size: 3683
Editor: 12
Comment:
← Revision 2 as of 2007-10-31 16:38:34 → ⇥
Size: 2855
Editor: 12
Comment:
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Line 32: Line 30:

Include:
 * data migration, if any
 * redirects from old URLs to new ones, if any
 * how users will be pointed to the new way of doing things, if necessary.
Line 40: Line 33:
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during CD testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.
Line 45: Line 34:

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
Line 50: Line 37:
* User Management  * User Management
Line 52: Line 39:
  * Open Account Provisioning System (OAPS) tries to do this kind of thing. It's used to automatically create accounts, deactivate them and so on. https://svn.revolutionlinux.com/OpenRevolution/OAPS/
* Box Management		   * Open Account Provisioning System (OAPS) tries to do this kind of thing. It's used to automatically create accounts, deactivate them and so on. https://svn.revolutionlinux.com/OpenRevolution/OAPS/
  ==== Tools ====
 * General information about management software : http://en.wikipedia.org/wiki/Comparison_of_open_source_configuration_management_software
Line 55: Line 44:
==== Tools ====
* General information about management software : http://en.wikipedia.org/wiki/Comparison_of_open_source_configuration_management_software

* Puppet: http://reductivelabs.com/trac/puppet		  * Puppet: http://reductivelabs.com/trac/puppet
Line 62: Line 48:
* Cfengine
* Bcfg2 : http://trac.mcs.anl.gov/projects/bcfg2 This tool models really well a system so it's possible to get a declarative spec, not a procedural one.
* webmin (note that we will use ebox by default for web-based maintenance it provides similar functionality)		  * Cfengine
 * Bcfg2 : http://trac.mcs.anl.gov/projects/bcfg2 This tool models really well a system so it's possible to get a declarative spec, not a procedural one.
 * webmin (note that we will use ebox by default for web-based maintenance it provides similar functionality)
Line 67: Line 53:
* Lanscape (http://www.canonical.com/projects/landscape)  * Lanscape (http://www.canonical.com/projects/landscape)
Line 70: Line 56:
* dsh
* clusterssh
* fanout/fanterm (http://www.stearns.org/fanout/README.html)		  * dsh
 * clusterssh
 * fanout/fanterm (http://www.stearns.org/fanout/README.html)

Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

Edubuntu is often used in situations with large numbers of systems and users; we will provide tools to maintain these large networks.

Release Note

Rationale

Maintaining 10.000 thin clients, 17.000 desktops/laptops, and 80.000 users dispersed over 10.000 square kilometers is very difficult when you only have the Gnome user manager and you have to ssh into every system to do maintenance.

Use Cases

Assumptions

Design

Implementation

UI Changes

Code Changes

Migration

Test/Demo Plan

Outstanding Issues

BoF agenda and discussion

Tools

  • General information about management software : http://en.wikipedia.org/wiki/Comparison_of_open_source_configuration_management_software

  • Puppet: http://reductivelabs.com/trac/puppet

    • good for ensuring a small number of particular users exist locally on a large number of systems
    • great for mass BOX management
    • can do very well in a remote situation, such as a WAN
  • Cfengine

  • Bcfg2 : http://trac.mcs.anl.gov/projects/bcfg2 This tool models really well a system so it's possible to get a declarative spec, not a procedural one.

  • webmin (note that we will use ebox by default for web-based maintenance it provides similar functionality)
    • has security problems, bad reputation
    • has good bulk-import and user management interfaces that even work for Samba/LDAP

  • Lanscape (http://www.canonical.com/projects/landscape)

    • This is a service from Canonical, and can offer much of this functionality.
    • This is not the primary solution for solving these issues in Edubuntu.
  • dsh
  • clusterssh

  • fanout/fanterm (http://www.stearns.org/fanout/README.html)

    • The next sessions should be attended by a person from the server and the landscape team, ogra will care for them to be subscribed.
    • Also, moquist has contacted Luke Kanies (puppet project lead) to see if he can attend remotely
    • Jorge Castro has put puppet into production as well; would be good to get his input

CategorySpec

Edubuntu/Specifications/MassMaintenance (last edited 2010-01-21 18:43:01 by 196-210-177-89-wblv-esr-3)