Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-23 Thread Lars Marowsky-Bree
On 2006-01-21T18:47:48, Andrew Beekhof [EMAIL PROTECTED] wrote: Not really. If you cast your mind back, the original purpose for managed/ unmanaged was so that we could depend on things that were outside the CRM's control. So that resources could sit on top of an unmanaged resource

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-23 Thread Andrew Beekhof
On Jan 23, 2006, at 2:38 PM, Lars Marowsky-Bree wrote: On 2006-01-21T18:47:48, Andrew Beekhof [EMAIL PROTECTED] wrote: Not really. If you cast your mind back, the original purpose for managed/ unmanaged was so that we could depend on things that were outside the CRM's control. So that

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-22 Thread Huang Zhen
Lars Marowsky-Bree wrote: - #878: pengine core dump in StopOnebyOne (with fencing enable) Comment #8 seems to indicate that this might well be fixed as a side effect of other issues, and no further report has been seen since November. I think so, close it. - #1012: GUI crash No

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-21 Thread Andrew Beekhof
On 1/21/06, Peter Kruse [EMAIL PROTECTED] wrote: Good morning, Lars Marowsky-Bree wrote: On 2006-01-20T12:37:10, Peter Kruse [EMAIL PROTECTED] wrote: OK, this we'll eventually provide again. (ipfail) except that ipfail relies on an external address, but I don't understand why the

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-21 Thread Lars Marowsky-Bree
On 2006-01-21T11:38:18, Andrew Beekhof [EMAIL PROTECTED] wrote: One thing to keep in mind is that if we stop monitoring a resource when its not managed then the resources that sit on top of it may be adversely affected since they now don't know that its prerequisite is starting/stopping.

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-21 Thread Andrew Beekhof
On Jan 21, 2006, at 5:56 PM, Lars Marowsky-Bree wrote: On 2006-01-21T11:38:18, Andrew Beekhof [EMAIL PROTECTED] wrote: One thing to keep in mind is that if we stop monitoring a resource when its not managed then the resources that sit on top of it may be adversely affected since they now

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-20 Thread Lars Marowsky-Bree
On 2006-01-20T10:03:53, Andrew Beekhof [EMAIL PROTECTED] wrote: Woah, what are you calling crm_attribute for all the time? Its either an ipfail replacement or his way of getting resources to run on the node where they've failed the least... I forget which. We definetely need to include both

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-20 Thread Peter Kruse
Hello, Lars Marowsky-Bree wrote: On 2006-01-20T10:03:53, Andrew Beekhof [EMAIL PROTECTED] wrote: Woah, what are you calling crm_attribute for all the time? Its either an ipfail replacement or his way of getting resources to run on the node where they've failed the least... I

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-20 Thread Lars Marowsky-Bree
On 2006-01-20T12:37:10, Peter Kruse [EMAIL PROTECTED] wrote: 1. There is an ifmonitord that monitors all network interfaces in the cluster and writes the current status to the cib so it is available to all nodes. When a network interface fails (link goes down) before I return and error and

Re: [Linux-ha-dev] Tracking 2.0.3 release

2006-01-19 Thread Lars Marowsky-Bree
On 2006-01-19T20:17:58, Peter Kruse [EMAIL PROTECTED] wrote: The problem I observe only manifested after the resources have been online for about 24h with one or two resource groups with some resources defined in it. So I'm not sure that the tests you run really are real live so to say. The