Currently all extract scripts run as separate standalone programs. While this makes adding in new extract scripts more straightforward, the lack of visibility between them leaves some deficiencies:
It is not possible to ensure a consistent view of the database for all extract scripts in a given run. Machines may be added to DNS, but left of out DHCP until the next run.
More calls to ssh/rsync than are necessary, as each script may cause its own file transfers and scripted actions. Bundling these together would allow for somewhat more efficient runs.
Lack of introspection means it is not possible to view or manipulate the status of the individual extract scripts without per-script code in webint. A good framework would allow webint to query for all installed extract modules and their state.
Addition of new scripts must be reflected in high level script management code.
For a good idea of what such a framework might look like, take a look at how the capture/collect modules are laid out in NetMon.
Currently all extract scripts run as separate standalone programs. While this makes adding in new extract scripts more straightforward, the lack of visibility between them leaves some deficiencies:
For a good idea of what such a framework might look like, take a look at how the capture/collect modules are laid out in NetMon.