[osiris-devel] database archiving options

[Brian Wotring]

Many users have stated on this list (and to me) that they would like to 
configure the management console to auto-accept changes (up the trusted 
database) as well as clean up old databases.  I have come up with a 
solution and will present the idea here for comment.

Currently, there are two options for dealing with databases, 1) 
archiving where every scan creates a new database and 2) non-archiving, 
where a new db is created only on detected changes thus saving a record 
of change to for that host,  but not retaining a redundant archive.

One problem with the non-archiving option is that the database store 
for a host can still grow and need to be purged if monitored elements 
are frequently changing.  Another problem is that many people are 
configuring Osiris to monitor anticipated changes, and find it 
cumbersome to regularly have to accept these changes; they simply want 
logs/notifications for these events a single time.

I feel strongly that the current use model should not be effected, only 
extended.  That is, the options to archive and not archive will 
continue to behave in the same way, and an additional options for 
purging the previous database as well as auto-accepting changes be 
added.  Those that don't wish to use the new options can ignore them.

To add these two options, I propose changing the "archive_databases" 
flag in the OSI_HOST and OSI_HOST_BRIEF structures to a bit mask, 
similar to the way notification flags are stored.

There will be three flags, initially:

OSI_DB_ARCHIVE
OSI_DB_PURGE
OSI_DB_AUTOACCEPT

Existing functionality will just make use of the archive flag, on or 
off.  Upon completion of a scan, the db_flags for the host in question 
will be consulted and the trusted database reset if the autoaccept flag 
is set.  If the purge flag is set, the previous database is deleted.

These are minor changes, but will satisfy the many who have asked for 
this functionality while not impacting current use models in any way.  
Any changes will be made after 4.0 is released.  As always, I'm open to 
comments, suggestions, criticisms, etc.

--
     Brian Wotring ( brian at shmoo.com )
     PGP KeyID: 0x9674763D