[Demi-devel] Demi requirements

[Leo Eraly]

Hi,

This is the first list of requirements that I think could be usefull 
in demi. Mainly inspired by the features we need at work and the
features in my current versionner.


- Central overview of all machines
- Central overview of all installed software on machines
- Central overview of which machines are not up to date (compare status
  file with the security.debian.org file)
- Assign machines to a specific customer (entity)
- Assign a user to a customer by doing this the person is the main
  contact for all the machines of this customer
- Put certain packages on machines on hold (this allows possible
  conflicts - by doing this a certain package will not show up as 'not
  up to date' - e.g when using backports)
- Put a complete machine on hold
- Mark a machine as supported/unsupported
- Allow a backlog of all the packages per machine that are upgraded
- Machine should pull its current packages list after every apt-get
  instruction (Post-invoke)
- Central server polls at certain interval all the hosts
- Create machine-groups and put machines in different groups
  (e.g: group of machines that offers public services)
- Specify a different ssh port for every machine (not every machine has
  ssh on port 22)
- Allow specific reports (generate pdf's , html pages , ...)
- Make notes on every machine (usefull with multiple engineers)

Should you use one ssh key to poll all the machines or a different key
for every host?

More will follow but this is my first shot ;)

L.

-- 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Leo ERALY		
leo at e-concepts.be
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++