Hello,
I am running heartbeat 2.0.0 on SuSE10 (rpm -q heartbeat =
heartbeat-2.0.0.20050906-2).
I am launching heartbeat from my application in order to perform IP
failover between 2 nodes and the application communicates with the
heartbeat process through HEARTBEAT API in order to obtain
On 2006-06-15T10:37:37, Huang Zhen [EMAIL PROTECTED] wrote:
No, it is unclear because a resource _container_ is treated as if it was
merely an option on a primitive. Which it is not.
I added the label like belong to to show the contain relationship.
Or you may have better suggestion?
Yes,
Many LSB init scripts implement a 'reload' action which permits them to
reread their configurations without interrupting service.
By design, OCF spec is upwards-compatible with the LSB.
I think it would be good to specifically add the reload operation to the
OCF spec.
Saying something like
On 2006-06-15T08:56:00, Alan Robertson [EMAIL PROTECTED] wrote:
Many LSB init scripts implement a 'reload' action which permits them to
reread their configurations without interrupting service.
By design, OCF spec is upwards-compatible with the LSB.
I think it would be good to
On 2006-06-15T09:58:37, Alan Robertson [EMAIL PROTECTED] wrote:
1. The administrator of course may not change the parameters so much
that the RA can no longer identify the already running resource
instance. (Do we need to provide hints in the meta data to identify
which parameters are safe to
Lars Marowsky-Bree wrote:
On 2006-06-15T10:37:37, Huang Zhen [EMAIL PROTECTED] wrote:
No, it is unclear because a resource _container_ is treated as if it was
merely an option on a primitive. Which it is not.
I added the label like belong to to show the contain relationship.
Or you may have
