On Sun, Jun 28, 2009 at 2:54 AM, Darren Thompsondarr...@akurit.com.au wrote:
Perhaps Andrew Beekhof would followup with item 1 through the
Pacemaker wiki (as I understand he is a core developer with that
project).
I'll see what I can do
___
Openais
Openais Team
I am a user of Heartbeat cluster on SLES10 and have my first
(pre-production) SLES11 HAE cluster.
I'm impressed with how smoothly the transition for Heartbeat to
pacemaker/openais was with this new implementation.
The documentation for SLES 11 / HAE was actually better than that
On Sun, 2009-06-28 at 07:52 +0930, Darren Thompson wrote:
Openais Team
I am a user of Heartbeat cluster on SLES10 and have my first
(pre-production) SLES11 HAE cluster.
I'm impressed with how smoothly the transition for Heartbeat to
pacemaker/openais was with this new implementation.
Good call...
can I ask that my list of requested faetures be added to the design of
the wiki
Thanks
On Sat, 2009-06-27 at 15:28 -0700, Steven Dake wrote:
On Sun, 2009-06-28 at 07:52 +0930, Darren Thompson wrote:
Openais Team
I am a user of Heartbeat cluster on SLES10 and have my first
Steve
Thank you for taking the time to reply.
In hindsight I realised my original post specified vendor product a
and you email address indicates you work for a different vendor.
No disrespect was intended, my comments were intended for the open
source project, not a particular vendors
Steven Dake wrote:
I invite all of our contributors to help define the X.Y roadmap of both
corosync and openais. Please submit your ideas on this list. Some
examples of suggested ideas have been things like converting to libtool.
Also new service engine ideas are highly welcome. Keep ideas
On Wed, 2009-06-24 at 16:56 +0200, Jan Friesse wrote:
Steven Dake wrote:
I invite all of our contributors to help define the X.Y roadmap of both
corosync and openais. Please submit your ideas on this list. Some
examples of suggested ideas have been things like converting to libtool.
On Mon, Jun 22, 2009 at 09:26:06AM -0700, Steven Dake wrote:
On Mon, 2009-06-22 at 10:59 -0500, David Teigland wrote:
On Sat, Jun 20, 2009 at 11:51:40AM -0700, Steven Dake wrote:
I invite all of our contributors to help define the X.Y roadmap of both
corosync and openais. Please submit
captured your other comments, but curious about following so I
understand what you mean:
On Sun, 2009-06-21 at 07:31 +0200, Fabio M. Di Nitto wrote:
On Sat, 2009-06-20 at 11:51 -0700, Steven Dake wrote:
[snip]
- integration of .spec files and debian/ into upstream to allow people
to easily
On Sun, 2009-06-21 at 19:24 +0200, Fabio M. Di Nitto wrote:
On Sun, 2009-06-21 at 08:43 -0700, Steven Dake wrote:
captured your other comments, but curious about following so I
understand what you mean:
On Sun, 2009-06-21 at 07:31 +0200, Fabio M. Di Nitto wrote:
On Sat, 2009-06-20 at
I invite all of our contributors to help define the X.Y roadmap of both
corosync and openais. Please submit your ideas on this list. Some
examples of suggested ideas have been things like converting to libtool.
Also new service engine ideas are highly welcome. Keep ideas within a 1
month - 3
On Sat, 2009-06-20 at 11:51 -0700, Steven Dake wrote:
I invite all of our contributors to help define the X.Y roadmap of both
corosync and openais. Please submit your ideas on this list. Some
examples of suggested ideas have been things like converting to libtool.
Also new service engine
12 matches
Mail list logo
