-
Notifications
You must be signed in to change notification settings - Fork 19
Acceptance Criteria
During testing you will be comparing the behavior of the old Windows ZenPacks to that of the new one.
Old Windows ZenPacks:
- PySamba
- WindowsMonitor
- ActiveDirectory
- IISMonitor
- MSExchange
- MSMQMonitor
- MSSQLServer
New Windows ZenPacks:
- PythonCollector
- Microsoft.Windows
Set up two machines running Zenoss for each version being tested. One machine will run the old Windows zenpacks. The second machine will run the new Windows ZenPack. This will allow you to compare the results of modeling, the graphs, and events for both the old and new ZPs.
The old and new ZenPacks use different Device Classes.
- Old - Devices/Server/Windows/WMI
- New - Devices/Server/Microsoft/Windows
Devices/Server/Microsoft/Windows should have all zenoss.winrm.* modeler plugins bound to it, and no zenoss.wmi.* plugins bound to it. Devices/Server/Windows/WMI will have zenoss.wmi.* plugins bound to it (but not all), and it should not have any zenoss.winrm.* plugins bound to it.
The type of all the datasources in the new ZenPack should be "WinRS Single Counter". The type of the datasources in the old ZenPack should be "WinPerf".
Both ZenPacks use the same Configuration Properties (aka zProps) for setting the username and password. These are zWinUser and zWinPassword. The old ZenPack supports NTLM authentication for local Windows accounts. The new ZenPack supports Basic authentication for local accounts and Kerberos authentication for domain accounts. Support for NTLMv2 is planned before for the initial release. If you have multiple target Windows machines that share the same credentials you can create sub-DeviceClasses and configure zWinUser and zWinPassword on the device class. For kerberos authentication zWinUser should be in the form username@domain (e.g. bedwards@solutions.loc). The software will key off the fact that zWinUser has an '@' character in it and automatically use kerberos authentication.
Another Test scenario is having both old and new ZenPacks running on same Zenoss instance. You won't be able to monitor the same device with both because the system does not allow for duplicate management IP addresses without the MultiRealmIP ZenPack installed. You will be able to test that various devices can be monitored and modeled with both ZenPacks and a device can be moved from the device class of one ZenPack to the other.
Past Iterations
- Windows OS Modeling
- Windows IIS Modeling
- Windows Services Modeling
- Windows OS Monitoring
- Active Directory Monitoring
- MS SQL Server Monitoring
- Ethernet Interface Monitoring
- MS Exchange Monitoring
- Filesystem Monitoring
- IIS Monitoring
Current Iteration
- US926: powershell get-counter listset datasourcetype
- US923: Multiple counters per typeperf command in data source
- US918: Thresholds and Graphs from old ZenPack
- US883: Kerberos authentication
- US920: Implement Windows Event Collection
- US862: HA modeling Phase 1
Future Iterations