Summary report for 'RHQ Overnight Full Report'
by Michael Foley
Hi,
In the interest of transparency, information sharing, and community involvement ... I am sharing the recent test automation results for RHQ.
The tests are located here -->> https://github.com/RedHatQE/jon-tests
Anyone is welcome to :
* look at the tests
* contribute tests
* learn from the tests ( I would expect the CLI and REST would provide the most useful code snippets, as most people are familiar with the UI)
Regards,
Michael Foley
QE Lead, JBoss Operations Network
----- Original Message -----
From: noreply(a)redhat.com
To: jon-qa-list(a)redhat.com
Sent: Sunday, August 11, 2013 9:00:01 AM
Subject: [jon-qa-list] Summary report for 'RHQ Overnight Full Report'
Report Engine - Email Report Hello, This is auto generated email from Report Engine. It's based on RHQ Overnight Full Report
Test Suite Name Total Passed Failed Skipped Build Start Time End Time Duration RHQ CLI JS/JAVA Test 98 (0) 30 (+30) 28 (+28) 40 (-58) 4.9.0-SNAPSHOT (34e1c7b) Aug 11 15:35:43 IST 2013 Aug 11 17:18:15 IST 2013 01:42:31
Check Resource Configuration 52 (+4) 0 (0) 0 (0) 52 (+4) - Aug 11 15:28:01 IST 2013 Aug 11 15:35:18 IST 2013 00:07:15
RHQ REST Groovy Client Test 8 (0) 8 (0) 0 (0) 0 (0) 4.9.0-SNAPSHOT (34e1c7b) Aug 11 14:44:09 IST 2013 Aug 11 14:45:01 IST 2013 00:00:50
RHQ REST JAVA Client Test 40 (0) 39 (+19) 1 (-19) 0 (0) 4.9.0-SNAPSHOT (34e1c7b) Aug 11 14:43:33 IST 2013 Aug 11 14:49:41 IST 2013 00:06:07
RHQ REST Python 78 (0) 58 (+1) 4 (-1) 16 (0) 4.9.0-SNAPSHOT (34e1c7b) Aug 11 14:43:23 IST 2013 Aug 11 15:26:40 IST 2013 00:43:17
RHQ 4.x core UI Test 281 (+6) 59 (-127) 179 (+101) 43 (+32) 4.9.0-SNAPSHOT (34e1c7b) Aug 11 06:49:55 IST 2013 Aug 11 14:42:41 IST 2013 07:52:44
Import Resources 4 (0) 4 (0) 0 (0) 0 (0) 4.9.0-SNAPSHOT (34e1c7b) Aug 10 22:17:49 IST 2013 Aug 10 22:18:56 IST 2013 00:01:06
RHQ_4.4_UI_AS7Plugin_Test 210 (0) 134 (+14) 35 (+7) 41 (-21) 4.9.0-SNAPSHOT (9674555) EAP 6.1.0.GA Jul 28 15:46:17 IST 2013 Jul 28 21:07:11 IST 2013 05:20:52
RHQ CLI EAP6 44 (0) 39 (+5) 5 (-1) 0 (-4) 4.9.0-SNAPSHOT (9674555) EAP 6.1.0.GA Jul 28 13:58:39 IST 2013 Jul 28 15:45:24 IST 2013 01:46:33
Fresh Installation of RHQ 1 (0) 0 (0) 1 (0) 0 (0) - Dec 24 23:45:58 IST 2012 Dec 24 23:47:26 IST 2012 00:01:28 Summary: 816 371 253 192 17:42:47
Test Suite Detaild View:
Test Suite: RHQ CLI JS/JAVA Test
Group Name Total Passed Failed Skipped Import all Resources 2 1 1 0
Examples from jon documentation 22 8 12 2
bz reproduction test 3 1 0 2
Examples from rhq documentation 4 2 1 1
Samples from CLI client 3 0 3 0
operation scheduling test 3 0 3 0
manager test 6 5 1 0
permission test 15 0 0 15
role test 2 1 0 1
subject test 2 2 0 0
drift test 1 1 0 0
DynaGroup definitions test 9 1 0 8
Bundles 15 5 5 5
schedule_Management_For_RHQ_Agent 1 1 0 0
RHQ Storage Alert Definition 1 1 0 0
StorageNodesTest 3 1 2 0
stress test 5 0 0 5
Uninventory-Platforms-End 1 0 0 1 Total: 98 30 28 40 Test Suite: Check Resource Configuration
Group Name Total Passed Failed Skipped GuiLoginTest 1 0 0 1
Version Information 1 0 0 1
CheckResourceConfiguration 49 0 0 49
GuiLogoutTest 1 0 0 1 Total: 52 0 0 52 Test Suite: RHQ REST Groovy Client Test
Group Name Total Passed Failed Skipped Status 2 2 0 0
Login 3 3 0 0
Resource 3 3 0 0 Total: 8 8 0 0 Test Suite: RHQ REST JAVA Client Test
Group Name Total Passed Failed Skipped Login Test Negative 2 2 0 0
check New Rest Api 1 1 0 0
Login Test Positive 1 1 0 0
List Status 1 1 0 0
Visit Platforms 1 1 0 0
Visit Platforms By Id 1 1 0 0
get Resource By Platform Name 1 1 0 0
get Resource By Platform Name And Category 1 1 0 0
get Resource By Category 1 1 0 0
get Resource By Paging 1 1 0 0
get Platform Xml 1 1 0 0
Validate Children 1 1 0 0
get Alerts For Resources 1 1 0 0
get Schedules For Resources 1 1 0 0
get Availability For Resources 1 1 0 0
get Availability History For Resources 1 1 0 0
get Root URI 1 1 0 0
get Json PWrapper 1 1 0 0
verify AS Server Presence 1 1 0 0
Check Platform Operations 1 1 0 0
Validate Schedules 1 1 0 0
Validate Metric Data Default 1 1 0 0
Validate Metric Data 1 1 0 0
Visit Alerts 1 1 0 0
Redirect From Definition 1 1 0 0
Alert Definitions 1 1 0 0
Alert Count 1 1 0 0
AlertSender 1 1 0 0
AlertSender_DirectEmails 1 1 0 0
AlertSender_Mobicents 1 1 0 0
AlertSender_NotExisting 1 1 0 0
get Event Sources 1 1 0 0
get Event Definitions 1 1 0 0
get Group 1 1 0 0
get Group With Params 1 1 0 0
get Metrics Schedule 1 1 0 0
get Metrics Schedule By Id 1 0 1 0
get Favorite Resources 1 1 0 0
get Favorite Groups 1 1 0 0 Total: 40 39 1 0 Test Suite: RHQ REST Python
Group Name Total Passed Failed Skipped proboscis.case.MethodTest 78 58 4 16 Total: 78 58 4 16 Test Suite: RHQ 4.x core UI Test
Group Name Total Passed Failed Skipped GuiLoginTest 1 1 0 0
Version Information 1 1 0 0
Metric Collection Schedules validation 39 0 39 0
AlertDefinitionCreationTest 13 13 0 0
InventoryTest 11 2 5 4
BundleTest 3 0 2 1
TopLevelMenusTest 12 12 0 0
ReportsTest 7 7 0 0
DashboardTest 12 10 2 0
ResourcesTest 5 0 4 1
AdministrationTest 6 0 3 3
HelpTest 10 9 1 0
RecentOperationsTest 5 0 1 4
FavouriteTest 4 0 1 3
PluginsTest 52 0 52 0
Individualconfig 4 0 2 2
Configuration History 2 1 1 0
Group Config 3 0 1 2
SubNavigationMenuTests 2 0 2 0
Administration JSP page validation 6 1 5 0
Drift management-Create-[add/change/remove]-Delete 5 0 1 4
AlertHistoryValidationTest 13 0 13 0
AlertHistoryDeletionTest 13 0 13 0
AlertDefinitionDeletionTest 13 0 13 0
Scheduling Groups 4 0 1 3
Search groups... 6 0 3 3
Permissions Test 7 0 7 0
Alert Definition Template 6 0 1 5
CheckAlertDefTempCreated 1 0 1 0
Drift Definition Template 3 0 1 2
AlertDefinitionTest 5 0 1 4
StorageAutoInventoryTest 1 0 0 1
StorageNode 3 1 2 0
Setup LDAP 1 0 0 1
GuiLDAPUserLoginTest 1 1 0 0
GuiLogoutTest 1 0 1 0 Total: 281 59 179 43 Test Suite: Import Resources
Group Name Total Passed Failed Skipped GuiLoginTest 1 1 0 0
Version Information 1 1 0 0
GImportResourcesTest 1 1 0 0
GuiLogoutTest 1 1 0 0 Total: 4 4 0 0 Test Suite: RHQ_4.4_UI_AS7Plugin_Test
Group Name Total Passed Failed Skipped GuiLoginTest 1 1 0 0
Version Information 1 1 0 0
Standalone_AutodetectConfiguration 1 1 0 0
DetectServerVersion 1 1 0 0
Standalone_SocketBindingGroups 3 3 0 0
Standalone_Logging_Subsystem 16 9 3 4
Standalone_SecuritySubsystem 6 4 2 0
Standalone_Naming_Subsystem 1 1 0 0
Standalone_SignalServerReload 2 1 1 0
Standalone_Mail_Subsystem 13 3 4 6
Standalone_InfinispanSubsystem 9 3 3 3
Standalone_Web_Subsystem 7 6 0 1
Standalone_ResourceCreation 2 2 0 0
Standalone_Monitoring 3 1 1 1
Standalone_Deployment 20 18 2 0
Standalone_JMSDestinations 4 4 0 0
Standalone_Datasources 16 3 2 11
Standalone_SystemProperties 3 3 0 0
Standalone_ResourceConfiguration 5 5 0 0
Standalone_OSGI_Child_Configuration_Test 6 0 0 6
Standalone_Transactions_Test 1 1 0 0
Standalone_JAXR_Test 4 3 1 0
Standalone_Operations 4 4 0 0
Standalone_ManualImport 28 22 5 1
Domain_AutodetectConfiguration 1 1 0 0
Domain_ResourceConfiguration 3 3 0 0
Domain_SystemProperties 12 7 2 3
Domain_ResourceCreation 2 2 0 0
Domain_Monitoring 3 1 2 0
Domain_JMSDestinations 4 2 1 1
Domain_Deployment 6 2 1 3
Domain_Operations 4 4 0 0
Domain_ManagedServersManagement 7 7 0 0
Domain_ServerGroupsManagement 10 4 5 1
GuiLogoutTest 1 1 0 0 Total: 210 134 35 41 Test Suite: RHQ CLI EAP6
Group Name Total Passed Failed Skipped Standalone_Discovery_StartCommand_Parameters 15 15 0 0
Domain_Discovery_StartCommand_Parameters 4 4 0 0
Uninventory_EAP_Servers 1 1 0 0
Inventory_EAP_Servers 1 1 0 0
Detect_ServerVersion 1 1 0 0
Standalone_Deployment 5 4 1 0
Standalone_BundleDeployment 1 1 0 0
Standalone_NetworkInterfaces 1 0 1 0
Standalone_MailSubsystemTest 1 0 1 0
Standalone_BZ918677Test 1 1 0 0
DeployAndRestartSampleTest 1 1 0 0
Domain_Deployment 11 10 1 0
Domain_NetworkInterfaces 1 0 1 0 Total: 44 39 5 0 Test Suite: Fresh Installation of RHQ
Group Name Total Passed Failed Skipped GuiInstallationTest 1 0 1 0 Total: 1 0 1 0 Report Engine URL: https://mercury.lab.eng.pnq.redhat.com:8443/re
Report Generated on: Aug 11 18:30:00 IST 2013
_______________________________________________
jon-qa-list mailing list
jon-qa-list(a)redhat.com
https://post-office.corp.redhat.com/mailman/listinfo/jon-qa-list
10 years, 9 months
Re: Transforming Log Events into Information
by Michael Burman
Hi,
Some time ago (July) Heiko wrote a small mail with a link to a log
management blog. That got me wondering, what's the roadmap with this issue
and how should it be solved?
After a small chat in the IRC-channel, I decided I might write my thoughts
here also, in case we could get some discussion going on, as it probably is
an issue that's interesting to many people. Currently there's Events in the
RHQ, which could be parsed from the logs, but this isn't clearly enough.
The Fuse team has integrated Kibana to their Hawtio management tool, so
some teams at JBoss are playing with the idea.
There are some issues which come to my head right away about storing and
querying:
- Where to store the logs? Cassandra could be used as a place to store the
logs, but it's horrible in queries.
- If we store it in something like ElasticSearch, should the storage node
architect be extended to include ES as well? This is very close to what
DataStax Enterprise product does (with Solr, and it has static schema which
ES doesn't usually use).
The even trickier issue is, how should we support logs? Would shippings
logs with the agent be enough to some third party service? Should we create
Events from these as well? And how would we support structured logs in this
case? Like json formatted logs.
It's not probably wise use of resources to build something from the ground
to compete with likes of logstash/splunk/flume/many others, that can parse
different logformats effectively. The current Events format isn't enough
for many purposes, and many logs are not just plain text.
And that's just the parsing + shipping part. The other issue is viewing the
logs, searching the logs, creating metrics, creating statistics etc. Should
we integrate some third party UI, such as Kibana to our tool (Fuse guys
have ported some Ruby parts to Java servlets) ? I remember there was some
discussion on how these could be added, but I can't remember if it was
finished.
I'm only throwing around ideas, but to me this is a big part of
infrastructure.
- Micke
10 years, 9 months
Re: Agent / Server Communications Options
by Van Dillon
Hi Lukas,
Thanks for the quick reply.
I'm interested in doing work in this area and am willing to contribute.
I've signed the Contributor agreement and joined freenode (vdillon). I've
also forked the code and have begun looking at the areas you suggested.
Any suggestions on how I could hook my own handlers into this area on the
agent and server sides would be much appreciated. I'm sure I'll have more
questions as I become familiar with the communications layer architecture.
I look forward to working with you and the rest of the RHQ development team!
Thanks,
Van
10 years, 9 months
Agent / Server Communications Options
by Van Dillon
Hi everyone,
At the end of last month I posted a question to this list. Perhaps the
post was missed because I didn't receive an answer. If, on the other hand,
I am posting to the wrong list, please accept my apologies and I will post
the question on the rhq-users list instead.
Here is the body of the post:
>>
I'm new to RHQ and am interested in using it in several different ways.
Some of the ways I want to use it require the agent to be on platforms
that do not have a public IP address. I read the Design Documentation wiki
entries: "Design-Agent-to-Server Unidirectional Communications" and
"Design-Agent-Server Communications 3", both of
which indicate that you guys have put some serious thought into adding this
ability to RHQ.
Is this feature being added to the roadmap anytime soon? If not, is there
a way to hook our own handlers into the agent and server communications
layers?
<<
I'm interested in getting involved in the development of this feature if
it's still being considered.
Thanks,
Van Dillon
10 years, 9 months
[as7] Server discovery and resource version
by Thomas Segismont
Hi,
I've just pushed a fix for Bug 913764 - [as7] Version identifier of EAP
resource changes depending on run state of EAP.
The version of the managed resource was previously determined:
* looking at the server base directory name for AS7
* making a call to the HTTP management interface for EAP6 and other
layered projects/products
Now discovery of the server version is only based on file inspection and
obeys to the following logic:
* look for a version.txt file
* or
modules/system/layers/base/org/jboss/as/product/slot/dir/META-INF/MANIFEST.MF
file
* or modules/org/jboss/as/product/slot/dir/META-INF/MANIFEST.MF
* or fallback to the server base directory name
The changes also fix BZ948053 and BZ969120 which describe other symptoms
of the same problem.
Cheers,
Thomas
10 years, 9 months
Rename manageRootDir property in bundles
by Lukas Krejci
Hi all,
In BZ 801464 (and 801926) (https://bugzilla.redhat.com/show_bug.cgi?id=801464), we're discussing the problems of manageRootDir property on the deployment units in bundles.
We have decided to take 2 actions on it:
1) A short term remedy to prevent people from shooting themselves in the foot
2) A long term overhaul of how bundles work to make them more similar to RPM/APT so that people are less surprised by the behavior.
I won't discuss 2) here because there will be plenty of opportunities to do that later when we start concentrating on it, but I'd like to discuss 1) with you.
As the subject suggests, one of the things we intend to do is to rename the manageRootDir property to something that more clearly expresses the true meaning of the setting. The other thing that we want to do is to make the parameter mandatory so that people are forced to think about the value to put in there when creating a new bundle (this will only affect the upload of new bundles. The system will be able to revert to bundle versions that are already uploaded).
So the one thing I'm gathering input for is the new name for manageRootDir.
But what manageRootDir (which defaults to true) really means? If it is true (the default), the bundle deployer will delete any and all files (recursively) in the destination directory before deploying the bundle files into it. This means that it is guaranteed that the bundle destination only contains the bundle files. When manageRootDir is false, it means that that the files and directories at directly under the destination directory are left intact - this means that the bundle deployer will only overwrite the files that are also part of the bundle and, also, will replace any directories that are present in the bundle with the contents from the bundle - this means that the sub-directories are always wiped to conform to the contents of the bundle - there is currently no way of overriding that (and we don't search for a mechanism to provide that in this email).
There already have been some suggestions for the new name:
manageRootDir=true
could also be expressed like:
manageDestDirFully=true
doNotTouchTopLevelDirectoriesFoundInDestDirButNotFoundInBundle=false
ignoreTopLevelDirectoriesInDestDirButNotFoundInBundle=false
cleanTopLevelDirectoriesFoundInDestDirAndNotFoundInBundle=true
bundleToManageAllTopLevelDirectoriesInDestDir=true
manageAllTopLevelDirectoriesInDestDir=true
I'll add a couple of suggestions, too:
cleanDestinationFully=true
wipeDestinationDir=true
alsoWipeUnmanagedFilesAndDirectoriesInDestination=true
Which of the above do you think expresses the best what manageRootDir does? Do you have some other suggestions for the name?
Cheers,
Lukas
10 years, 9 months