On May 8, 2008, at 8:43 AM, Keisuke MORI wrote:
Hi,
Andrew Beekhof <[EMAIL PROTECTED]> writes:
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 node
Hi,
Andrew Beekhof <[EMAIL PROTECTED]> writes:
> 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)
>
> >>> 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 p
On May 8, 2008, at 7:52 AM, Junko IKEDA wrote:
Hi,
The changes for Pacemaker 1.0 include an overhaul of configuration
syntax.
We have a few things in mind for this already, but I'd also like to
get people's opinion on which parts need the most attention.
When are you planning to release Pa
Hi,
> The changes for Pacemaker 1.0 include an overhaul of configuration
> syntax.
>
> We have a few things in mind for this already, but I'd also like to
> get people's opinion on which parts need the most attention.
When are you planning to release Pacemaker 1.0?
New features which you are imp
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 ou
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 res
Dominik,
Does option 3 cause HB to recycle the resources when you re-attach them? 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
___
Lars Marowsky-Bree wrote:
On 2008-05-07T09:02:17, Dominik Klein <[EMAIL PROTECTED]> wrote:
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 res
On 2008-05-07T09:02:17, Dominik Klein <[EMAIL PROTECTED]> wrote:
>> 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 runn
On 2008-05-06T15:02:47, Andrew Beekhof <[EMAIL PROTECTED]> 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)
The first two is most of what I see in the field and d
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
12 matches
Mail list logo
