Roadmap and an architecture to fulfill it

[Joost van Baal]

On Mon, Jun 18, 2001 at 01:26:47PM -0700, Christoph Lameter wrote:
> On Mon, 18 Jun 2001, Joost van Baal wrote:
> 
> > On Fri, Jun 15, 2001 at 01:31:32PM -0700, Christoph Lameter wrote:
> > > I have talked with Francis a lot today on IRC on how to reach the goals.
> > > A key element is the ease of handling and the configuration of the whole
> > > system. Many of the components are the typical import,export,generate
> > > summaries/report stuff known from databases. That why we thought it would
> > > be useful to store the data in a SQL database
> >
> > An SQL database allows a relational database.  Currently, we use only
> > _one_ table.  If we go for an sql database, we have to consider this.
> > Is it usefull to use sql, even though we're not using multiple tables?
> > Or would we like to _go_ using multiple tables?
> 
> We need multiple tables for the different log formats. DLF formats are
> distinct depending on the service.

Currently, a postfix logfile gets converted to an email dlf file.
This dlf file looks the same as the one which would've been generated
in case when the host running postfix would have run sendmail.

I don't see how multiple tables would occur when building an sql database
from one logfile.  That's what my question was about.

> > > Using a SQL database would mean that we already have a powerful query
> > > language doing aggregation, selecting, sorting and all the other stuff
> > > needed for effective data processing. Each of the DLF service structures
> > > would require a corresponding SQL table to be generated. Databases are
> > > generated by customer.
> >
> > What do you mean by 'customer'?
> 
> The person/entity wanting the report? Data needs to be separatable for the
> clients.

I asked this since it occurred in discussion we had in the past.
There have been (yet unsolved) issues on building lists which link
services, machines and customers.  When we are able to merge reports,
we should have a mechanism to find out where to sent merged report to
(and to find out which reports to merge.)

I'd like to get some way operational to automatically sent weekly
reports to people submitting their logs to the online responder daily.
Don't know how to implement this yet, though.

> > > deployed. The issue of having the wrong version of tools does not arise.
> > > Deploy is very simple since the complete operating system is deployed. The
> > > deployment as an add-on onto existing operating systems (Sun, BSD etc) is
> > > still possible but carries with it the usual problems. The difficulty
> > > might increase since a SQL database and a webinterface might become
> > > necessary if we go down this route.
> >
> > I would very much like to keep supporting Solaris, OpenBSD and FreeBSD.
> > Perhaps we could fully support a commandline interface on these
> > platforms, and support webfrontends only on GNU/Linux platforms.
> > I would very much regret is if we would only support Debian GNU/Linux.
> 
> Well the problem is the effort of maintaining it on all platforms. All the
> components are available on all platforms. But we need to have the knowhow
> of all these tools on all platforms in order to make our stuff available.

True.  I go for it.  :)

Bye,

Joost



-- 
To UNSUBSCRIBE, email to development-request at logreport.org with a subject of 
"unsubscribe". Trouble? Send an email with subject "help" to 
development-request at logreport.org