Skip to content

QA Instructions

Jump to bottom Edit New page
echun edited this page Aug 14, 2013 · 7 revisions

Installing Zenoss Core and RM

We need to test against Zenoss RM 4.1.1 and 4.2.3 with recommend patch sets (RPS) applied.

Use a CentOS 6 machine. It is highly unlikely that we will have a defect specific to Linux distro / version.

An easy way to install is to use vagrant and VirtualBox. Information is at http://vagrant.zenoss.loc. Before running 'vagrant up' one of the following Vagrantfiles in the current directory, download the box file once and use the local copy many times with the following commands:

Core 4.2.3

$ wget http://vagrant.zenoss.loc/boxes/zen-cent6-Core-4.2.3.box
$ vagrant box add zen-cent6-Core-4.2.3 zen-cent6-Core-4.2.3.box

Vagrantfile

Vagrant::Config.run do |config|
  config.vm.box = "zen-cent6-Core-4.2.3"
  config.vm.network :bridged
end

RM 4.2.3

$ wget http://vagrant.zenoss.loc/boxes/zen-cent6-RM-4.2.3.box
$ wget box add zen-cent6-RM-4.2.3 zen-cent6-RM-4.2.3.box

Vagrantfile

Vagrant::Config.run do |config|
  config.vm.box = "zen-cent6-RM-4.2.3"
  config.vm.network :bridged
end

There is no vagrant box for RM 4.1.1. You could use the cent6 base box and install the 4.1.1 RPM from artifacts on top of it. The 4.1.1 RPM is available at http://artifacts.zenoss.loc/releases/4.1.1/ga/resmgr/

You should apply the Recommended Patch Set on top of RM 4.1.1 and 4.2.3. You should use 4.2.4 instead of 4.2.3 once it comes out. Information on applying the RPS is at...

If for some reason the 4.2.x vagrant boxes don't work for you, then you can get the RPMs on artifacts.

Old and New Windows ZenPacks

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

The old ZenPacks come as part of the Zenoss Core 4.2.x RPM. They can be installed on top of an RM install with the msmonitor RPM which is available at http://artifacts.zenoss.loc/releases/4.2.3/ga/msmonitor/

For the new Windows zenpack you can install PythonCollector from http://wiki.zenoss.org/ZenPack:PythonCollector

Get the latest Microsoft.Windows egg at http://jenkins-ci.zenosslabs.com/job/ZenPacks.zenoss.Microsoft.Windows%20-%20master/

Installing the Kerberos Libraries

For kerberos to work you need to do the following steps (eventually this will be part of the ZenPack install):

  • Install the kerberos C libraries

    $ sudo yum -y install gcc krb5-devel krb5-workstation

  • Install the kerberos python library

    $ easy_install kerberos

  • Generate a krb5.conf file

    $ genkrb5conf --output /tmp/krb5.conf solutions.loc 10.30.1.10

  • Move the krb5.conf file to /etc

    $ sudo mv /tmp/krb5.conf /etc/krb5.conf

Setting up WinRM Service on the Target Windows Machine

Disabled firewall
Run command prompt as Administrator
winrm quickconfig
For WinRM 2.0 and greater(Use 'winrm id' and check Stack):
    winrm s winrm/config/service @{AllowUnencrypted="true";MaxConcurrentOperationsPerUser="4294967295"}
For WinRM 1.1(Use 'winrm id' and check Stack):
    winrm s winrm/config/service @{AllowUnencrypted="true";MaxConcurrentOperations="4294967295"}
winrm s winrm/config/service/auth @{Basic="true"}
winrm s winrm/config/winrs @{MaxShellsPerUser="2147483647"}
winrm s winrm/config/winrs @{IdleTimeout="7200000"}
Check MaxProcessesPerShell is any number except for 25 by using
    winrm g winrm/config/winrs
If the value is 25, change the value to 15 with the following command:
    winrm s winrm/config/winrs @{MaxProcessesPerShell="15"}

Those are the max values for MaxConcurrentOperationsPerUser and WinRS MaxShellsPerUser. You should also test with lower values (15 or 50 should be fine), as well as value == 1, and see how the system fails. I believe the default is 5 on both.

Add a custom footer
Add a custom sidebar
Clone this wiki locally