[ClusterLabs] can't start/stop a drbd resource with pacemaker

[Lentes, Bernd]

----- On Jul 18, 2016, at 7:29 PM, Ken Gaillot kgaillot at redhat.com wrote:


>> 
>> Hi Ken,
>> 
>> thanks for your help.
>> 
>> Can i edit them directly ? Or do i have to make a circuit with constraints ?
> 
> Constraints are how they are edited.
> 
> Stop/start aren't used in normal operation, typically only when you're
> doing some sort of maintenance. Normally, you just leave everything
> "started", and the cluster starts/stops services as needed.
> 
> Constraints let you set scores for conditions you desire, such as
> preferring a more powerful node, keeping two resources together, etc.
> 
>> Is pcs available for Suse SLES 11 SP4 ?
>> I searched for it but didn't find it.
>> Is it a good idea to use pcs because i read crm is deprecated ?
> 
> No, crm is still actively maintained and fully supported on SuSE. Pcs is
> used on Fedora/RHEL/CentOS. The two are largely equivalent in
> functionality; only the syntax is different.
> 

I managed to get it run. I deleted the "target-role" in the meta-Attributes from the primitive and from the
ms resource. Then the resource started immediately.
You recommended to leave target-role in default (which is started, i think).
I thought target-role=stopped would be sensfull because then after configuring the resource it would not start
immediately and so maybe disturb the cluster.


I have now this situation:

sunhb58820:~ # ptest -sLV
Allocation scores:
   error: unpack_rsc_op:        Preventing prim_hawk from re-starting anywhere: operation start failed 'not configured' (6)
native_color: prim_ip_hawk allocation score on sunhb58820: -INFINITY
native_color: prim_ip_hawk allocation score on sunhb65277: -INFINITY
native_color: prim_fs_drbd_r0 allocation score on sunhb58820: -INFINITY
native_color: prim_fs_drbd_r0 allocation score on sunhb65277: -INFINITY
native_color: prim_hawk allocation score on sunhb58820: -INFINITY
native_color: prim_hawk allocation score on sunhb65277: -INFINITY
clone_color: ms_drbd_r0 allocation score on sunhb58820: 0
clone_color: ms_drbd_r0 allocation score on sunhb65277: 0
clone_color: prim_drbd_r0:0 allocation score on sunhb58820: 10001
clone_color: prim_drbd_r0:0 allocation score on sunhb65277: 0
clone_color: prim_drbd_r0:1 allocation score on sunhb58820: 0
clone_color: prim_drbd_r0:1 allocation score on sunhb65277: 10001
native_color: prim_drbd_r0:0 allocation score on sunhb58820: 10001
native_color: prim_drbd_r0:0 allocation score on sunhb65277: 0
native_color: prim_drbd_r0:1 allocation score on sunhb58820: -INFINITY
native_color: prim_drbd_r0:1 allocation score on sunhb65277: 10001
prim_drbd_r0:1 promotion score on sunhb65277: 10000
prim_drbd_r0:0 promotion score on sunhb58820: 10000


sunhb58820:~ # crm resource status
 prim_ip_hawk   (ocf::heartbeat:IPaddr):        (target-role:Stopped) Stopped
 prim_fs_drbd_r0        (ocf::heartbeat:Filesystem):    (target-role:Stopped) Stopped
 prim_hawk      (lsb:hawk):     Stopped
 Master/Slave Set: ms_drbd_r0 [prim_drbd_r0]
     Masters: [ sunhb65277 ]
     Slaves: [ sunhb58820 ]



Just for the sake of clarity:

The scores from clone_color and native_color 
are added together ? So E.g. prim_drbd_r0:0 on sunhb58820 has a total of 20002 ?
And prim_drbd_r0:1 is the master and prim_drbd_r0:0 is the slave ?


Bernd
 

Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Dr. Alfons Enhsen, Renate Schlusen (komm.)
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671