Re: [Acd-devel] Proposal for DB design

[Scott M. K. <ko...@cs...>]

On Thu, Dec 16, 2004 at 12:01:01AM -0500, Matt Disney wrote:
> >
> >I guess we still face the fundamental deficiency previously mentioned 
> >with the schema originally proposed by Josh and Scott: how to deal with 
> >things like disks that have serial numbers?
> >
> >MD
> 
> Josh and I briefly discussed the possibility of not supporting disk 
> serial numbers. But aren't network interfaces the same kind of thing? 
> Assuming they are, I think we're stuck having to support that kind of 
> non-repetitive data. Well, you could make the case that we should also 
> ignore the IP and subnet of the net interfaces, but I would disagree 
> since knowing what networks a box is on is a big win for ACD.
> 
> So I think those tables should basically just look like we currently 
> have them:
> 
> network_interfaces
>   interface_device
>   hardware_addres
>   netmask
>   ip
>   instance_id
> 
> I understand that leaves us simply with a different but still somewhat 
> undesirable database design, but I don't see another way. Anyone have 
> other ideas or oppose this one?
> 
> MD
> 
> 

One idea that comes to mind is to store the unique info such as IP's, serials,
etc. in flat files or using some other method.  The way I see it is 
combining the disk serials, IP, etc.. with the type of info that is currently 
in the acd_manual_info files into a single file stored on the server for each 
host.

I think this would solve/clean-up our database issue, but is  there a way to
do this without losing functionality?  The only problem I forsee is keeping
historical information on the data in these files efficiently. There is 
something else to thing about.

-Scott