Arusha Project
ARK (mechanism)
 
How to..., etc.
ARK objects
Configuration language
Package mgmt
`ark' tool
ARK site gen
 
Design, etc.
foo.bar()
Grokking the code
Problems
Ideas
 
Admin, etc.
Glossary
Technologies
Conventions
 
Hosted by
SourceForge.net Logo

Arusha Project driving problems

This document is a ``shopping list'' of things we'd like to be able to do with ARK stuff; it reflects stuff we just haven't done yet, or that we don't know how to do at all...

The casual ARK user can ignore this.

  • Each host's password file includes entries only for users entitled to use that host.

  • Some of a host's configuration may depend on its network state (e.g. connected vs disconnected).

  • Need to ``give away'' control of some of the configuration to others.

  • Each proto-host is basically a binary assertion about a host. Could parameterizing make things simpler? E.g. instead of proto-hosts hpux-amanda-client and hpux-amanda-server, perhaps we could have a proto-host amanda-host(platform,client-or-server)?? (Of course, platform sure looks like the "single descriptor" we were getting away from...)


© The Arusha Project, 2000-2003; team: ARK; c/o partain@users.sourceforge.net; revision 1.4, 2004-05-26.