These were accidentally overwritten by the sensor registration changes.
They belong in their own file anyways so the code has been split and the registration
moved to a common location.
Rework snmp oid registration so that the temperature, fan, and PSU oids are registered as netsnmp tables. When a sensor is added or deleted, the corresponding table is updated accordingly.
The following new APIs are introduced:
onlp_<subsystem>_status_get()
- Retreives only the operational status (PRESENT, FAILED, UNPLUGGED) of the object
Useful for improving the performance of the platform manager, whose primary concern
is the operational status, not the object information itself.
onlp_<subsystem>_hdr_get()
- Retrieves the OID header (description, parent, children) only.
Improved performance of OID iteration by avoiding collection of all
of the unused object information during execution.
If a platform does not implement these functions they will be simulated using
calls to the existing onlp_<subsystem>_info_get(), which reduces to the
original performance level.
Some platforms do not provide direct device access to the ONIE system eeprom.
The only way these systems can export their system data under ONL is by scraping it
from the output of onie-syseeprom and/or reading fields from machine.conf.
These new platform methods can be called in a platform's baseconfig() to
populate the cached version of these values for later use, or used
to access that cached data at a later time.
- single run() method is called with a mode argument
- plugin objects are persistent (re-entrant) for the lifetime of the install
- installer grovels the filesystem and/or zip file for plugin files
The ONIE firware upgrade staging area is not initialized properly if we don't first boot into ONIE after
the initial upgrade. This causes our workflow of ONIE then CPLD upgrade to fail the first time.
The onie-fwpkg script does not report an error about the staging area which is why our code
is not detecting the failure to install the firmware package.
