mrayzenoss has changed the topic to: Today's QA Test Day: Zenoss 2.5.2: http://bit.ly/7wT0Fw (8:13:51 AM)
8:44:19 AM bbibeault: Good morning, everyone.  Today is the QA Test Day, covering the 2.5.2 beta!
8:44:47 AM mrayzenoss: woohoo!
8:57:27 AM mrayzenoss: I'm going to upgrade my 2.5.1 source install following the Installation Guide
8:57:53 AM bbibeault: A brand new community appliance was just posted - zenoss-2.5.2-533-x86-devel-beta.vmware.tar.gz
8:58:00 AM mrayzenoss: I'll get that too
8:58:08 AM bbibeault: Get it while it's hot - http:://alpha.zenoss.com/2.5.2-beta/zenoss-2.5.2-533-x86-devel-beta.vmware.tar.gz
8:59:31 AM bbibeault: Get it while it's hot (now with 100% less erroneous colons!) - http://alpha.http://zenoss.com/2.5.2-beta/zenoss-2.5.2-533-x86-devel-beta.vmware.tar.gz
9:00:05 AM mrayzenoss: heh
9:09:48 AM bbibeault: I am upgrading a Cent5-64 machine to the latest 2.5.2 beta build, to see how it works with events migration.
9:15:04 AM cumanzor: I'm going to install and test the community appliance
9:19:47 AM wquesada: I'm about to update a community appliance from 2.4.5 to 2.5.2
9:43:33 AM bbibeault: Starting the enterprise zenpacks update now, then will continue looking at Event Console issues.
9:54:58 AM bbibeault: Upgrade is almost complete; my machine seems to be running slowly today.
10:30:18 AM mrayzenoss: upgrading my 2.5.1 source install to 2.5.X
10:31:23 AM wquesada: Ah.. that is a nice scenario to try mrayzenoss.. let's us know how it goes..
10:32:07 AM cumanzor: community appliance is working ok so far. doing a very small network discovery
11:36:55 AM mrayzenoss: http://dev.zenoss.org/trac/ticket/6078 and http://dev.zenoss.org/trac/ticket/6077
11:50:28 AM bbibeault: My installs seem to have completed without issue, has anyone else seen anything good or bad with the process?
11:51:18 AM mrayzenoss: my source upgrade is taking forever on a slow machine
11:51:30 AM mrayzenoss: of course… it's a slow machine
11:52:06 AM mrayzenoss: I'm going to fire up the new VM soon
11:52:17 AM mrayzenoss: do some testing with some Zenpacks
12:20:28 PM bbibeault: I am scripting an event generation load against my 2.5.2, to test the event console.
12:23:26 PM mrayzenoss: I know Ian has one, I saw him add 1000 events yesterday in the UI meeting
12:23:54 PM bbibeault: I wonder if he is using the script that I created for that.
12:24:11 PM Muti: how about 1,000,000+ ?
12:24:41 PM Muti: mysql> select count(*) from history;
12:24:41 PM Muti: +----------+
12:24:41 PM Muti: | count(*) |
12:24:41 PM Muti: +----------+
12:24:41 PM Muti: |  3852379 |
12:25:27 PM bbibeault: Performance of this script isn't that hight; I can't get the counts to that level in a timely fashion yet.
12:25:36 PM Muti: hmm, ok
12:25:52 PM bbibeault: If you export those events as CSV, any clue how large the resulting file would be?
12:26:04 PM bbibeault: I could try and do an import, if that is safe/allowed.
12:26:17 PM Muti: big, but I don't think I'd get permission to release this
12:26:23 PM Muti: in binary it's around 3 GB
12:26:26 PM bbibeault: Understandable, that's what I have found before.
12:26:55 PM Muti: we just had quite a few annoying SQL performance issues w/ 2.5.1
12:27:11 PM bbibeault: I am very curious to see how you fare with 2.5.2.
12:27:37 PM bbibeault: Is there any way that you can try and test a backup of your 2.5.1 data on a 2.5.2 VM?
12:27:47 PM Muti: that's a possibility
12:28:12 PM Muti: I have a dev server, but I'm in the middle of writing a ZenPack and can't upgrade it to 2.5.2 beta
12:29:01 PM bbibeault: While 2.5.2 is still in development/beta, any issues that are found still have a chance of getting resolved.  We are testing in QA with much larger event loads, but still nothing on the order of millions (I think we are topping out around the 120,000 event mark).
12:29:49 PM Muti: ok, I might be able to find the time to setup a VM on my workstation here and do some testing, but things are always busy here.
12:30:41 PM bbibeault: As they are everywhere, I am sure - I really appreciate the consideration; if this is something you can try, please let me know the results.  Even an issues found in the first hour can be quite helpful.
12:31:16 PM Muti: I did just send a note to cluther regarding the patch in ticket #5881
12:31:56 PM Muti: which I'd like to apply to our 2.5.1 install
12:32:19 PM bbibeault: What was the note, if you don't mind my asking?  I don't see a reference in the ticket.
12:32:43 PM Muti: I sent a note in the CRM, case #10469
12:33:12 PM Muti: so it's only available to internal Zenoss support
12:34:10 PM bbibeault: Thanks
2:53:07 PM mrayzenoss: anyone verify the Device List is working?  It's broken on my source upgrade
3:05:36 PM cumanzor: I will install a fresh ent appliance in order to check #6071 completely
3:08:26 PM cumanzor: i did an appliance upgrade from 2.5.1 enterprise to 2.5.2, everything seems to be ok, event view, alerting rules, new zenpacks (HP_UX), etc
3:11:08 PM bbibeault: Carlos, if you view the Device List page, is everything displayed correctly?
3:29:20 PM cumanzor: I see that long class name like "/VMware/VM Infrastructure/ResourcePools" are not rendered correctly on Device list, somehow part of the string is hidden behind another cell
4:16:55 PM mrayzenoss: thoroughly convinced that upgrading my home install to 2.5.2 was a bad idea
4:17:03 PM mrayzenoss: http://dev.zenoss.org/trac/ticket/6084
4:20:38 PM mrayzenoss: I'll be breaking more source installs later
4:20:47 PM mrayzenoss: gotta bring my Debian and Fedora boxes back online
4:21:23 PM bbibeault: Not the best situation; I marked that ticket as 2.5.2 and proposed, Matt.
4:21:42 PM mrayzenoss: meh, they're for breaking
4:21:49 PM mrayzenoss: my home isn't exactly production
4:53:31 PM cumanzor: http://dev.zenoss.com/trac/ticket/6071 is not present on enterprise/community appliance 2.5.2
4:57:12 PM mrayzenoss: yeah, that's fixed
5:05:48 PM mrayzenoss: on upgraded boxes, is anyone not getting their graphs updated anymore?
5:06:23 PM mrayzenoss: or should I just write this one off to my source upgrade?
5:07:21 PM mrayzenoss: ugh, my search results are broken as well