Bug 729298

Summary: RFE: Resource states defined per-plugin, as finite state machine
Product: [Other] RHQ Project Reporter: Ondřej Žižka <ozizka>
Component: Core ServerAssignee: Nobody <nobody>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: 3.0.1CC: hrupp
Target Milestone: ---Keywords: FutureFeature, Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
JON-EAP-UP-after-shutdown.png none

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