Bug 881408

Summary:	Document minimal requirements for a resource to be manageable
Product:	[JBoss] JBoss Operations Network	Reporter:	Charles Crouch <ccrouch>
Component:	Plugin -- JBoss EAP 6	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED EOL	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.2	CC:	hbrock
Target Milestone:	---
Target Release:	JON 4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1048369 1048370 1048371 1048372 1048373 1048374 1048375 1048376 1048377 1048378 1048379 1048381 (view as bug list)		Environment:
Last Closed:	2019-06-24 14:53:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1048369, 1048370, 1048371, 1048372, 1048373, 1048374, 1048375, 1048376, 1048377, 1048378, 1048379, 1048381

Description Charles Crouch 2012-11-28 20:53:35 UTC

This issue is to make sure we have documentation available which describes the basic minimal requirements that a given managed resource needs to provide in order to be manageable by JON. Examples include:
AS4: Remote JMX connection
AS5: Profileservice deployed
etc etc

Comment 1 Charles Crouch 2012-11-28 20:54:56 UTC

This should probably be done on a plugin by plugin basis since each product is going to have its own set of requirements e.g. SOA, EPP, which we may have no idea about.

Comment 2 Deon Ballard 2014-01-03 15:16:04 UTC

I think this is actually a plug-in doc issue, not a content service documentation issue. Anything set in the rhq-plugin.xml descriptor will get pulled in when the resource reference is generated. But it requires more technical knowledge of the resource to create that content (i.e., plug-in developer work). 

I am assigning this to the Plugin component for EAP and I will clone it for the other JBoss plugins.

Comment 3 Jay Shaughnessy 2014-08-26 15:18:27 UTC

Useful plugin documentation but won't make 3.3.  Pushing to 4.0 although I could see this getting pulled back to a potential 3.4 release (no target exists for 3.4 at the moment)

Comment 5 Filip Brychta 2019-06-24 14:53:37 UTC

JBoss ON is coming to the end of its product life cycle. For more information regarding this transition, see https://access.redhat.com/articles/3827121.
This bug report/request is being closed. If you feel this issue should not be closed or requires further review, please create a new bug report against the latest supported JBoss ON 3.3 version.