 |
Amalgam
def: a mixture of different elements |
|
Managing multiple Operating Systems under a single administrative umbrella
|
|
|
Design Docs
|
| UML
|
Schema [top]
 |
Basic relational schema.
Included is a possible control by user to clients *shrugs* not
sure if that is even necessary. Will wait on some feedback
for that. |
|
User Case [top]
 |
Nothing special. An
outline of the basic set of features that are to built into the
system upon the first release. |
|
Client [top]
 |
As a remote client, a
connection must be maintained at all times to ensure the server
can communicate back to the client once a command it given from
the admin-client.
The client can also, via the built in 'cron' feature send
heartbeats or transmit data to the server on a scheduled basis.
|
|
Server [top]
 |
The server is the most
complicated piece since it involved united two separate pieces
together, the client and the admin-client. Aside from a
simple proxy model, the server keeps track, via the database, of
what modules each client has and what groups are associated by the
admin. |
|
Admin Client [top]
 |
The admin client is
relatively simply. Connect and login to the server, display the
clients and their associated modules that are registered with the
repository.
Commands can then be issued to the clients individually or by
groups.
|
|
|
Copyright
©2005 Steve Gee, All Rights Reserved
|
