FW: [Pacemaker] RFC: How do you upgrade?

Wed May 7 10:40:19 EDT 2008

No sorry - I posted the output from the build yesterday in a tar file.  Here is a copy of that EMAIL with attachment 

Hi 

Andrew thanks for the fast turnaround on this - but it appears that I'm still having a problem - I should have sent this in the first place. But attached please find the output from build process using the latest src rpm. 

Thanks...

Phil Pinto 

-----Original Message-----
From: Andrew Beekhof [mailto:beekhof at gmail.com] 
Sent: Wednesday, May 07, 2008 10:23 AM
To: Pinto, Phil (GTS)
Subject: Re: [Pacemaker] RFC: How do you upgrade?

On May 7, 2008, at 3:50 PM, Pinto, Phil (GTS) wrote:

> Andrew,
>
> Thanks - I will give this method a shot in our QA environment when I  
> roll out the new HB 213 and Pacemaker packages.  By the way - any  
> luck on the GUI packages?  That's the last piece I need to move  
> forward on rhel 4.6. ;-)

the patch didn't help?

>
>
>
>
> Thanks...
>
> Phil Pinto
> ppinto at exchange.ml.com
> GTI - PA Data Center
> 35 Runway Drive
> Levittown, PA 19057
> _______________________________________________
>
> Work Phone:	267-580-3360
> Cell Phone:	917-841-0422
> SMS: 		9178410422 at vtext.com
>
>
> -----Original Message-----
> From: Andrew Beekhof [mailto:beekhof at gmail.com]
> Sent: Wednesday, May 07, 2008 9:14 AM
> To: The Pacemaker cluster resource manager; Pinto, Phil (GTS)
> Subject: Re: [Pacemaker] RFC: How do you upgrade?
>
>
> On May 7, 2008, at 3:08 PM, Pinto, Phil (GTS) wrote:
>
>> Dominik,
>>
>> Does option 3 cause HB to recycle the resources when you re-attach
>> them?
>
> nope - that would defeat the point :-)
>
>> If not this approach would be better than what I'm doing using a
>> rolling upgrade with one fail-over - if the resource can stay up
>> throughout upgrade process.
>>
>>
>>
>> Thanks...
>>
>> Phil Pinto
>> _______________________________________________
>>
>> Work Phone:	267-580-3360
>> Cell Phone:	917-841-0422
>> SMS: 		9178410422 at vtext.com
>>
>> -----Original Message-----
>> From: pacemaker-bounces at clusterlabs.org [mailto:pacemaker-bounces at clusterlabs.org
>> ] On Behalf Of Dominik Klein
>> Sent: Wednesday, May 07, 2008 3:02 AM
>> To: The Pacemaker cluster resource manager
>> Subject: Re: [Pacemaker] RFC: How do you upgrade?
>>
>> Andrew Beekhof wrote:
>>> Me again,
>>>
>>> I'd like to get a sense of how people upgrade their clusters...
>>>
>>> * rolling upgrade (node-by-node)
>>> * big-bang (all nodes at once with all resources stopped)
>>> * detach and reattach (all nodes at once with resources still
>>> running)
>>> * other?
>>>
>>> I'm interested to know how popular the various methods are.
>>>
>>> Andrew
>>
>> I prefer no. 3 (detach and reattach).
>>
>> Works quite nicely.
>>
>> Regards
>> Dominik
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at clusterlabs.org
>> http://list.clusterlabs.org/mailman/listinfo/pacemaker
>> --------------------------------------------------------
>>
>> This message w/attachments (message) may be privileged, confidential
>> or proprietary, and if you are not an intended recipient, please
>> notify the sender, do not use or share it and delete it. Unless
>> specifically indicated, this message is not an offer to sell or a
>> solicitation of any investment products or other financial product
>> or service, an official confirmation of any transaction, or an
>> official statement of Merrill Lynch. Subject to applicable law,
>> Merrill Lynch may monitor, review and retain e-communications (EC)
>> traveling through its networks/systems. The laws of the country of
>> each sender/recipient may impact the handling of EC, and EC may be
>> archived, supervised and produced in countries other than the
>> country in which you are located. This message cannot be guaranteed
>> to be secure or error-free. This message is subject to terms
>> available at the following link: http://www.ml.com/e-communications_terms/
>> . By messaging with Merrill Lynch you consent to the foregoing.
>> --------------------------------------------------------
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at clusterlabs.org
>> http://list.clusterlabs.org/mailman/listinfo/pacemaker
> --------------------------------------------------------
>
> This message w/attachments (message) may be privileged, confidential  
> or proprietary, and if you are not an intended recipient, please  
> notify the sender, do not use or share it and delete it. Unless  
> specifically indicated, this message is not an offer to sell or a  
> solicitation of any investment products or other financial product  
> or service, an official confirmation of any transaction, or an  
> official statement of Merrill Lynch. Subject to applicable law,  
> Merrill Lynch may monitor, review and retain e-communications (EC)  
> traveling through its networks/systems. The laws of the country of  
> each sender/recipient may impact the handling of EC, and EC may be  
> archived, supervised and produced in countries other than the  
> country in which you are located. This message cannot be guaranteed  
> to be secure or error-free. This message is subject to terms  
> available at the following link: http://www.ml.com/e-communications_terms/ 
> . By messaging with Merrill Lynch you consent to the foregoing.
> --------------------------------------------------------
--------------------------------------------------------

This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rebuild.tar.gz
Type: application/x-gzip
Size: 12978 bytes
Desc: rebuild.tar.gz
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20080507/36bb2c86/attachment-0001.bin>