[Demi-devel] The much awaited database schema...
Andrew Pollock
apollock@debian.org
Sun, 28 Mar 2004 14:31:34 +1000
On Sat, Mar 27, 2004 at 09:27:42PM -0500, John Morrissey wrote:
> On Thu, Mar 18, 2004 at 09:28:04AM +1000, Andrew Pollock wrote:
> > I thought about having a separate table for packags and versions, but I
> > didn't think the extra joining involved was worth it to reduce the data
> > redundancy.
>
> The joins should be pretty cheap, since they'll be on indexed columns and
> (some of the time, at least) joined on constant values.
Hmm okay. I also had a thought this morning about storing a timestamp for
when a host was last polled, so that there is some indication of hosts where
polling has started failing for some reason.
> > With user access levels, I was really only envisaging two, maybe three at
> > the most, a read-only level that could essentially just run reports and
> > monitor the situation, a read-write level, that could add hosts, and
> > possibly a read-write-update level, that was allowed to trigger updates on
> > remote hosts (or just roll this level into the read-write level).
>
> I'd like a separate level that only allows adding hosts; it would be very
> useful in our automated install procedure without giving that automated
> account too many privileges. Perhaps a bitmask-like system where a given
> user could have ADD, READ, and/or WRITE/UPDATE permission bits on a given
> system or group of systems?
Fair enough. I'll factor that in.
regards
Andrew