Re: [Openais] question stack Pacemaker/corosync on SLES11

2012-03-08 Thread Tim Serong
On 03/08/2012 07:23 PM, alain.mou...@bull.net wrote:
 Hi Darren
 And thanks. I effectively found that the stack is started with the service 
 openais : no more
 'corosync' neither 'pacemaker' lsb scripts.
 But I'am surprised because I think I remind that one or two years ago, it 
 was said that corosync
 was sort of an 'extract' of openais , just to isolate needed code for 
 stack Pacemaker/corosync to
 work ... and now it seems that all is managed again by openais ... so I 
 don't completely
 understand the evolution of 'architecture'  ... but perhaps am I wrong ? 
 Could you clarify the history for me ?

openais 0.80.x (before the creation of corosync) shipped for SLES 11.
You started it by running /etc/init.d/openais start.

corosync 1.2.x + openais 1.1.x shipped for SLES 11 SP1.  corosync is the
core messaging layer, and openais just includes some extra magic for
OCFS2 etc.  But (on SLES at least) the /etc/init.d/openais init script
remained, even though that init script now starts corosync.

The same is true now for SLES 11 SP2 (albeit with corosync 1.4.1);
corosync is what's running, but you use the openais init script to start it.

So your history of project splits and whatnot is correct, you're just
being misled by the name of an init script :)

Regards,

Tim

 
 
 De :Darren Thompson darr...@akurit.com.au
 A : alain.mou...@bull.net
 Date :  07/03/2012 21:03
 Objet : Re: [Openais] question stack Pacemaker/corosync on SLES11
 
 
 
 Alain
 With SLES you also need to install the OpenAIS stack as that is where the 
 init.d service comes from etc.
 Darren
 On Mar 8, 2012 2:14 AM, alain.mou...@bull.net wrote:
 Hi, 
 
 In rpm corosync-1.4.1-4 on rhel are installed : 
 /etc/rc.d/init.d/corosync 
 
 but in rpm corosync-1.4.1-0.11.29 on SLES 11, I don't have anything 
 installed 
 as init.d service, even in /etc/init.d, and I checked the rpm, there is no 
 more /etc/rc.d/init.d/corosync 
 
 same thing for pacemaker , the rpm pacemaker-1.1.6-1.25.1 on SLES does not 
 install the lsb script 
 pacemaker as in the rpm pacemaker-1.1.6-3 on rhel 
 
 could someone tell me how to start the stack Pacemaker/corosync service 
 with the pacemaker-1.1.6-1.25.1/corosync-1.4.1-0.11.29 on SLES 11 ? 
 
 Many thanks 
 Alain
 ___
 Openais mailing list
 Openais@lists.linux-foundation.org
 https://lists.linuxfoundation.org/mailman/listinfo/openais
 
 
 
 
 ___
 Openais mailing list
 Openais@lists.linux-foundation.org
 https://lists.linuxfoundation.org/mailman/listinfo/openais


-- 
Tim Serong
Senior Clustering Engineer
SUSE
tser...@suse.com
___
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/openais


Re: [Openais] question stack Pacemaker/corosync on SLES11

2012-03-08 Thread Steven Dake
On 03/08/2012 03:10 AM, Tim Serong wrote:
 On 03/08/2012 07:23 PM, alain.mou...@bull.net wrote:
 Hi Darren
 And thanks. I effectively found that the stack is started with the service 
 openais : no more
 'corosync' neither 'pacemaker' lsb scripts.
 But I'am surprised because I think I remind that one or two years ago, it 
 was said that corosync
 was sort of an 'extract' of openais , just to isolate needed code for 
 stack Pacemaker/corosync to
 work ... and now it seems that all is managed again by openais ... so I 
 don't completely
 understand the evolution of 'architecture'  ... but perhaps am I wrong ? 
 Could you clarify the history for me ?
 
 openais 0.80.x (before the creation of corosync) shipped for SLES 11.
 You started it by running /etc/init.d/openais start.
 
 corosync 1.2.x + openais 1.1.x shipped for SLES 11 SP1.  corosync is the
 core messaging layer, and openais just includes some extra magic for
 OCFS2 etc.  But (on SLES at least) the /etc/init.d/openais init script
 remained, even though that init script now starts corosync.
 
 The same is true now for SLES 11 SP2 (albeit with corosync 1.4.1);
 corosync is what's running, but you use the openais init script to start it.
 
 So your history of project splits and whatnot is correct, you're just
 being misled by the name of an init script :)
 
 Regards,
 
 Tim
 


 De :Darren Thompson darr...@akurit.com.au
 A : alain.mou...@bull.net
 Date :  07/03/2012 21:03
 Objet : Re: [Openais] question stack Pacemaker/corosync on SLES11



 Alain
 With SLES you also need to install the OpenAIS stack as that is where the 
 init.d service comes from etc.
 Darren
 On Mar 8, 2012 2:14 AM, alain.mou...@bull.net wrote:
 Hi, 

 In rpm corosync-1.4.1-4 on rhel are installed : 
 /etc/rc.d/init.d/corosync 

 but in rpm corosync-1.4.1-0.11.29 on SLES 11, I don't have anything 
 installed 
 as init.d service, even in /etc/init.d, and I checked the rpm, there is no 
 more /etc/rc.d/init.d/corosync 

 same thing for pacemaker , the rpm pacemaker-1.1.6-1.25.1 on SLES does not 
 install the lsb script 
 pacemaker as in the rpm pacemaker-1.1.6-3 on rhel 

 could someone tell me how to start the stack Pacemaker/corosync service 
 with the pacemaker-1.1.6-1.25.1/corosync-1.4.1-0.11.29 on SLES 11 ? 

Another thing to keep in mind is a particular company's product trails
upstream by some time interval...  (which is good, upstream has bugs,
product should not :)

Regards
-steve
 Many thanks 
 Alain
 ___
 Openais mailing list
 Openais@lists.linux-foundation.org
 https://lists.linuxfoundation.org/mailman/listinfo/openais




 ___
 Openais mailing list
 Openais@lists.linux-foundation.org
 https://lists.linuxfoundation.org/mailman/listinfo/openais
 
 

___
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/openais