[Server-devel] Server Admin Interface

[John Watlington]

What would an administrative interface for the school server provide ?

The scripts I've written (things that have needed configuration so far):
- change the domain name of the school
    Coming in tonight's build to handle the mess of file editing  
currently needed.
    This should only be done once.   If done after ejabberd starts up  
for the first time,
    ejabberd will crash and refuse to run.
- configure the LAN networking.  Done automatically on first boot  
assuming a server
   has an ID of 1, and rerun manually to assign another ID  
(additional servers in a school).
   This absolutely should not be changed, as laptops will be bound to  
a particular server
   for their backup.
- configure the role of the server (is it the principal server in a  
school, running primary
    versions of services ? or an auxiliary server just running the  
distributed services ?
    This should be easily changeable (perhaps even automatic in the  
case of a failure of
    the principal server.)

- There needs to be an easy way to configure the WAN interface.  We  
don't have a handle yet
    on all the different interfaces we might have to work with  
(PPPoE ?  PPPoA ?).
    This might change at any time.

There is a whole level of "school interface" needed (adding/removing  
students, fixing
things after a student's laptop is replaced, etc) but that is  
different from the admin interface
and needs much more careful interface design.

Cheers,
wad