Bug 871974 - Add availability type REMOVED to AvailabilityType class
Summary: Add availability type REMOVED to AvailabilityType class
Keywords:
Status: CLOSED DUPLICATE of bug 1093822
Alias: None
Product: RHQ Project
Classification: Other
Component: Inventory
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-31 21:33 UTC by Elias Ross
Modified: 2014-05-02 21:05 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-02 21:05:53 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1093822 0 high CLOSED RFE (offshot of JON3-42) : Allow automatic uninventory of dead / missing / removed resources 2021-02-22 00:41:40 UTC

Internal Links: 1093822

Description Elias Ross 2012-10-31 21:33:19 UTC
Reason is explained here: https://community.jboss.org/thread/212115

Here's the JavaDoc showing the use cases for this enum type.

public enum AvailabilityType {

    /**
     * Resource was externally removed.
     * Example situations:
     * <ul>
     * <li>For a server resource, the agent observes the server is no longer installed.</li>
     * <li>For a .war deployment, the .war is no longer running on the server</li>
     * <li>For a file, the agent observes the file is no longer on the file system.</li>
     * <li>For a database table, the agent sees the table was removed.</li>
     * </ul>
     * The difference between REMOVED and DOWN is that REMOVED resources were
     * likely intentionally removed and advises administrators that this
     * resource should no longer be inventoried.
     * <p/>
     * This availability should only be used if the agent is certain the
     * resource was removed. These are examples where DOWN would be the correct
     * type:
     * <ul>
     * <li>For a database table, the agent has no permissions to access the
     * parent schema. It is possible the table still exists.</li>
     * <li>For a file, the agent cannot access the parent's directory.</li>
     * <li>For a .war file, the server was shut down as part of upgrade.</li>
     * </ul>
     * As a rule of thumb, if the parent of a resource is available,
     * and if at least one 'siblings' of a resource are available,
     * but this particular resource is absent, then it is suggested to
     * return this availability type.
     */
    REMOVED
    ;

Comment 1 Jay Shaughnessy 2014-05-02 18:45:19 UTC
Hi Elias, 

This has been something we've thought about for a while. Bug 1093822 is being worked on and has some overlap with this RFE.  Please check it out and comment. Thanks!

Comment 2 Elias Ross 2014-05-02 20:56:49 UTC
This is exactly what I was after.

You can mark this as a duplicate.

Comment 3 Elias Ross 2014-05-02 20:57:04 UTC
This is exactly what I was after.

You can mark this as a duplicate.

Comment 4 Jay Shaughnessy 2014-05-02 21:05:53 UTC
Excellent, thanks.

*** This bug has been marked as a duplicate of bug 1093822 ***


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