1.9.0: Improved physical drive reporting

Features:

• extend reported drive details on --detailed #140
  from:

  [CRITICAL]: Physical Drive NonRAID Solid State Disk 0:1:0 (Dell Ent NVMe CM6 MU 1.6TB / SSD / PCIe) 1599.74GiB status: CRITICAL
  [OK]: Physical Drive TOSHIBA KPM51MUG800G (0) (KPM51MUG800G / SSD / SAS) 800.17GiB status: OK
  [OK]: Physical Drive (2I:1:6) 240GB status: OK
  

  to:

  [CRITICAL]: Physical Drive NonRAID Solid State Disk 0:1:0 Failure predicted: True (Dell Ent NVMe CM6 MU 1.6TB, SSD, PCIe, Media life left: 100%, Status: Enabled) 1599.74GiB status: CRITICAL
  [OK]: Physical Drive TOSHIBA KPM51MUG800G (0) (KPM51MUG800G, SSD, SAS, Media life left: 100%, Status: Enabled, Hours on: 181) 800.17GiB status: OK
  [OK]: Physical Drive (2I:1:6, VK000240GWSRQ, SSD, SATA, Media life left: 89%, Status: Enabled, Hours on: 19415) 240.06GiB status: OK
  

• add physical driver performance data (temp, power on hours, media lifetime left) #142
• add warning/critical if physical drive media life time gets below certain values #143

Bugfixes:

• fixes issue with reported memory status on detailed view if all modules reported OK but memory subsystem had an issue #141
• fixes issue with disabled drives on Cisco servers #144

Possible breaking changes

Using --warning and --critical values for --mel and --storage at the same time will cause issues as these apply to both checks.

Thanks to @HHerrgesell for the contributions

1.8.1: fixes sessionlock option

BugFix

• fixes --sessionlock option in order to actually write a session lock file

1.8.0: Adds session lock option #132

Features:

• added option --sessionlock which prevents multiple sessions and locks the session file when connecting (#132)

Bugfixes:

• adds condition to check for internal error on HPE iLO5 #130

Documentation

• enhances README in regards of iLO IML critical and warning #133

Thanks to @itsul for the contributions

1.7.3: improves reporting of storage components on newer iLO5 firmware

• improves reporting of storage components on newer iLO5 firmware #128 #129
• fixes issue with misbehaving iLO firmware for Storage response #129

1.7.2: sets physical drive predicted failure alarms to CRITICAL

• sets physical drive predicted failure alarms to CRITICAL #126

1.7.1: add IP address prefix length to interface data and inventory output

Features:

• adds IP address prefix length to interface data and inventory output #125

1.7.0: iLO 6 support and improved storage and network data handling

Features:

• adds iLO6 support #116
• return status data in a predictive order #115

Bugfixes:

• fixes issue with with failed logout on --no-session option #119
• fixes issue with parsing NVMe storage more then once #113
• fixes issue with network information on iLO 6 interfaces #116

1.6.1: fixes issue with reading network port information

Bugfix:

• fixes issue with alternative json object data for network ports and functions on SuperMicro systems #118

1.6.0: adds flap detection and a few bug fixes

Features:

• adds flap detection for log entries #108

Bugfixes:

• Fixes a bug where disabled power control would become CRITICAL #105
• Fixes 'ALREADY IN INVENTORY' message in --nic #109
• Fixes bug showing incorrect status when server is powered off #110
• Fixes bug causing error when parsing certain network interface data #100
• Fixes bug causing in mode --firmware which also checks --storage -> and returns request error #112
• Fixes issue with deterring host name on different platforms #117

Some code has been refactored to simply internal interfaces.

1.5.0: adds security state for HPE ILO, fixes parsing of network ports

Features:

• Adding iLO5 security state to manager data and new flag --enable_bmc_security_warning #95
• Adds certain SSD drives for Fujitsu server with firmware issues
• Adds support processor type GPU in inventory #101

Bugfixes:

• Fixes issues with missing root objects #98
• Fixes issue with wrong variable names in Icinga service example #92
• Fixes issue with unavailable network port information #100
• Fixes discovery of all NIC ports #102

Thanks to @SamuelePilleri and @zvfvrv for their contribution, this is highly appreciated.