You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Phase 1: SVN 1.4 upgrade

This phase will focus on ironing out the details of the IPS-to-OIS rollout process.  The test server map-dev-svn1 will be set up to duplicate the features and user management of the existing svn.mit.edu service, with an upgrade to SVN 1.4.x being the only new user-visible feature.  The new service will be rolled out to OIS and existing repositories migrated.  svn.mit.edu will become separate from cvs.mit.edu at this time.

Phase 2: DAV, ra_svn, MAP passwords, possibly SVN 1.5

An IPS standard Apache HTTPD 2.x installation will be added to map-dev-svn1. The SVN server will be rebuilt with support for DAV (http(smile) and ra_svn (svn: without the SSH tunneling).  DAV access will support authentication with Kerberos, MIT certificates, and passwords over SSL.  ra_svn access will support authentication with passwords and possibly Kerberos.  Both access methods will also support anonymous read-only access if repositories are appropriately configured.

If Subversion 1.5 has been released by the time this phase gets underway, it will be used for this phase.  Subversion 1.5 is a requirement for Kerberos ra_svn authentication.

A new administrative web application, itself a MAP project running under Tomcat (probably without SASHServer), will be developed for this phase.  Initially the only feature of this application will be the provisioning of MAP passwords.  Users will authenticate to the application with certificates (or Touchstone if that's an option at this point in time) and will have the option to create, destroy, display, or change their MAP passwords.  Users do not get to choose MAP passwords; they are randomly assigned.  MAP passwords are only recommended when stronger authentication is not an option.  The web application will store a master list of MAP passwords, and a script will propagate the passwords to the /etc/shadow file (for SSH authentication) and to the svnserve and HTTPD password files.  MAP passwords eventually be reused when appropriate for other pieces of MAP infrastructure running on src.mit.edu and build.mit.edu, such as Bamboo.

Phase 3: Expanded administrative features

The administrative application will be extended to support new features, which can be rolled out one at a time.  Likely features include:

  • Manage the authorized_keys file of a user account, and allow public key authentication for SSH.
  • Configure commit emails for a repository.
  • Manage access control for a repository.
  • Manage integration of a repository with other MAP infrastructure such as Bamboo.
  • Receive a partial or complete dump file of a repository.
  • Post a dump file to be loaded into a repository.
  • Automatically provision a new repository for an existing -users and -admin group, to faciliate one project per repository.

In parallel with the above, the following new user management features will be implemented:

  • Support for users without Kerberos principals.  Touchstone and CAMS are prerequisites for this.
  • -admin groups; these are subsets of -user groups and control who has access to manage a repository through the web application.
  • No labels