Version 104 of the Docker PowerPack addresses several container aggregation issues.
- Minimum Required SL1 Version: 8.7.1.2
Before You Install or Upgrade
Ensure that you are running version 8.7.1.2 or later of SL1 before installing "Docker" PowerPack version 104.
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
To install version 104 of the Docker PowerPack, perform the following steps:
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.
If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.
To install this PowerPack:
- Familiarize yourself with the Known Issues for this release.
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 8.7.1.2 or later release.
- Download the "Docker" version 104PowerPack from the Support Site to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. When prompted, import "Docker" version 104.
- Click the 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 Basic/Snippet Credential and 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 version 104 of the "Docker" PowerPack:
- A new Run Book Action, "Docker: Vanish Timer Update Status Write", was added to the PowerPack. In conjunction with a new "Docker: Vanish Timer Update" Event Policy and the existing "Docker: Component Vanish Timer Update" Run Book Policy, this new RBA will update vanish and purge timer thresholds whenever new components are discovered.
- The "Docker: Container Configuration" Dynamic Application was updated to ensure that dynamic component map relationships display correctly on the Device View (Registry > Devices > Device Manager > graph icon > Topology) and Device Component Map (Views > Device Maps > Components) pages.
- An issue was addressed that was preventing swarm performance and service container configuration data from being aggregated at the swarm component.
- An issue was addressed that was causing the "Docker: Container Performance" Dynamic Application to not cache performance data properly.
Known Issues
The following known issues affect version 104 of the Docker PowerPack:
- When the PowerPack is used in conjunction with the Linux Base Pack PowerPack, a conflict arises wherein both PowerPacks attempt to classify the Docker Device Classes. To avoid this conflict, disable the "Linux Classification and Automation" Run Book Action in the Linux Base Pack PowerPack.