Bug 729298 - RFE: Resource states defined per-plugin, as finite state machine
Summary: RFE: Resource states defined per-plugin, as finite state machine
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server
Version: 3.0.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-09 12:34 UTC by Ondřej Žižka
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 741450 0 medium CLOSED RFE: Improve Availability Handling (Tracker) 2021-02-22 00:41:40 UTC

Description Ondřej Žižka 2011-08-09 12:34:35 UTC 
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 12:36:17 UTC 
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 17:13:16 UTC 
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.