[ClusterLabs] Q: status section of CIB: "last_0" IDs and "queue-time"

[Ulrich Windl]

Hello!

I have a question:
Inspecting the XML of our cluster, I noticed that there are several IDs ending with "last_0". So I wondered:
It seems those IDs are generated for start and stop operations, and I discovered one case where an ID is duplicate (the status is for different nodes, and one is a start operation, while the other is a stop operationhowever).

Background: I wrote some program that extarcts the runtimes of operations from the CIB, like this:
prm_r00_fs_last_0 13464 stop
prm_r00_fs_last_0 61 start
prm_r00_fs_monitor_300000 34 monitor
prm_r00_fs_monitor_300000 43 monitor

The first word is the "id" attribute, the second is the "exec-time" attribute, and the last one (added to help myself out of confusion) is the "operation" attribute. Values are converted to milliseconds.

Is the name of the id intentional, or is it some mistake?

And another question: For an operation with "start-delay" it seems the start delay is simple added to the queue time (as if the operation was waiting that long). Is that intentional?

Another program tried to extract queue and execution times for operations, and the sorted result looks like this then:

1 27 prm_nfs_home_exp_last_0 monitor
1 39 prm_q10_ip_2_monitor_60000 monitor
1 42 prm_e10_ip_2_monitor_60000 monitor
1 58 prm_s01_ip_last_0 stop
1 74 prm_nfs_cbw_trans_exp_last_0 start
30001 1180 prm_stonith_sbd_monitor_180000 monitor
30001 178 prm_c11_ascs_ers_monitor_60000 monitor
30002 165 prm_c11_ascs_ers_monitor_45000 monitor

Regards,
Ulrich