Hi Richard,
The problem you're having is that AutoCluster backing groups, like
AutoGroup backing groups, are basically hidden groups that back the
AutoCluster and AutoGroup features offered in the GUI. They are
specifically intended to support navigating the Resource Group and
Resource trees. It's true that they are in fact real groups but they
are not intended for remote consumption as they are really part of the
implementation.
In case the distinction isn't clear, an AutoGroup is a dynamically
populated group of resources with the same type and the same parent, and
accessible by a specific user. They are generated when navigating a
resource tree.
An AutoCluster is a dynamically populated group of resources that are
logically the same resource. For example, a group WAR files under a
recursive compatible group of AS servers. There generated when
navigating a recursive compatible group tree.
There is currently no way to generate these groups outside of the GUI.
Although, if you are hellbent on querying for them it is possible using
ResourceGroupCriteria. The trick is, for autoClusters:
criteria.addFilterVisible(false);
The caller must have access to the root group.
And for AutoGroups:
criteria.addFilterVisible(false);
criteria.addFilterPrivate(true);
The caller must be the owner of the AutoGroup.
Jay
On 6/1/2012 3:31 PM, Richard Hensman wrote:
Hi
I am developing a web app that reads metrics from RHQ via the Remote
Client API and am having trouble accessing clustered resources (Auto
Clusters) such as file systems. I am ok if I know the id of the Auto
Cluster as I can
use ResourceGroupManagerRemote.getResourceGroupComposite, but cannot
see any way of querying for Auto Clusters via tags (for example). Is
there no way of querying for Auto Clusters using criteria?
Can anyone please advise?
thanks
Richard
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel