On 2012-09-11T15:04:55, Alan Robertson al...@unix.sh wrote:
Depends. Pacemaker may still care about the status of these agents.
If it can't start or stop them, what can it do with them?
The status from these agents may feed into operations on other
resources that are fully managed.
On 09/12/2012 05:14 AM, Lars Marowsky-Bree wrote:
On 2012-09-11T15:04:55, Alan Robertson al...@unix.sh wrote:
Depends. Pacemaker may still care about the status of these agents.
If it can't start or stop them, what can it do with them?
The status from these agents may feed into operations on
On 2012-09-12T09:01:05, Alan Robertson al...@unix.sh wrote:
The status from these agents may feed into operations on other
resources that are fully managed.
Understood.
I believe it will care about those other agents - not these. It
shouldn't know about these, AFAIK.
I guess then
On 09/08/2012 02:53 PM, Lars Marowsky-Bree wrote:
On 2012-09-07T13:46:27, Alan Robertson al...@unix.sh wrote:
Well, I presume that one would not tell pacemaker about such agents, as
they would not be useful to pacemaker. From the point of view of the
crm command, you wouldn't consider them
On 2012-09-07T13:46:27, Alan Robertson al...@unix.sh wrote:
Well, I presume that one would not tell pacemaker about such agents, as
they would not be useful to pacemaker. From the point of view of the
crm command, you wouldn't consider them as valid resource agents to
put in a
On 2012-09-05T15:25:44, Dejan Muhamedagic de...@suse.de wrote:
BTW, FWIW -
monocf may be just like ocf, sans start and stop operations.
That would make all ocf RA elligible for this use.
Thinking about this, not entirely. We'd have to fake the start/stop at
least. (In particular the start.)
On 09/05/2012 03:32 AM, Dejan Muhamedagic wrote:
This would be for my new monitoring project, of course
;-). But it could then be called by all the HTTP resource agents - or
used directly - for example by the Assimilation project.
This would be a slight but useful bending of OCF resource
Hi,
On Tue, Sep 04, 2012 at 07:20:23PM -0600, Alan Robertson wrote:
Hi Dejan,
If the resource agent is not running correctly it needs to be
restarted. My memory says that OCF_ERR_GENERIC will not cause that
behavior. I believe the spec says you should exit with not running if
it is
On 2012-09-04T19:20:23, Alan Robertson al...@unix.sh wrote:
I will likely write a monitor-only resource agent for web servers. What
would you think about calling it from the other web resource agents?
Sharing code - in this case, the monitor-via-network of the http agents
- seems to make
Hi Lars,
On Wed, Sep 05, 2012 at 11:41:17AM +0200, Lars Marowsky-Bree wrote:
On 2012-09-04T19:20:23, Alan Robertson al...@unix.sh wrote:
I will likely write a monitor-only resource agent for web servers. What
would you think about calling it from the other web resource agents?
Sharing
On 2012-09-05T15:25:44, Dejan Muhamedagic de...@suse.de wrote:
How about a new element. Something like
primitive vm1 ocf:heartbeat:VirtualDomain
require vm1 web-test dns-test
How we map this into Pacemaker's dependency scheme is obviously open to
discussion.
The require would imply that
On 06/09/2012, at 12:30 AM, Lars Marowsky-Bree l...@suse.com wrote:
On 2012-09-05T15:25:44, Dejan Muhamedagic de...@suse.de wrote:
How about a new element. Something like
primitive vm1 ocf:heartbeat:VirtualDomain
require vm1 web-test dns-test
How we map this into Pacemaker's
Hi Dejan,
If the resource agent is not running correctly it needs to be
restarted. My memory says that OCF_ERR_GENERIC will not cause that
behavior. I believe the spec says you should exit with not running if
it is not functioning correctly. (but I didn't check it, and my memory
isn't that
13 matches
Mail list logo
