Version 101 of the VMware Automation PowerPack adds support for memory management when multiple actions that use the "Get VMware Diagnostic Logs" action type are included in a single automation policy. This release also fixes several defects.
This PowerPack is intended to supplement the VMware: vSphere PowerPack.
- Minimum Required SL1 Version: 8.10.0
Before You Install or Upgrade
Ensure that you are running version 8.10.0 or later of SL1 before installing "VMware Automation" PowerPack version 101.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
IMPORTANT: For best results, install and configure the VMware: vSpherePowerPack before using "VMware Automation" version 101.
IMPORTANT: To provide output formatting in HTML or plaintext, you must also install the Datacenter Automation Utilities PowerPack.
Installation or Upgrade Process
To install version 101 of the VMware Automation PowerPack, perform the following steps:
- See the Before You Install section. If you have not done so already, upgrade your system to the 8.10.0 or later release.
- Familiarize yourself with the Known Issues for this release.
- Download the VMware Automation version 101 PowerPack to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. Import the VMware Automationversion 101 PowerPack. For details on importing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- Click the button. For details on installing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- See the Run Book Automation manual for instructions on using Action Type contained in the new PowerPack.
See the VMware Automation PowerPack manual for instructions on using the new PowerPack.
Features
This release includes the following features:
- Automation Policy that is triggered when events occur:
- VMware Automation: Get VMKernel Log and Syslog (VA-11)
- Automation Actions that you can configure to collect additional diagnostic information when events occur:
- Get VMware Diagnostic Logs (VA-8)
- Get VMware VMKernel Log and Syslog (VA-10)
- Custom Action Type that you can use to create new automation actions:
- Get VMware Diagnostic Logs (VA-1)
Enhancements and Issues Addressed
The following enhancements and addressed issues are included this release of the "VMware Automation":
- The "Get VMware Diagnostic Logs" action type can now be used with the "Calculate Memory Size for Each Action" automation action, which is included in the Datacenter Automation Utilities PowerPack, to include multiple collection actions in the same automation policy. (VA-14)
- The mechanism for getting credential information from the root device for VMware Host servers now works correctly. (VA-18)
- The "Get VMware Diagnostic Logs" automation action is now called "Get All Available VMware Diagnostic Logs". The number of lines collected from each log file is now 10. (VA-19)
- The PowerPack has been renamed "VMware Automation". (VA-20)
- Error handling for API connection problems (for example, if the user has incorrect vSphere permissions) has been improved. (VA-22)
Known Issues
This release has no known issues.