i.e. in the case of VRF, the physical node is the master. Other modes of
operation that are similar to VRF exist (including VDC).

…ances

In the case of a master netbox, duplicate all collected port metrics
across all instance netboxes when shipping to Graphite.

In the case of a virtualized instance, just debug log a list of local
ports (that do not appear on the master) and exit.

There is _no_ collection of data from local ports at the moment, as this
would require a complete restructuring of things (i.e collection from
individual ports, rather than full column snmpwalks for the values we
want)

instead, have the eventengine make copies of linkState events for master
devices.

tests and doc updated.

i.e. in the case of VRF, the physical node is the master. Other modes of
operation that are similar to VRF exist (including VDC).

…ances

In the case of a master netbox, duplicate all collected port metrics
across all instance netboxes when shipping to Graphite.

In the case of a virtualized instance, just debug log a list of local
ports (that do not appear on the master) and exit.

There is _no_ collection of data from local ports at the moment, as this
would require a complete restructuring of things (i.e collection from
individual ports, rather than full column snmpwalks for the values we
want)

instead, have the eventengine make copies of linkState events for master
devices.

tests and doc updated.

…stances

…tances

Remove redundant collection of system and sensor stats in cases of virtualized device instance

SeedDB is, IMNSHO, overdue for a rewrite. The way it's written makes it
really hard to do anything useful outside of building tables of text
strings.

This hack will at least enable any custom templates to access the
original model object of each row, instead of a list of dicts containing
compressed attribute strings :-P

Implemented as a custom template overriding the row logic for netbox
lists.