Bug 674827 - Add a DynaGroup template to cluster together EAP5/AS 6 clusters
Summary: Add a DynaGroup template to cluster together EAP5/AS 6 clusters
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: John Mazzitelli
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 13:28 UTC by Heiko W. Rupp
Modified: 2013-09-02 07:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-02 07:28:04 UTC
Embargoed:

Attachments (Terms of Use)

Description Heiko W. Rupp 2011-02-03 13:28:18 UTC 
The template in the UI says "Group by AS cluster" - but this only applies to AS3/4 clusters.
Just exchanging the plugin name in the created dynagroups expression is not enough, as the name of the trait is also different in AS 5 / 6

So the DynaGroups UI needs another template entry for AS5/6

groupby resource.trait[MCBean|ServerConfig|*|partitionName]
resource.type.plugin = JBossAS5
resource.type.name = JBossAS Server
Comment 1 John Mazzitelli 2011-02-16 15:32:08 UTC 
commit 461c9be10b701ca381f4fcbf4765689f074f90f7

"JBossAS 5/6 Clusters" is a new option in the templates drop down
Comment 2 Sunil Kondkar 2011-06-10 08:57:06 UTC 
Verified on build 123 (Version: 4.1.0-SNAPSHOT Build Number: a6d2d56)

While creating a DynaGroup definition, verified that the dropdown 'Saved Expression' has a option 'JBoss As 5/6 Clusters'.

Selecting the option displays below expression:

groupby resource.trait[MCBean|ServerConfig|*|partitionName]
resource.type.plugin = JBossAS5
resource.type.name = JBossAS Server

Verified by creating a dynagroup using above option.
Marking as verified.
Comment 3 Heiko W. Rupp 2013-09-02 07:28:04 UTC 
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.
Note You need to log in before you can comment on or make changes to this bug.