05.02.2013 Views

opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2 - opsi Download - uib

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>opsi</strong> <strong>manual</strong> <strong>opsi</strong> <strong>version</strong> <strong>4.0.2</strong><br />

21.3 mysql backend<br />

21.3.1 mysql backend for inventory data<br />

Figure 84: <strong>opsi</strong> ldap backend in the Jxplorer<br />

170 / 193<br />

Inventory data at the file backend is stored in structured text files by default. This type of storage is not very useful<br />

if you wish to form free queries on these data. In order to allow free queries and reports a mysql based backend for<br />

the inventory data has been introduced.<br />

The main characteristics of this backend are: * only for inventory data free (for other data it is part of a co funding<br />

project until now) * optional (not the default backend) * a very fine granulated data structure with an additional<br />

table to make queries easier. * a history function which tracks changes in the inventory.<br />

Regarding the very different structure of the components in the inventory the resulting data structure is complex.<br />

The table hosts comprises all known hosts. For every device type we use two tables: The HARDWARE_DEVICE_<br />

.table describes the model without individual aspects like the serial number. The HARDWARE_CONFIG table stores<br />

these individual and configuration data.<br />

These both tables are connected via the field hardware_id. This is the resulting list of tables:<br />

HARDWARE_CONFIG_1394_CONTROLLER<br />

HARDWARE_CONFIG_AUDIO_CONTROLLER<br />

HARDWARE_CONFIG_BASE_BOARD

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!