DockerPowerPack Release Notes, version 108

Version 108 of the "Docker" PowerPack updates the PowerPack to make it compatible with Python , addresses an issue with the "Docker: Host Device Class Realignment" run book action, and adds a device template to use if Dynamic Applications fail to align automatically during discovery.

  • Minimum Required SL1 Version: 11.3.0

Before You Install or Upgrade

Ensure that you are running version 11.3.0 or later of SL1 before installing "Docker" PowerPack version 108.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

You must also enable the Docker API. For instructions, see the Monitoring Docker manual.

Installation or Upgrade Process

By default, installing a new version of a PowerPack will overwrite all content in that PowerPack that has already been installed on the target system. You can use the Enable Selective PowerPack Field Protection setting in the Behavior Settings page (System > Settings > Behavior) to prevent the new version of the PowerPack from overwriting local changes for some commonly customized fields.

To install this PowerPack:

  1. Familiarize yourself with the Known Issues for this release.
  2. See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 11.3.0 or later release.
  3. Download the "Docker" version 108 PowerPack from the Support Site to a local computer.
  4. Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the Actions menu and choose Import PowerPack. When prompted, import "Docker" version 108.
  5. Click the Install button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.

Features

This release includes the following features:

  • Dynamic Applications that discover and collect data from Docker component devices
  • Device classes for each type of Docker component device monitored
  • Event policies that are triggered when Docker devices meet certain status criteria
  • Run book actions and policies that automate some aspects of the device discovery and creation process
  • An example SSH/Key credential for discovering Docker devices
  • Device dashboards that display information about Docker component devices

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in this release:

  • Updated the PowerPack to be compatible with Python 3.6

  • Addressed an issue that caused the "Docker: Host Device Class Realignment" run book action to activate incorrectly in certain situations. As part of the fix for this issue:

    • The "Docker: Hosts and Swarm Cluster realignment to CU id of the leader node" event policy will only be triggered by the leader node.

    • If one or more nodes are not discovered, they will not be taken into account when deciding whether to trigger the event.

    • The run book action now uses the IP address instead of the hostname to read the cache, because the cache is saved using the IP address. (Case: 00424553)

  • Added the "Docker Template Example" device template that you can apply to root (Docker Host) Docker devices if the required Dynamic Applications fail to align automatically during discovery.

  • Made several modifications to example credentials in the PowerPack.

Known Issues

The following known issues affect version 108 of the "Docker" PowerPack:

  • The "Virtual Size" collection object in the "Docker: Image Configuration" Dynamic Application is obsolete in version 108 of the PowerPack due to the data being removed from the API in version 1.43 of the Docker API.
  • The "Docker: Container Performance" Dynamic Application getting more than 100% of CPU usage is an expected Docker behavior. SL1 will report CPU usage peaks just as it reports it on the Docker CLI. CPU usage can exceed 100% depending on the number of cores the container has. For example, two CPUs can report numbers up to 200%, three CPUs can report up to 300%, and so on.
  • If a discovered device is reporting the "Device Failed Availability Check: UDP/SNMP check requested but invalid or no credential was specified" message, ensure that the Availability Port field in the Device Properties page (Devices> Classic Devices > wrench icon) is configured as ICMP/ICMP.