Central "Asset" thing
introduction
I've been thinking about the need for a central database of our
systems.
Currently, we have
- some stuff in our wiki
- some stuff in munin
- some stuff in paul's asset db
- some stuff in lorna's
- some stuff in nagios
- more?
It would be nice to have a central place for this sort of thing and to
push out config files for the others based on that data. So, to model
what we have. Starting from the bottom.
thoughts about the model
At the bottom we have machines. These come and go. They have some
attributes in common that are useful to other things: manufacturer/model
impact the kind of manufacturer-specific monitoring we might have
available to us, also what kind of disk stock for replacements we have
available.
Also what kind of remote access is available, whether they have dual
power, etc.
Machines have a location. they are in sb12, nb1, databanx...
Next level up, we have hosts. Hosts are not 1:1 matched to machines. E.g.
we have had more than one finan.
Then, we have services. they are a high-level concept. Services run on top
of hosts, but they are not 1:1 again.
The whole lot is connected by the network. There are dependencies on
paranahs etc.
current model
first, machines:
| Field | Type | Null | Key | Default | Extra |
|---|
| id | int(11) | NO | PRI | | auto_increment |
then hosts, tying them to their current machines:
| Field | Type | Null | Key | Default | Extra |
|---|
| id | int(11) | NO | PRI | | auto_increment |
| current_machine | int(11) | YES | | | |
| name | varchar(32) | YES | | | |
we need services, although not sure what to give them yet:
| Field | Type | Null | Key | Default | Extra |
|---|
| id | int(11) | NO | PRI | | auto_increment |
sample data