Florian Haas | 1 Mar 09:10 2010

Re: DRBD Management Console 0.6.0

On 2010-02-28 21:09, Cristian Mammoli - Apra Sistemi wrote:
> Cristian Mammoli - Apra Sistemi wrote:
> 
>> Cause I am the one who wrote it in the first place and the version I
>> use has some minor improvement and fixes.
> 
> And the version shipped with pacemaker is different from the one I
> posted 2 years ago on the Linux-HA ML. It's broken, don't use it. I'll
> issue a bug report for that.

RAs don't ship with Pacemaker. They ship with the Linux-HA
resource-agents package. I'll respond to your other email in a minute.

Cheers,
Florian

_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Florian Haas | 1 Mar 09:10 2010

Re: Updated VMwareVM resource agent

On 02/28/2010 10:36 PM, Cristian Mammoli - Apra Sistemi wrote:
> In 2008 I posted on the linux-ha ML a resource agent script for vmware
> server 2 virtual machines. It has been slightly modified and shipped
> with heartbeat and (now) pacemaker.
> Actually the script is broken:
> the script is named "vmware" while the "resource-agent name" is set to
> "vmwarevm". They should match.

This was fixed upstream 2 months ago; both are now named "vmware":

http://hg.linux-ha.org/agents/rev/4b1f781a51cf

> Besides that, even if all the "OCF_" stuff is correctly declared the
> script always reports:
> "WARNING: Could not find out virtual machine name"
>
> That's because in the modified version the function "set_environment" is
> not properly executed before actually starting and stopping resources.

This was also fixed upstream,
http://hg.linux-ha.org/agents/rev/ae1ebe1f151b.

There are a few other upstream changes you may have missed. Could you
please rebase your patch on current upstream and send a hg export patch?
Or, alternatively, could you diff your new version against the one you
orginally submitted, and submit that patch? That makes merging a whole
lot easier for us. Thanks!

Cheers,
Florian
(Continue reading)

Picon

Re: Updated VMwareVM resource agent

Florian Haas wrote:
There are a few other upstream changes you may have missed. Could you
> please rebase your patch on current upstream and send a hg export patch?
> Or, alternatively, could you diff your new version against the one you
> orginally submitted, and submit that patch? That makes merging a whole
> lot easier for us. Thanks!

I don't have the original script anymore and using cut/paste from a 
google search makes a mess with spacing etc.
How can I get an up to date version of your RA?

--

-- 
Cristian Mammoli
APRA SISTEMI srl
Florian Haas | 1 Mar 10:12 2010

Re: Updated VMwareVM resource agent

On 2010-03-01 09:56, Cristian Mammoli - Apra Sistemi wrote:
> Florian Haas wrote:
> There are a few other upstream changes you may have missed. Could you
>> please rebase your patch on current upstream and send a hg export patch?
>> Or, alternatively, could you diff your new version against the one you
>> orginally submitted, and submit that patch? That makes merging a whole
>> lot easier for us. Thanks!
> 
> I don't have the original script anymore and using cut/paste from a
> google search makes a mess with spacing etc.

I've found your original submission in my local list archive, and will
send that along in an off-list email.

> How can I get an up to date version of your RA?

Here:
http://hg.linux-ha.org/agents/raw-file/tip/heartbeat/vmware

Florian

_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Rasto Levrinc | 1 Mar 11:20 2010

Re: [drbd-mc] DRBD Management Console 0.6.0

Am Sunday 28 February 2010 schrieb Rasto Levrinc:
> Hi,
>
> This is the next DRBD-MC beta release 0.6.0. DRBD-MC is a Java GUI that
> helps to configure DRBD/Pacemaker/Corosync/Openais/Heartbeat clusters. It
> is compatible with Heartbeat 2.1.3 to the latest and greatest Pacemaker
> with both communication stacks and DRBD 8.

I've just discovered a not critical but quite annoying bug in 0.6.0 release, 
where internal guiid would be saved in cib. This is not a problem for the 
cluster, but if you use crm shell as well, it would complain loudly about 
this parameter. You can simply remove the "guiid" paramater in crm shell 
every time you save the configuration, only to get it back in DRBD-MC.

In order not to be annoying for very long I've just released DRBD-MC 0.6.1 
with just that bug fixed.

Rasto Levrinc

--

-- 
: Dipl-Ing Rastislav Levrinc
: DRBD-MC http://www.drbd.org/mc/management-console/
: DRBD/HA support and consulting http://www.linbit.com/
DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
Simon Horman | 1 Mar 11:23 2010
Picon

[Announce] #debian-ha

Hi,

I have established the #debian-ha channel on irc.freenode.net.
I hope that this can aid in the co-ordination of packaging of Linux-HA,
Pacemaker and OpenAIS for Debian.
Andrew Beekhof | 1 Mar 11:27 2010
Picon

Re: ignoring transitional memberships

On Fri, Feb 26, 2010 at 7:55 PM, Alan Jones <falancluster@...> wrote:
> On Fri, Feb 26, 2010 at 2:57 AM, Andrew Beekhof <andrew@...> wrote:
>>
>> Not only safe but essential, otherwise B would kill A for no reason.
>> Transitional memberships are just corosync's way of saying "i;m still
>> working, but this is what I have so far".
>
> The best explanation I've found for the transitional membership is in:
> "Group Communication Specifications: A Comprehensive Study" 1999
> Vitenberg/Chockler/Keidar/Dolev
>
> It relates to support for positionable memberships.  In Pacemaker it might
> be the case that for B to
> become DC and modify the CIB without A, B would have to STONITH A.  If that
> is the case, then when
> A gets a new membership including B he can assume that B has not modified
> the CIB without him.
>
> However, I'm not convinced that he can assume that B has received all the
> same messages during
> the transition.

He doesn't have to.
The CIB contains version information that it uses to resolve conflicts
and ensure everyone is up-to-date.

The only time you'd have trouble is if you made different changes to
both A and B while they couldn't see each other.
And that would be a strange thing to do.

(Continue reading)

Andrew Beekhof | 1 Mar 11:34 2010
Picon

Re: Unnecessarily Failover when restarting network!!!

On Thu, Feb 25, 2010 at 7:32 PM, Jayakrishnan
<jayakrishnanlll@...> wrote:
> Hiiii,
> One more question...
> I managed make every things to work with Heartbeat-Pacemaker (2.99 - 1.0.5).
> I have a cluster ip, pingd, postgresql lsb and a lsb resource successfully
> configured for slony replication .. But when I restart network via
>
> # /etc/init.d/networking restart
>
> split-brain is happening.. I have increases my monitor intervels and even
> dampening in all resources and even in by ha.cf file but still split brain
> is happening. Please advice me!!!

I guess its permanently affecting Heartbeat's communication or
membership mechanisms.

> As I have specified dampening as 90s, the resources are sticking in the
> master for 90s and the n gets started in slave. that is for 90s it is in
> tact and gets shifted .. What could be the reason??
> Here stonith would not work because the resources (maybe pingd) are not
> supposed to do a failover if I do restart my network in my active machine..
>
> Please advice...
>
> ha.cf
>
> autojoin none
> keepalive 2
> deadtime 60
(Continue reading)

Picon

Re: Updated VMwareVM resource agent

Florian Haas wrote:

>> How can I get an up to date version of your RA?
> 
> Here:
> http://hg.linux-ha.org/agents/raw-file/tip/heartbeat/vmware
> 

I made some additional modification and created a patch file against 
this script. I moved the "set_env" function inside the "validate-all" 
function.

--

-- 
Cristian Mammoli
APRA SISTEMI srl
Via Brodolini,6 Jesi (AN)
tel dir. 0731 719822

Web   www.apra.it
e-mail  c.mammoli@...
Attachment (VMwareVM.patch): text/x-patch, 11 KiB
_______________________________________________
Pacemaker mailing list
Pacemaker@...
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Picon

Re: DRBD Management Console 0.6.0

Hi again...

I tried adding a resource with DMC. My script needs 2 mandatory 
parameters: vmxpath and vimshbin

In the gui i filled the field for vmxpath while vimshbin was already 
present because the resource agent has:

<shortdesc lang="en">vmware-vim-cmd path</shortdesc>
<content type="string" default="/usr/bin/vmware-vim-cmd"/>

Anyway the resulting configuration is:

primitive res_VMwareVM_1 ocf:apra:VMwareVM \
         params vmxpath="/datastore1/openfiler/openfiler.vmx" \
         operations $id="res_VMwareVM_1-operations" \
         op stop interval="0" timeout="900" \
         op start interval="0" timeout="900" \
         meta target-role="stopped"

There is no "vimshbin" parameter. It should be:

params 
vmxpath="/datastore1/openfiler/openfiler.vmx"vimshbin="/usr/bin/vmware-vim-cmd" 
\

As a consequenze the resource fails to start with 
res_VMwareVM_1_monitor_0 (node=srvha01.apra.it, call=251, rc=2, 
status=complete): invalid parameter

(Continue reading)


Gmane