Re: [Pacemaker] Move DRBD master

[Vadym Chepkov]

On Oct 19, 2010, at 9:18 AM, Dan Frincu wrote:

> 
> 
> Vadym Chepkov wrote:
>> 
>> 
>> On Oct 19, 2010, at 3:42 AM, Pavlos Parissis wrote:
>> 
>>> 
>>> 
>>> On 19 October 2010 01:18, Vadym Chepkov  wrote:
>>> Hi,
>>> 
>>> What is the crm shell command to move drbd master to a different node?
>>> 
>>> 
>>> take a look at this 
>>> http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg06300.html
>>> ___
>> 
>> Wow, not the friendliest command I would say. Maybe "move" command can be 
>> enhanced to provide something similar?
>> 
>> Thanks,
>> Vadym
> The crm resource move/migrate  provides/creates the location constraint 
> within the crm shell. 
> 
> In the example I gave:
> 
> crm resource migrate ms_drbd_storage
> 
> WARNING: Creating rsc_location constraint 'cli-standby-ms_drbd_storage' with 
> a score of -INFINITY for resource ms_drbd_storage on cluster1.
>   This will prevent ms_drbd_storage from running on cluster1 until the 
> constraint is removed using the 'crm_resource -U' command or manually with 
> cibadmin
>   This will be the case even if cluster1 is the last node in the cluster
>   This message can be disabled with -Q
> 
> The warning message appears in the console after executing the command in the 
> crm shell, running a crm configure show reveals the following:
> 
> location cli-standby-ms_drbd_storage ms_drbd_storage \
> rule $id="cli-standby-rule-ms_drbd_storage" -inf: #uname eq cluster1
> 
> The example in the UEL above has been done manually to (probably) provide an 
> advisory placement constraint, the one set by crm resource move  is a 
> mandatory placement constraint.
> 


It misses $role=Master and doesn't work because of that.

Vadym

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] is recovery from link failure now automatic?

[Juha Heinanen]

Dan Frincu writes:

> You can take a look at the following and see if it helps
> 
> http://lists.linux-ha.org/pipermail/linux-ha/2010-October/041473.html

if i understood correctly, conclusion from the thread is

  Active/active rings seem to work well enough - but they do not recover
  without manual intervention.

i'll check again one year from now if corosync then would not require
manual babysitting, which in my opinion should not be a component of
a "high availability" solution.

-- juha

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Move DRBD master

[Dan Frincu]

Vadym Chepkov wrote:


On Oct 19, 2010, at 3:42 AM, Pavlos Parissis wrote:




On 19 October 2010 01:18, Vadym Chepkov > wrote:


Hi,

What is the crm shell command to move drbd master to a different
node?


take a look at this
http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg06300.html
___


Wow, not the friendliest command I would say. Maybe "move" command can 
be enhanced to provide something similar?


Thanks,
Vadym
The _crm resource move/migrate _ provides/creates the location 
constraint within the crm shell.


In the example I gave:

_crm resource migrate ms_drbd_storage_

/WARNING: Creating rsc_location constraint 'cli-standby-ms_drbd_storage' 
with a score of -INFINITY for resource ms_drbd_storage on cluster1.
*  This will prevent ms_drbd_storage from running on cluster1 until 
the constraint is removed using the 'crm_resource -U' command or 
manually with cibadmin

 This will be the case even if cluster1 is the last node in the cluster
*  This message can be disabled with -Q
/
The warning message appears in the console after executing the command 
in the crm shell, running a crm configure show reveals the following:


/location cli-standby-ms_drbd_storage ms_drbd_storage \
   rule $id="cli-standby-rule-ms_drbd_storage" -inf: #uname eq cluster1
/
The example in the UEL above has been done manually to (probably) 
provide an advisory placement constraint, the one set by _crm resource 
move _ is a mandatory placement constraint.


Regards,

Dan




___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
  


--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Move DRBD master

[Dan Frincu]

Vadym Chepkov wrote:

On Oct 19, 2010, at 3:13 AM, Dan Frincu wrote:

  

Vadym Chepkov wrote:


Hi,

What is the crm shell command to move drbd master to a different node?
 
  

# crm resource help migrate

Migrate a resource to a different node. If node is left out, the
resource is migrated by creating a constraint which prevents it from
running on the current node. Additionally, you may specify a
lifetime for the constraint---once it expires, the location
constraint will no longer be active.

Usage:
...
  migrate  [] []

crm resource migrate ms_drbd_storage

WARNING: Creating rsc_location constraint 'cli-standby-ms_drbd_storage' with a 
score of -INFINITY for resource ms_drbd_storage on cluster1.
  This will prevent ms_drbd_storage from running on cluster1 until the 
constraint is removed using the 'crm_resource -U' command or manually with 
cibadmin
  This will be the case even if cluster1 is the last node in the cluster
  This message can be disabled with -Q


This also made me to remind that I was wondering, is there a way to
demote one instance of multi-master ms resource away from particular
node (forcibly switch it to a slave state on that node). I didn't find
the answer too. Is it possible with crm shell?

Same as above, just specify the node in the command.




Have you actually tried it? This command doesn't work for this case.

  
To be honest, no, I actually don't think it's viable since in a 
multi-master architecture you have a one-to-one relationship on the DRBD 
side. There's a thread related to this over on the DRBD mailing list, 
still no reply yet, might want to check it out over the next couple of 
days for progress.


Regards,

Dan

Regards,

Dan


Thank you,
Vadym

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
 
  

--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania


___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker




___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
  


--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] unpack_rsc_op: Hard error

[Pavlos Parissis]

On 19 October 2010 14:16, Andrew Beekhof  wrote:

> On Mon, Oct 11, 2010 at 11:25 AM, Pavlos Parissis
>  wrote:
> > On 10 October 2010 17:39, Andrew Beekhof  wrote:
> >> On Sat, Oct 9, 2010 at 11:20 PM, Pavlos Parissis
> >>  wrote:
> >>> Hi,
> >>>
> >>> Does anyone know why PE wants to unpack resources on nodes that will
> >>> never run due to location constraints?
> >>
> >> Because part of its job is to make sure they dont run there.
> >>
> >>> I am getting this messages and I am wondering if they harmless or not.
> >>
> >> Basically yes.  We've since reduced this to an informational message.
> >>
> > So, it is not necessary to place the LSB script of a resource to nodes
> > where the resource will never run, due to location constraints.Am I
> > right?
>
> Correct, though the probes might show up in crm_mon as "failed".
>
>
>
Even it is correct, I placed the script on all nodes, just to avoid the
warnings.

Thanks,
Pavlos
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

[Pacemaker] DRBD MC 0.8.2 / Pacemaker GUI

[Rasto Levrinc]

Hi,

This is the next DRBD MC beta release 0.8.2. DRBD MC is a Java application
that helps to configure DRBD, Pacemaker, VMs or any combination of them.
It uses SSH to connect to the cluster from a desktop computer.

In this minor release couple of minor enhancements were implemented and
minor issues were fixed.

Now it is possible to specify location according the pingd results. At the
moment, the "on host with most connections" and "stop on host with no
connection" can be chosen. Let me now if there are some other uses for
that.

The gathering information from servers has been optimized, fixed and
tuned, so that it needs much less CPU on the servers then before.

Screenshots:

http://oss.linbit.com/drbd-mc/img/drbd-mc-0.8.2.png
http://oss.linbit.com/drbd-mc/img/drbd-mc-0.8.2-drbd.png

You can get DRBD MC here:

http://www.drbd.org/mc/management-console/
http://oss.linbit.com/drbd-mc/DMC-0.8.2.jar
http://oss.linbit.com/drbd-mc/drbd-mc-0.8.2.tar.gz

You can download it and start it with "java -jar DMC-0.8.2.jar" command or
you can use Java Webstart. First of all, please don't run it on one node
with X forwarding, but on the desktop.

It works with SUN Java 6 and OpenJDK 7. It does not work good with OpenJDK
1.6 and this is probably what you have if you have OpenJDK installed as
Java. With this so-called fully compatible Java version it runs slow,
experiences random errors or may even hang.

DRBD MC is compatible with Heartbeat 2.1.3 to the Pacemaker 1.1.2 with
Corosync or Heartbeat and DRBD 8.

Here are the most important changes:
* fix DRBD panels updating
* make rrp_mode=active default in corosync.conf
* fix Ubuntu Lucid software installation
* fix Fedora 13 software installation
* using backports repos for Debian software installation
* fix on-mouse-over ptest not working all the time
* hb 2.1.4: fix when using rsc_order without type argument
* improved ssh connection handling
* allow moving group resources up and down in the group
* fix progress indicator
* pingd location constraints
* score 0 for order is shown better
* fix tooltips showing old info
* move order score to the not advanced section
* group services fixes
* make failed resource red again
* make migrate-from the default migrate option
* migrate all and unmigrate all menu items
* add drop down list with hosts for stonith hostlists parameter
* improve colors
* add actions menu to the block devices
* fix retry button in host configuration wizard
* fix standby mode for old heartbeats

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.


___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] unpack_rsc_op: Hard error

[Andrew Beekhof]

On Mon, Oct 11, 2010 at 11:25 AM, Pavlos Parissis
 wrote:
> On 10 October 2010 17:39, Andrew Beekhof  wrote:
>> On Sat, Oct 9, 2010 at 11:20 PM, Pavlos Parissis
>>  wrote:
>>> Hi,
>>>
>>> Does anyone know why PE wants to unpack resources on nodes that will
>>> never run due to location constraints?
>>
>> Because part of its job is to make sure they dont run there.
>>
>>> I am getting this messages and I am wondering if they harmless or not.
>>
>> Basically yes.  We've since reduced this to an informational message.
>>
> So, it is not necessary to place the LSB script of a resource to nodes
> where the resource will never run, due to location constraints.Am I
> right?

Correct, though the probes might show up in crm_mon as "failed".

>
> Cheers,
> Pavlos
>
> ___
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: 
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] problem about move node from one cluster to another cluster

[Andrew Beekhof]

> how does this fit the release schedule?

The short answer is that it doesn't.
 
The community generally does a pretty good job, heartbeat2 was a dead end that 
was put out of its misery years ago[1] and openais 0.80 was something like 5 
years old when pacemaker started supporting it.  Pacemaker 1.0 itself is almost 
3 years old now iirc. 

But long term support will always be hole that enterprise vendors fill with 
products like sles, rhel and ubuntu LTS.

With limited resources, projects need to choose their battles.
We can't be everything to everyone, so we let the enterprise distress do what 
they do best while we concentrate on improving the core software.


[1] there were also unique circumstances that necessitated killing hb2 early

Sent from my iPad

On 13 Oct 2010, at 13:37, Dan Frincu  wrote:

> Hi,
> 
> Yes, it sometime needs to be killed manually because the process hangs and 
> the restart operation never seems to end. Yet another reason to upgrade.
> 
> All,
> 
> Question: given the fact that this type of software usually gets installed on 
> a platform once and then usually goes into service for many years, on servers 
> where downtime should be kept to a minimum (gee, that's why you use a cluster 
> :)), how does this fit the release schedule? 
> 
> I mean, there are plenty of users out there with question related to 
> Heartbeat 2, openais-0.8.0, and so on and so forth, some environments cannot 
> be changed lightly, others, not at all, so what is the response to "this 
> feature doesn't work on that version of software?", upgrade? If so, at what 
> interval (keeping in mind that you probably want the stable packages on your 
> system)?
> 
> I'm asking this because when I started working with openais, the latest 
> version available was 0.8.0 on some SUSE repos that aren't available anymore.
> 
> Regards,
> 
> Dan
> 
> jiaju liu wrote:
>> 
>> Hi,
>> 
>> Depending on the openais version (please mention it)
>>  
>> Hi
>> Thank you for your reply my openais version is openais-0.80.5-15.1
>> pacemaker version is pacemaker-1.0.5-4.1.
>> I use restart but it does not work. I found it could not stop
>>  
>>  
>> this behavior could 
>> happen, I've seen it as well, on openais-0.8.0. What I've done to fix it 
>> was to restart the openais process via /etc/init.d/openais restart. And 
>> then it worked, however, this was one of the reasons I updated the 
>> packages to the latest versions of corosync, pacemaker, etc. The tricky 
>> part was doing the migration procedure for upgrading production servers  
>>
>> without service downtime, but that's another story.
>> 
>> 
>>  
> 
> -- 
> Dan FRINCU
> Systems Engineer
> CCNA, RHCE
> Streamwide Romania
> ___
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: 
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] reboot -v 100 constantly showing up in the 'standby' /var/log/cluster/corosync.log file

[Andrew Beekhof]

Newer versions of crm_attribute support the --quiet option to supress these 
messages.
They're nothing to worry about, just drbd updating the preferences for which 
node(s) should be promoted.

Sent from my iPad

On 12 Oct 2010, at 16:18, Mike A Meyer  wrote:

> We are running an Active/Passive two node cluster with Pacemaker/Corosync and 
> on the 'standby' node we are constantly seeing this message in the 
> /var/log/cluster/corosync.log file. 
> 
> Oct 12 09:11:30 qa-magdb2 crm_attribute: [12846]: info: Invoked: 
> crm_attribute -N qa-magdb2 -n master-mysql_drbd:1 -l reboot -v 100 
> Oct 12 09:11:45 qa-magdb2 crm_attribute: [12874]: info: Invoked: 
> crm_attribute -N qa-magdb2 -n master-mysql_drbd:1 -l reboot -v 100 
> Oct 12 09:12:00 qa-magdb2 crm_attribute: [12917]: info: Invoked: 
> crm_attribute -N qa-magdb2 -n master-mysql_drbd:1 -l reboot -v 100 
> Oct 12 09:12:15 qa-magdb2 crm_attribute: [12949]: info: Invoked: 
> crm_attribute -N qa-magdb2 -n master-mysql_drbd:1 -l reboot -v 100 
> 
> We are wondering what that all means and what does the reboot -v 100 mean?  
> We are not using Stonith as I have seen references to Stonith setup and 
> 'reboot' and we don't remember setting up any value for reboot or '100'.
> Everything seems to be working fine and failing over when we need to.  Just 
> curious what these messages above mean.   Any help would greatly be 
> appreciated. 
> 
> Our configuration file is below. 
> 
> node qa-magdb1 
> node qa-magdb2 
> primitive email_notify ocf:heartbeat:MailTo \ 
> params email="test...@test.com" subject="DRBD/Pacemaker FAILOVER!!! " 
> \ 
> op monitor interval="10" timeout="10" depth="0" 
> primitive mysql_drbd ocf:linbit:drbd \ 
> params drbd_resource="mysql" \ 
> op monitor interval="15s" 
> primitive mysql_fs ocf:heartbeat:Filesystem \ 
> params device="/dev/drbd0" directory="/mnt/mysql/" fstype="ext3" 
> primitive mysql_service ocf:heartbeat:mysql \ 
> params binary="/usr/bin/mysqld_safe" config="/mnt/mysql/my.cnf" 
> datadir="/mnt/mysql/data" pid="/var/run/mysql/mysqld.pid" 
> socket="/var/run/mysql/mysql.sock" test_passwd="testingit" 
> test_table="mysql.user" test_user="root" \ 
> op monitor interval="20s" timeout="10s" \ 
> meta migration-threshold="10" target-role="Started" 
> primitive mysql_vip ocf:heartbeat:IPaddr2 \ 
> params ip="172.26.76.100" nic="eth0" 
> group mysql mysql_fs mysql_vip mysql_service email_notify 
> ms ms_mysql_drbd mysql_drbd \ 
> meta master-max="1" master-node-max="1" clone-max="2" 
> clone-node-max="1" notify="true" 
> location primary_mysql mysql 10: qa-magdb1 
> location primary_mysql_drbd ms_mysql_drbd 10: qa-magdb1 
> location standby_mysql mysql 5: qa-magdb2 
> location standby_mysql_drbd ms_mysql_drbd 5: qa-magdb2 
> colocation mysql_on_drbd inf: mysql ms_mysql_drbd:Master 
> order mysql_after_drbd inf: ms_mysql_drbd:promote mysql:start 
> property $id="cib-bootstrap-options" \ 
> dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \ 
> cluster-infrastructure="openais" \ 
> expected-quorum-votes="2" \ 
> stonith-enabled="false" \ 
> no-quorum-policy="ignore" \ 
> cluster-recheck-interval="0" 
> 
> Thanks, 
> Mike 
> 
> 
> -
> 
> This e-mail message is intended only for the personal use of the recipient(s)
> named above. If you are not an intended recipient, you may not review, copy or
> distribute this message. If you have received this communication in error,
> please notify the CDS Global Help Desk (cdshelpd...@cds-global.com) 
> immediately
> by e-mail and delete the original message.
> 
> -
> ___
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: 
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Move DRBD master

[Vadym Chepkov]

On Oct 19, 2010, at 3:42 AM, Pavlos Parissis wrote:

> 
> 
> On 19 October 2010 01:18, Vadym Chepkov  wrote:
> Hi,
> 
> What is the crm shell command to move drbd master to a different node?
> 
> 
> take a look at this 
> http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg06300.html
> ___

Wow, not the friendliest command I would say. Maybe "move" command can be 
enhanced to provide something similar?

Thanks,
Vadym

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Move DRBD master

[Vadym Chepkov]

On Oct 19, 2010, at 3:13 AM, Dan Frincu wrote:

> Vadym Chepkov wrote:
>> Hi,
>> 
>> What is the crm shell command to move drbd master to a different node?
>>  
> # crm resource help migrate
> 
> Migrate a resource to a different node. If node is left out, the
> resource is migrated by creating a constraint which prevents it from
> running on the current node. Additionally, you may specify a
> lifetime for the constraint---once it expires, the location
> constraint will no longer be active.
> 
> Usage:
> ...
>   migrate  [] []
> 
> crm resource migrate ms_drbd_storage
> 
> WARNING: Creating rsc_location constraint 'cli-standby-ms_drbd_storage' with 
> a score of -INFINITY for resource ms_drbd_storage on cluster1.
>   This will prevent ms_drbd_storage from running on cluster1 until the 
> constraint is removed using the 'crm_resource -U' command or manually with 
> cibadmin
>   This will be the case even if cluster1 is the last node in the cluster
>   This message can be disabled with -Q
> 
> 
> This also made me to remind that I was wondering, is there a way to
> demote one instance of multi-master ms resource away from particular
> node (forcibly switch it to a slave state on that node). I didn't find
> the answer too. Is it possible with crm shell?
> 
> Same as above, just specify the node in the command.
> 

Have you actually tried it? This command doesn't work for this case.


> Regards,
> 
> Dan
>> Thank you,
>> Vadym
>> 
>> ___
>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> 
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: 
>> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>  
> 
> -- 
> Dan FRINCU
> Systems Engineer
> CCNA, RHCE
> Streamwide Romania
> 
> 
> ___
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: 
> http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker


___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Move DRBD master

[Pavlos Parissis]

On 19 October 2010 01:18, Vadym Chepkov  wrote:

> Hi,
>
> What is the crm shell command to move drbd master to a different node?
>
>
take a look at this
http://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg06300.html
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Re: [Pacemaker] Move DRBD master

[Dan Frincu]

Vadym Chepkov wrote:

Hi,

What is the crm shell command to move drbd master to a different node?
  

# crm resource help migrate

Migrate a resource to a different node. If node is left out, the
resource is migrated by creating a constraint which prevents it from
running on the current node. Additionally, you may specify a
lifetime for the constraint---once it expires, the location
constraint will no longer be active.

Usage:
...
   migrate  [] []

crm resource migrate ms_drbd_storage

WARNING: Creating rsc_location constraint 'cli-standby-ms_drbd_storage' 
with a score of -INFINITY for resource ms_drbd_storage on cluster1.
   This will prevent ms_drbd_storage from running on cluster1 until 
the constraint is removed using the 'crm_resource -U' command or 
manually with cibadmin
   This will be the case even if cluster1 is the last node in the 
cluster

   This message can be disabled with -Q


This also made me to remind that I was wondering, is there a way to
demote one instance of multi-master ms resource away from particular
node (forcibly switch it to a slave state on that node). I didn't find
the answer too. Is it possible with crm shell?

Same as above, just specify the node in the command.

Regards,

Dan

Thank you,
Vadym

___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
  


--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania


___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker