20) Understanding about OCF RA specification
Please refer to the file resource-agent-api.txt
* (Around line 149)
But can give more definite rules for a implementation?
* (Around line 306)
RA executor. But what values should be assigned to some variables? For example, for OCF_RESOURCE_INSTANCE, OCF_RESOURCE_TYPE OCF_RESOURCE_TYPE should be the name of the resource being invoked -- for example Filesystem, or datadisk, or LinuxSCSI, or ServeRAID -- it's normally the same as the script name. As far as OCF_RESOURCE_INSTANCE, I
think you need to ask LMB about this one... -- AlanRobertson If OCF_RESOURCE_TYPE is always the name of the resource being invoked, maybe don't need to be set it by the RA
executor. Right? -- SunJiangDong
Partially for my own clarification, examples of OCF_RESOURCE_TYPE are IPaddr and apache (as opposed to 10.0.0.1 and myWebServer). -- AndrewBeekhof
OCF_RESOURCE_INSTANCE is the configured name for the resource (eg. 10.0.0.1 and myWebServer from above). -- AndrewBeekhof
* (Around line 168)
leave the resource instance in the requested state.
What's the meaning? It means that stopping twice in a row is the same as stopping once. Starting twice in a row is the same
as starting once. Note that this is a property of the individual ResourceAgent, not of the LocalResourceManager. This means you don't have to do anything to make this happen - it's supposed to be a property of the ResourceAgent. If you wanted (for some reason) to rely on this being true, then you would be permitted to rely on this property. But, I suspect you don't care one way or the other about this property. -- AlanRobertson
I'm making OCF compliant RA based on the former heartbeat resource agent scripts, so have to care it -- SunJiangDong