Bug 811287 - RFE (availability): Allow component code to disable or enable resource
RFE (availability): Allow component code to disable or enable resource
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: Agent, Plugins (Show other bugs)
4.3
All All
unspecified Severity medium (vote)
: ---
: RHQ 4.4.0
Assigned To: Jay Shaughnessy
Mike Foley
:
Depends On:
Blocks: 741450
  Show dependency treegraph
 
Reported: 2012-04-10 11:55 EDT by Jay Shaughnessy
Modified: 2013-09-01 06:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-01 06:15:31 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jay Shaughnessy 2012-04-10 11:55:28 EDT
We already have (starting in 4.4) the ability for a user to
DISABLE/ENABLE resources via the GUI or CLI.  In some circumstances
it makes sense for plugin code to be able to do the same.  AS7 has
the notion of managed servers that may or may not be auto-started. A
managed server that is not started is not UP or DOWN, but more
logically DISABLED.  This can be determined via the component code.

This feature will make it possible for the component code to
set resource enablement programmatically.
Comment 1 Jay Shaughnessy 2012-04-10 14:54:50 EDT
commit 48694295b96f8e28a84d7f1d36be3b9d8ae456e9

Added this new feature. Called like:
     resourceContext.getAvailabilityContext().disable();



Test Notes
----------
This will likely be used in the AS7 plugin. Perhaps a test
using that plugin can be designed.
Comment 2 Heiko W. Rupp 2013-09-01 06:15:31 EDT
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.

Note You need to log in before you can comment on or make changes to this bug.