Re: [ClusterLabs] starting primitive resources of a group without starting the complete group - unclear behaviour

2017-04-21 Thread Ken Gaillot
On 04/21/2017 07:52 AM, Lentes, Bernd wrote:
> 
> 
> - On Apr 21, 2017, at 11:38 AM, Bernd Lentes 
> bernd.len...@helmholtz-muenchen.de wrote:
> 
>> - On Apr 21, 2017, at 1:24 AM, Ken Gaillot kgail...@redhat.com wrote:
>>
>>> On 04/20/2017 02:53 PM, Lentes, Bernd wrote:
>>
>>>
>>> target-role=Stopped prevents a resource from being started.
>>>
>>> In a group, each member of the group depends on the previously listed
>>> members, same as if ordering and colocation constraints had been created
>>> between each pair. So, starting a resource in the "middle" of a group
>>> will also start everything before it.
> 
> Not in each case. 
> 
> 
> I tested a bit:
> target-role of the group: stopped. (This is inherited by the primitives of 
> the group if not declared otherwise.
> If declared for the primitive otherwise this supersedes the target-role of 
> the group.)
> 
> Starting first primitive of the group. Second primitive does not start 
> because target-role is stopped (inherited by the group).
> 
> 
> Next test:
> 
> target-role of the group still "stopped". target-roles of the primitives not 
> decleared otherwise.
> Starting second primitive. First primitive does not start because target-role 
> is stopped, inherited by the group.
> Second primitive does not start because first primitive does not start, 
> although target-role for the second primitive is started.
> Because second primitive needs first one.
> 
> Is my understanding correct ?

Yes

> 
> 
> 
> 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, Heinrich Bassler, Dr. Alfons 
> Enhsen
> Registergericht: Amtsgericht Muenchen HRB 6466
> USt-IdNr: DE 129521671

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] starting primitive resources of a group without starting the complete group - unclear behaviour

2017-04-21 Thread Ken Gaillot
On 04/21/2017 04:38 AM, Lentes, Bernd wrote:
> 
> 
> - On Apr 21, 2017, at 1:24 AM, Ken Gaillot kgail...@redhat.com wrote:
> 
>> On 04/20/2017 02:53 PM, Lentes, Bernd wrote:
> 
>>
>> target-role=Stopped prevents a resource from being started.
>>
>> In a group, each member of the group depends on the previously listed
>> members, same as if ordering and colocation constraints had been created
>> between each pair. So, starting a resource in the "middle" of a group
>> will also start everything before it.
> 
> What is the other way round ? Starting the first of the group ? Will the 
> subsequent follow ?

Groups are generally intended to start and stop as a whole, so I would
expect starting any member explicitly to lead the cluster to want to
start the entire group, but I could be wrong, because only prior members
are required to be started first.

>> Everything in the group inherits this target-role=Stopped. However,
>> prim_vnc_ip_mausdb has its own target-role=Started, which overrides that.
>>
>> I'm not sure what target-role was on each resource at each step in your
>> tests, but the behavior should match that.
>>
> 
> I have to admit that i'm struggling with the meaning of "target-role".
> What does it really mean ? The current status of the resource ? The status of 
> the resource the cluster should try
> to achieve ? Both ? Nothing of this ? Could you clarify that to me ?

"try to achieve"

The cluster doesn't have any direct concept of intentionally starting or
stopping a resource, only of a desired cluster state, and it figures out
the actions needed to get there. The higher-level tools provide the
start/stop concept by setting target-role.

It's the same in practice, but the cluster "thinks" in terms of being
told what the desired end result is, not what specific actions to perform.

> 
> Thanks.
> 
> 
> 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, Heinrich Bassler, Dr. Alfons 
> Enhsen
> Registergericht: Amtsgericht Muenchen HRB 6466
> USt-IdNr: DE 129521671

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] starting primitive resources of a group without starting the complete group - unclear behaviour

2017-04-21 Thread Lentes, Bernd


- On Apr 21, 2017, at 11:38 AM, Bernd Lentes 
bernd.len...@helmholtz-muenchen.de wrote:

> - On Apr 21, 2017, at 1:24 AM, Ken Gaillot kgail...@redhat.com wrote:
> 
>> On 04/20/2017 02:53 PM, Lentes, Bernd wrote:
> 
>> 
>> target-role=Stopped prevents a resource from being started.
>> 
>> In a group, each member of the group depends on the previously listed
>> members, same as if ordering and colocation constraints had been created
>> between each pair. So, starting a resource in the "middle" of a group
>> will also start everything before it.

Not in each case. 


I tested a bit:
target-role of the group: stopped. (This is inherited by the primitives of the 
group if not declared otherwise.
If declared for the primitive otherwise this supersedes the target-role of the 
group.)

Starting first primitive of the group. Second primitive does not start because 
target-role is stopped (inherited by the group).


Next test:

target-role of the group still "stopped". target-roles of the primitives not 
decleared otherwise.
Starting second primitive. First primitive does not start because target-role 
is stopped, inherited by the group.
Second primitive does not start because first primitive does not start, 
although target-role for the second primitive is started.
Because second primitive needs first one.

Is my understanding correct ?



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, Heinrich Bassler, Dr. Alfons Enhsen
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] starting primitive resources of a group without starting the complete group - unclear behaviour

2017-04-21 Thread Lentes, Bernd


- On Apr 21, 2017, at 1:24 AM, Ken Gaillot kgail...@redhat.com wrote:

> On 04/20/2017 02:53 PM, Lentes, Bernd wrote:

> 
> target-role=Stopped prevents a resource from being started.
> 
> In a group, each member of the group depends on the previously listed
> members, same as if ordering and colocation constraints had been created
> between each pair. So, starting a resource in the "middle" of a group
> will also start everything before it.

What is the other way round ? Starting the first of the group ? Will the 
subsequent follow ?


> 
> Everything in the group inherits this target-role=Stopped. However,
> prim_vnc_ip_mausdb has its own target-role=Started, which overrides that.
> 
> I'm not sure what target-role was on each resource at each step in your
> tests, but the behavior should match that.
> 

I have to admit that i'm struggling with the meaning of "target-role".
What does it really mean ? The current status of the resource ? The status of 
the resource the cluster should try
to achieve ? Both ? Nothing of this ? Could you clarify that to me ?


Thanks.


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, Heinrich Bassler, Dr. Alfons Enhsen
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


[ClusterLabs] starting primitive resources of a group without starting the complete group - unclear behaviour

2017-04-20 Thread Lentes, Bernd
Hi,

just for the sake of completeness i'd like to figure out what happens if i 
start one resource, which is a member of a group, but only this resource.
I'd like to see what the other resources of that group are doing. Also if it 
maybe does not make much sense. Just for learning and understanding.

But i'm getting mad about my test results:

first test:

crm(live)# status
Last updated: Thu Apr 20 20:56:08 2017
Last change: Thu Apr 20 20:46:35 2017 by root via cibadmin on ha-idg-2
Stack: classic openais (with plugin)
Current DC: ha-idg-2 - partition with quorum
Version: 1.1.12-f47ea56
2 Nodes configured, 2 expected votes
14 Resources configured


Online: [ ha-idg-1 ha-idg-2 ]

 Clone Set: clone_group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml 
[group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml]
 Started: [ ha-idg-1 ha-idg-2 ]
 prim_stonith_ipmi_ha-idg-1 (stonith:external/ipmi):Started ha-idg-2
 prim_stonith_ipmi_ha-idg-2 (stonith:external/ipmi):Started ha-idg-1

crm(live)# resource start prim_vnc_ip_mausdb

crm(live)# status
Last updated: Thu Apr 20 20:56:44 2017
Last change: Thu Apr 20 20:56:44 2017 by root via crm_resource on ha-idg-1
Stack: classic openais (with plugin)
Current DC: ha-idg-2 - partition with quorum
Version: 1.1.12-f47ea56
2 Nodes configured, 2 expected votes
14 Resources configured


Online: [ ha-idg-1 ha-idg-2 ]

 Clone Set: clone_group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml 
[group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml]
 Started: [ ha-idg-1 ha-idg-2 ]
 prim_stonith_ipmi_ha-idg-1 (stonith:external/ipmi):Started ha-idg-2
 prim_stonith_ipmi_ha-idg-2 (stonith:external/ipmi):Started ha-idg-1
 Resource Group: group_vnc_mausdb
 prim_vnc_ip_mausdb (ocf::heartbeat:IPaddr):Started ha-idg-1   
<===
 prim_vm_mausdb (ocf::heartbeat:VirtualDomain): Started ha-idg-1   
<===



second test:

crm(live)# status
Last updated: Thu Apr 20 21:24:19 2017
Last change: Thu Apr 20 21:20:04 2017 by root via cibadmin on ha-idg-2
Stack: classic openais (with plugin)
Current DC: ha-idg-2 - partition with quorum
Version: 1.1.12-f47ea56
2 Nodes configured, 2 expected votes
14 Resources configured


Online: [ ha-idg-1 ha-idg-2 ]

 Clone Set: clone_group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml 
[group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml]
 Started: [ ha-idg-1 ha-idg-2 ]
 prim_stonith_ipmi_ha-idg-1 (stonith:external/ipmi):Started ha-idg-2
 prim_stonith_ipmi_ha-idg-2 (stonith:external/ipmi):Started ha-idg-1


crm(live)# resource start prim_vnc_ip_mausdb


crm(live)# status
Last updated: Thu Apr 20 21:26:05 2017
Last change: Thu Apr 20 21:25:55 2017 by root via cibadmin on ha-idg-2
Stack: classic openais (with plugin)
Current DC: ha-idg-2 - partition with quorum
Version: 1.1.12-f47ea56
2 Nodes configured, 2 expected votes
14 Resources configured


Online: [ ha-idg-1 ha-idg-2 ]

 Clone Set: clone_group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml 
[group_prim_dlm_clvmd_vg_cluster_01_ocfs2_fs_lv_xml]
 Started: [ ha-idg-1 ha-idg-2 ]
 prim_stonith_ipmi_ha-idg-1 (stonith:external/ipmi):Started ha-idg-2
 prim_stonith_ipmi_ha-idg-2 (stonith:external/ipmi):Started ha-idg-1
 Resource Group: group_vnc_mausdb
 prim_vnc_ip_mausdb (ocf::heartbeat:IPaddr):Started ha-idg-1   
<===
 prim_vm_mausdb (ocf::heartbeat:VirtualDomain): (target-role:Stopped) 
Stopped   <===


Once the second resource of the group is started with the first resource, the 
other time not !?!
Why this unclear behaviour ?

This is my configuration:

primitive prim_vm_mausdb VirtualDomain \
params config="/var/lib/libvirt/images/xml/mausdb_vm.xml" \
params hypervisor="qemu:///system" \
params migration_transport=ssh \
op start interval=0 timeout=120 \
op stop interval=0 timeout=130 \
op monitor interval=30 timeout=30 \
op migrate_from interval=0 timeout=180 \
op migrate_to interval=0 timeout=190 \
meta allow-migrate=true is-managed=true \
utilization cpu=4 hv_memory=8006


primitive prim_vnc_ip_mausdb IPaddr \
params ip=146.107.235.161 nic=br0 cidr_netmask=24 \
meta target-role=Started


group group_vnc_mausdb prim_vnc_ip_mausdb prim_vm_mausdb \
meta target-role=Stopped is-managed=true


Failcounts for the group and the vm are zero on both nodes. Scores for the vm 
on both nodes is -INFINITY.


Starting the vm in the second case (resource start prim_vm_mausdb) succeeds, 
than i have both resources running.

Any ideas ?


Bernd


-- 
Bernd Lentes 

Systemadministration 
institute of developmental genetics 
Gebäude 35.34 - Raum 208 
HelmholtzZentrum München 
bernd.len...@helmholtz-muenchen.de 
phone: +49 (0)89 3187 1241 
fax: +49 (0)89 3187 2294 

Erst wenn man sich auf etwas festlegt kann man Unrecht haben 
Scott Adams
 

Helmholtz Zentrum Muenchen
Deutsches 

Re: [ClusterLabs] starting of resources

2015-08-12 Thread Jan Pokorný
On 11/08/15 09:14 -0500, Ken Gaillot wrote:
 On 08/11/2015 02:12 AM, Vijay Partha wrote:
 After you start pacemaker and then type pcs status, we get the output that
 there are nodes online and the list of resources are empty. We then add
 resources to the nodes. Now what i want is after starting pacemaker can i
 get some resources to be started without adding the resources by making use
 of pcs.
 
 You only need to add resources once. pcs status takes a little time to
 show them when a cluster first starts up; just wait a while and type
 pcs status again. 

On a related note, one could be spared from this manual busy waiting 
if there was a support for that:
https://bugzilla.redhat.com/show_bug.cgi?id=1229822

 The resources themselves will be started as soon as the cluster
 determines they safely can be.
 
 On Tue, Aug 11, 2015 at 12:39 PM, Andrei Borzenkov arvidj...@gmail.com
 wrote:
 
 On Tue, Aug 11, 2015 at 9:44 AM, Vijay Partha vijaysarath...@gmail.com
 wrote:
 
 Can we statically add resources to the nodes. I mean before the
 pacemaker is started can we add resources to the nodes like you
 dont require to make use of pcs resource create. Is this
 possible?
 
 You better explain what you are trying to achieve. Otherwise exactly
 this question was discussed just recently, search archives of this
 list.
 
 If there are archives for this list could you help me out in
 sending the link.

In general, primary archive of the list can be reached at
http://clusterlabs.org/pipermail/users/, with other semi-endorsed 
(having their own merits) mirrors being Gmane:
http://dir.gmane.org/gmane.comp.clustering.clusterlabs.user
and The Mail Archive:
https://www.mail-archive.com/users@clusterlabs.org/

Andrei likely referred to this thread that should cover what, I also
think, you want to achieve:
http://clusterlabs.org/pipermail/users/2015-August/000913.html

Hope this helps.

-- 
Jan (Poki)


pgpNqzXY4JAJv.pgp
Description: PGP signature
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] starting of resources

2015-08-11 Thread Andrei Borzenkov
On Tue, Aug 11, 2015 at 9:44 AM, Vijay Partha vijaysarath...@gmail.com wrote:
 Hi,

 Can we statically add resources to the nodes. I mean before the pacemaker is
 started can we add resources to the nodes like you dont require to make use
 of pcs resource create. Is this possible?


You better explain what you are trying to achieve. Otherwise exactly
this question was discussed just recently, search archives of this
list.

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


Re: [ClusterLabs] starting of resources

2015-08-11 Thread Ken Gaillot
On 08/11/2015 02:12 AM, Vijay Partha wrote:
 After you start pacemaker and then type pcs status, we get the output that
 there are nodes online and the list of resources are empty. We then add
 resources to the nodes. Now what i want is after starting pacemaker can i
 get some resources to be started without adding the resources by making use
 of pcs. If there are archives for this list could you help me out in
 sending the link.

You only need to add resources once. pcs status takes a little time to
show them when a cluster first starts up; just wait a while and type
pcs status again. The resources themselves will be started as soon as
the cluster determines they safely can be.

 On Tue, Aug 11, 2015 at 12:39 PM, Andrei Borzenkov arvidj...@gmail.com
 wrote:
 
 On Tue, Aug 11, 2015 at 9:44 AM, Vijay Partha vijaysarath...@gmail.com
 wrote:
 Hi,

 Can we statically add resources to the nodes. I mean before the
 pacemaker is
 started can we add resources to the nodes like you dont require to make
 use
 of pcs resource create. Is this possible?


 You better explain what you are trying to achieve. Otherwise exactly
 this question was discussed just recently, search archives of this
 list.



___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org