Bug 729298 - RFE: Resource states defined per-plugin, as finite state machine
RFE: Resource states defined per-plugin, as finite state machine
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
3.0.1
Unspecified Unspecified
medium Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature, Improvement
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-08-09 08:34 EDT by Ondřej Žižka
Modified: 2011-10-06 15:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
JON-EAP-UP-after-shutdown.png (115.83 KB, image/png)
2011-08-09 13:13 EDT, Ondřej Žižka
no flags Details

  None (edit)
Description Ondřej Žižka 2011-08-09 08:34:35 EDT
How about defining resource states per plugin.
Standard states would be
  UNKNOWN, STARTING, UP, STOPPING, DOWN, STOPPING_FOR_RESTART.

These states would be
  1) Updated as per agent's observations,
  2) Expected as per operation definitions.

Edges between these states could have characteristics which could be used for triggering further actions. For example:

  UP -> DOWN => Unexpected down
  STOPPING -> DOWN => Expected down
  STOPPING_FOR_RESTART -> DOWN => Restart failed
Etc.

In UI, the last edge (or last two states) would be used to determine what to display.

This might be an overkill, but I wanted to share the idea ;-)
Comment 1 Ondřej Žižka 2011-08-09 08:36:17 EDT
Technically, it's two RFEs:
1) Resource states defined per plugin.
2) States treated as FSM states.
Comment 2 Ondřej Žižka 2011-08-09 13:13:16 EDT
Created attachment 517448 [details]
JON-EAP-UP-after-shutdown.png

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