[ClusterLabs] DRBD on CentOS8 anyone?

[Michael Schwartzkopff]

Hi,


did anybody succeed in installing / compiling DRBD for CentOS8? It seems
to cause some trouble in my setup.

Michael Schwartzkopff

Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] IPaddr2 RA and multicast mac

[Michael Schwartzkopff]

Am 04.09.19 um 00:27 schrieb Tomer Azran:
> Hello,
>
> When using IPaddr2 RA in order to set a cloned IP address resource:
>
> pcs resource create vip1 ocf:heartbeat:IPaddr2 ip=10.0.0.100 iflabel=vip1 
> cidr_netmask=24 flush_routes=true op monitor interval=30s
> pcs resource clone vip1 clone-max=2 clone-node-max=2 globally-unique=true
>
> Then the cluster set the iptables CLUSTERIP module, and the result is 
> something like that:
>
> # iptables -L -n
> .
> .
> .
> CLUSTERIP  all  --  0.0.0.0/010.0.0.100 CLUSTERIP 
> hashmode=sourceip-sourceport clustermac=A1:DE:DE:89:A6:FE total_nodes=2 
> local_node=1 hash_init=0
> .
> .
> .
>
> The problem is that the RA picks a clustermac address which is not on the 
> multicast range (must start with 01:00:5E)
> If not working with a multicast address, the traffic is being treated as 
> broadcast which is bad.
>
> I found that you can set a multicast mac if you use the "mac" parameter, 
> which solves the issue.
>
> Can the RA default be changed to use multicast range?
> In addition, I think that you might need to update the documentation 
> (https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/_clone_the_ip_address.html)
>  and instruct users to use the mac parameter when creating the resource. In 
> addition, I think that the documentation should instruct the user to enable 
> multicast traffic on the network, which is not enabled by default.
>
> Tomer Azran
> IDM & LINUX Professional Services
>
> tomer.az...@edp.co.il
> m: +972-52-6389961
> t: +972-3-6438222
> f: +972-3-6438004
>
> [http://www.edp.co.il/logo1-small.png]
> www.edp.co.il
>
>
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/


Hi,


im Layer2 frames the least important bit of the most important byte
decides if it is multicast / broadcast or unicat. A "0" tells the switch
it is unicast and a "1" indicates a multicast address.

Depending on the switch vendor, the switch does learn the mutlicast MAC
address for the interface where it sees such a packet comming in or not.


A IEEE document explicitly says that a router SHOULD NOT learn multicast
MAC addresses for unicast IP addresses. Cisco is the only vendor that
sticks to that standard. On Cisco devices you have to add the MAC
manually. All other vendors just learn the MAC address.



Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein



signature.asc
Description: OpenPGP digital signature
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Summit

[Michael Schwartzkopff]

Am 15.02.19 um 21:16 schrieb digimer:
> If people are interested in coming to Canada, I might be able to work
> out some space here. I think a lot of people are in Europe, so I
> understand if it's preferred to host there again. If there is interest
> in host here though, please let me know. :)
>
> We should have the next generation Anvil! ready for demo by this fall,
> and it will be a pretty new take on HA, so we could do a presentation
> on that regardless of where it's held.
>
> Digi
>
> On 2019-02-15 1:42 p.m., Ken Gaillot wrote:
>> On Fri, 2019-02-15 at 16:24 +, Mark Syms wrote:
>>> Just been asked whether there were any plans for another Clusterlabs
>>> Summit as it will have been two years since the last one come
>>> September and at the moment it looks like the answer is no?
>> Plans, no -- but I have heard someone else bring up the possibility of
>> doing another one in Brno this year, so I'll look into it.
>>
>> Since we're bringing it up, what topics are people interested in
>> hearing about or presenting? (for the whole list to chime in)
> ___
> Users mailing list: Users@clusterlabs.org
> https://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


Hi,


I would like to take part again. I'd prefer the second half of September.


Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein




signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] MS MySQL resource not beeing promoted?

[Michael Schwartzkopff]

Hi,


I set up a mariadb on CentOS7 as master/slave-.

Manually the sync works.


when I confiure a ms resource in pacmaker, it comes up correctly on the
first glance.


"show master status" and "show slave status" in mysql works and shows
the correct status.


When I set the master node to standby, pacemaker promotes the database
server correctly, at least in the pacemaker status. BUT: "show master
status" on the now promoted server shows nothing. The database definitly
in NOT in the master state.

Setting the first node online again, pacemaker starts the database and
shows it as a slave. "show master status" in the database shows, that
the first node is master again.


So, the status in pacemaker does not agree to the real status of the
database.

Any ideas?

Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein




signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] Error in documentation of resource sets (collocation)?

[Michael Schwartzkopff]

Hi,


When I read the documentation of the colocating sets of of resources,
the last "note" section reads:


Pay close attention to the order in which resources and sets are listed.
While the colocation dependency for members of any one set is
last-to-first, the colocation dependency for multiple sets is
first-to-last. In the above example, B is colocated with A, but
colocated-set-1 is colocated with colocated-set-2.

But in the example above the config is:


    
    



So reading form last-to first inside the resource set would be "A" with
"B", which also correcpondens to the picture above. So the part "B is
colocated with A" seems to be wrong and should be "A is colocated with B"


Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein




signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] Antw: Re: Antw: Placing resource based on least load on a node

[Michael Schwartzkopff]

Am 20.11.18 um 08:57 schrieb Ulrich Windl:
>>>> Michael Schwartzkopff  schrieb am 20.11.2018 um 08:41 in 
>>>> Nachricht
> :
>> Am 20.11.18 um 08:35 schrieb Bernd:
>>> Am 2018-11-20 08:06, schrieb Ulrich Windl:
>>>>>>> Bernd  schrieb am 20.11.2018 um 07:21 in
>>>>>>> Nachricht
>>>> :
>>>>> Hi,
>>>>>
>>>>> I'd like to run a certain bunch of cronjobs from time to time on the
>>>>> cluster node (four node cluster) that has the lowest load of all four
>>>>> nodes.
>>>>>
>>>>> The parameters wanted for this system yet to build are
>>>>>
>>>>> * automatic placement on one of the four nodes (i.e., that with the
>>>>> lowest load)
>>>>>
>>>>> * in case a node fails, automatically removed from the cluster
>>>>>
>>>>> * it must only exist a single entity of the cronjob entity running
>>>>>
>>>>> so this really screams for pacemakter being used as foundation.
>>>>>
>>>>> However, I'm not sure how to implement the "put onto node with least
>>>>> load" part. I was thinking to use Node Attributes for that, but I
>>>>> didn't
>>>>> find any solution "out of the box" for this. Furthermore, as load is a
>>>>> highly volatile value, how can one make sure that all cronjobs are run
>>>>> to the end without being moved to a node that possibly meanwhile got a
>>>>> lower load than the one executing the jobs?
>>>> Hi!
>>>>
>>>> Actually I think the last one is the easiest (assuming the cron jobs
>>>> do not need any resources that are moved): Once a cron job is started,
>>>> it will run until it ends, whether it's crontab has been moved or not.
>>>>
>>>> Despite of that I think cluster software is not ideal when you
>>>> actually need load-balancing software.
>>>>
>>>> Regards,
>>>> Ulrich
>>> The only resource(s) existing would be the cron "runner".
>>>
>>> The point about load balancing is true, yes... so, any idea what to
>>> use instead? Is there already a tool or framework for solving a
>>> problem like this available or do I have to start from scratch? Not
>>> that I'd be too lazy, but what's the use of reinventing the wheel
>>> repeatedly...? ;)
>>>
>>> Regards,
>>>
>>> Bernd
>>> ___
>>> Users mailing list: Users@clusterlabs.org 
>>> https://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 
>>
>> hi,
>>
>>
>> I solved this problem years ago. I used the utilization attribute. But
>> you can use any attribute. You have to write an agent that measures the
>> CPU load every X minutes and updates the attribute.  Now you just have
>> to add a location constraint, that starts the resource on the node with
>> the "best" attribute value. The "best" could be lowest CPU usage or most
>> free RAM or whatever you want.
>>
>>
>> The disadvantage of this solution is that the cluster (i.e. pacemaker)
>> has to recalculate the scores every time you update your attribute. That
>> causes additional load. If you have many resources the interdepend that
>> additional load may be not negligible.
> Hi!
>
> Question on this: Is the cluster clever to check only updates of attributes 
> that some rule actually uses, or does it re-evaluate everything when any 
> attribute changed?
>
Everytime. That is what causes the load.





signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] Antw: Placing resource based on least load on a node

[Michael Schwartzkopff]

Am 20.11.18 um 08:35 schrieb Bernd:
> Am 2018-11-20 08:06, schrieb Ulrich Windl:
> Bernd  schrieb am 20.11.2018 um 07:21 in
> Nachricht
>> :
>>> Hi,
>>>
>>> I'd like to run a certain bunch of cronjobs from time to time on the
>>> cluster node (four node cluster) that has the lowest load of all four
>>> nodes.
>>>
>>> The parameters wanted for this system yet to build are
>>>
>>> * automatic placement on one of the four nodes (i.e., that with the
>>> lowest load)
>>>
>>> * in case a node fails, automatically removed from the cluster
>>>
>>> * it must only exist a single entity of the cronjob entity running
>>>
>>> so this really screams for pacemakter being used as foundation.
>>>
>>> However, I'm not sure how to implement the "put onto node with least
>>> load" part. I was thinking to use Node Attributes for that, but I
>>> didn't
>>> find any solution "out of the box" for this. Furthermore, as load is a
>>> highly volatile value, how can one make sure that all cronjobs are run
>>> to the end without being moved to a node that possibly meanwhile got a
>>> lower load than the one executing the jobs?
>>
>> Hi!
>>
>> Actually I think the last one is the easiest (assuming the cron jobs
>> do not need any resources that are moved): Once a cron job is started,
>> it will run until it ends, whether it's crontab has been moved or not.
>>
>> Despite of that I think cluster software is not ideal when you
>> actually need load-balancing software.
>>
>> Regards,
>> Ulrich
>
> The only resource(s) existing would be the cron "runner".
>
> The point about load balancing is true, yes... so, any idea what to
> use instead? Is there already a tool or framework for solving a
> problem like this available or do I have to start from scratch? Not
> that I'd be too lazy, but what's the use of reinventing the wheel
> repeatedly...? ;)
>
> Regards,
>
> Bernd
> ___
> Users mailing list: Users@clusterlabs.org
> https://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


See:


https://blog.sys4.de/making-resource-utilizations-dynamic-en.html

Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein




signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] Antw: Placing resource based on least load on a node

[Michael Schwartzkopff]

Am 20.11.18 um 08:35 schrieb Bernd:
> Am 2018-11-20 08:06, schrieb Ulrich Windl:
> Bernd  schrieb am 20.11.2018 um 07:21 in
> Nachricht
>> :
>>> Hi,
>>>
>>> I'd like to run a certain bunch of cronjobs from time to time on the
>>> cluster node (four node cluster) that has the lowest load of all four
>>> nodes.
>>>
>>> The parameters wanted for this system yet to build are
>>>
>>> * automatic placement on one of the four nodes (i.e., that with the
>>> lowest load)
>>>
>>> * in case a node fails, automatically removed from the cluster
>>>
>>> * it must only exist a single entity of the cronjob entity running
>>>
>>> so this really screams for pacemakter being used as foundation.
>>>
>>> However, I'm not sure how to implement the "put onto node with least
>>> load" part. I was thinking to use Node Attributes for that, but I
>>> didn't
>>> find any solution "out of the box" for this. Furthermore, as load is a
>>> highly volatile value, how can one make sure that all cronjobs are run
>>> to the end without being moved to a node that possibly meanwhile got a
>>> lower load than the one executing the jobs?
>>
>> Hi!
>>
>> Actually I think the last one is the easiest (assuming the cron jobs
>> do not need any resources that are moved): Once a cron job is started,
>> it will run until it ends, whether it's crontab has been moved or not.
>>
>> Despite of that I think cluster software is not ideal when you
>> actually need load-balancing software.
>>
>> Regards,
>> Ulrich
>
> The only resource(s) existing would be the cron "runner".
>
> The point about load balancing is true, yes... so, any idea what to
> use instead? Is there already a tool or framework for solving a
> problem like this available or do I have to start from scratch? Not
> that I'd be too lazy, but what's the use of reinventing the wheel
> repeatedly...? ;)
>
> Regards,
>
> Bernd
> ___
> Users mailing list: Users@clusterlabs.org
> https://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


hi,


I solved this problem years ago. I used the utilization attribute. But
you can use any attribute. You have to write an agent that measures the
CPU load every X minutes and updates the attribute.  Now you just have
to add a location constraint, that starts the resource on the node with
the "best" attribute value. The "best" could be lowest CPU usage or most
free RAM or whatever you want.


The disadvantage of this solution is that the cluster (i.e. pacemaker)
has to recalculate the scores every time you update your attribute. That
causes additional load. If you have many resources the interdepend that
additional load may be not negligible.


Greetings,


Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein




signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] ?==?utf-8?q? Limit of concurrent ressources to start?

[Michael Schwartzkopff]

Am 13.06.2018 um 16:18 schrieb Ken Gaillot:
> On Wed, 2018-06-13 at 14:25 +0200, Michael Schwartzkopff wrote:
>> On Wednesday, June 13, 2018 10:01 CEST, "Michael Schwartzkopff" > ys4.de> wrote: 
>>  
>>> Hi,
>>>
>>> we have a cluster with several IP addresses that can start after an
>>> other resource. In the logs we see that only 2 IP addresses start
>>> in parallel, not all. Can anyone please explain, why not all IP
>>> addresses start in parallel?
>>>
>>> Config:
>>> primitive resProc ocf:myprovider:Proc
>>> (ten times:) primitive resIP1 ocf:heartbeat:IPaddr2 params
>>> ip="192.168.100.1"
>>> order ord_Proc_IP Mandatory: resProc ( resIP1 resIP2 ... )
>>> collocation col_IP_Proc inf: (resIP1 resIP2 ...) resProc
>>>
>>> No batch-limit in properties.
>>> Any ideas? Thanks.
>>>
>>> Michael
> Each node has a limit of how many jobs it can execute in parallel. In
> order of most preferred to least, it will be:
>
> * The value of the (undocumented) PCMK_node_action_limit environment
> variable on that node (no limit if not existing)
>
> * The value of the (also undocumented) node-action-limit cluster
> property (defaulting to 0 meaning no limit)
>
> * Twice the node's number of CPU cores (as reported by /proc/stat)
>
> Also, the cluster will auto-calculate a cluster-wide batch-limit if
> high load is observed on any node.
>
> So, you could mostly override throttling by setting a high node-action-
> limit.
>
>> Hi,
>>
>> additional remark:
>>
>> With some tweaks I made my cluster start two resources (i.e. IP1 and
>> IP2) at the same time. But it takes about 4 seconds to that the
>> cluster starts the next resources (i.e. IP3 and IP4).
>>
>> Did anybody see this behaviour before?
>>
>> Why does my cluster do not start all "parallel" resources together?
>>
>> Michael.
> Ken Gaillot 

Thanks for this clarification.

Mit freundlichen Grüßen,

-- 

[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein




signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
https://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] ?==?utf-8?q? Limit of concurrent ressources to start?

[Michael Schwartzkopff]

On Wednesday, June 13, 2018 10:01 CEST, "Michael Schwartzkopff"  
wrote: 
 
> Hi,
> 
> we have a cluster with several IP addresses that can start after an other 
> resource. In the logs we see that only 2 IP addresses start in parallel, not 
> all. Can anyone please explain, why not all IP addresses start in parallel?
> 
> Config:
> primitive resProc ocf:myprovider:Proc
> (ten times:) primitive resIP1 ocf:heartbeat:IPaddr2 params ip="192.168.100.1"
> order ord_Proc_IP Mandatory: resProc ( resIP1 resIP2 ... )
> collocation col_IP_Proc inf: (resIP1 resIP2 ...) resProc
> 
> No batch-limit in properties.
> Any ideas? Thanks.
> 
> Michael

Hi,

additional remark:

With some tweaks I made my cluster start two resources (i.e. IP1 and IP2) at 
the same time. But it takes about 4 seconds to that the cluster starts the next 
resources (i.e. IP3 and IP4).

Did anybody see this behaviour before?

Why does my cluster do not start all "parallel" resources together?

Michael.

___
Users mailing list: Users@clusterlabs.org
https://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] Limit of concurrent ressources to start?

[Michael Schwartzkopff]

Hi,

we have a cluster with several IP addresses that can start after an other 
resource. In the logs we see that only 2 IP addresses start in parallel, not 
all. Can anyone please explain, why not all IP addresses start in parallel?

Config:
primitive resProc ocf:myprovider:Proc
(ten times:) primitive resIP1 ocf:heartbeat:IPaddr2 params ip="192.168.100.1"
order ord_Proc_IP Mandatory: resProc ( resIP1 resIP2 ... )
collocation col_IP_Proc inf: (resIP1 resIP2 ...) resProc

No batch-limit in properties.
Any ideas? Thanks.

Michael

___
Users mailing list: Users@clusterlabs.org
https://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] [ClusterLabs Developers] HA/Clusterlabs Summit 2017 Proposal

[Michael Schwartzkopff]

Am Dienstag, 31. Januar 2017, 21:09:24 schrieb Digimer:
> On 31/01/17 06:38 PM, Chris Feist wrote:
> > On Mon, Jan 30, 2017 at 8:23 AM, Kristoffer Grönlund <kgronl...@suse.com
> > 
> > <mailto:kgronl...@suse.com>> wrote:
> > Hi everyone!
> > 
> > The last time we had an HA summit was in 2015, and the intention then
> > was to have SUSE arrange the next meetup in the following year. We did
> > try to find a date that would be suitable for everyone, but for
> > various
> > reasons there was never a conclusion and 2016 came and went.
> > 
> > Well, I'd like to give it another try this year! This time, I've
> > already
> > got a proposal for a place and date: September 7-8 in Nuremberg,
> > Germany
> > (SUSE main office). I've got the new event area in the SUSE office
> > already reserved for these dates.
> > 
> > My suggestion is to do a two day event similar to the one in Brno, but
> > I
> > am open to any suggestions as to format and content. The main reason
> > for
> > having the event would be for everyone to have a chance to meet and
> > get
> > to know each other, but it's also an opportunity to discuss the future
> > of Clusterlabs and the direction going forward.
> > 
> > Any thoughts or feedback are more than welcome! Let me know if you are
> > interested in coming or unable to make it.
> > 
> > Kristoffer,
> > 
> > Thank you for getting some dates and providing a space for the summit.
> > I know myself and several cluster engineers from Red Hat are definitely
> > interested in attending.  The only thing that I might recommend is
> > moving the conference one day earlier (change to Wed/Thu instead of
> > Thu/Fri) to make it easier for people traveling to/from the conference.
> > 
> > Thanks!
> > Chris
> 
> I'd like to propose an informal sight seeing outing for the following
> weekend, whether it be held Wed/Thu or Thu/Fri. The last few times I've
> been to Europe, I afforded myself little to no time to see any sights. I
> don't plan to rush out this time, and would love to have some friendly
> company. :)

hi,

the idea of a new cluster meeting is great. I'd like to participate. But the 
date 6./7. Sept is not optimal . It is school holidays in Bavaria and the best 
time of the year to go to the mountains with the kids.

So I'd prefer perhaps a week later or an other time.


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Schleißheimer Straße 26/MG, 80333 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] Running several instances of a Corosync/Pacemaker cluster on a node

[Michael Schwartzkopff]

Am Dienstag, 26. April 2016, 10:33:00 schrieb Bogdan Dobrelya:
> Is it possible to run several instances of a Corosync/Pacemaker clusters
> on a node? Can a node be a member of several clusters, so they could put
> resources there? I'm sure it's doable with separate nodes or containers,
> but that's not the case.
> 
> My case is to separate data-critical resources, like storage or VIPs,
> from the complex resources like DB or MQ clusters.
> 
> The latter should run with no-quorum-policy=ignore as they know how to
> deal with network partitions/split-brain, use own techniques to protect
> data and don't want external fencing from a Pacemaker, which
> no-quorum-policy/STONITH is.
> 
> The former must use STONITH (or a stop policy, if it's only a VIP), as
> they don't know how to deal with split-brain, for example.

that is not possible. corosync and pacemaker are not able to run as multi-
tennen.

Use docker or plain linux partitions (lxc).

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] Antw: Regarding IP tables and IP Address clone

[Michael Schwartzkopff]

Am Mittwoch, 23. Dezember 2015, 12:28:06 schrieb Ulrich Windl:
> >>> Somanath Jeeva <somanath.je...@ericsson.com> schrieb am 23.12.2015 um
> >>> 06:01 in
> Nachricht <4f5e5141ed95ff45b3128f3c7b1b2a6721abe...@eusaamb109.ericsson.se>:
> > Hi ,
> > 
> > Thanks for the quick reply.
> > 
> > I will check with our IT team regarding the multicast MAC at switch level.
> > 
> > But the Virtual IP is reachable for 15 minutes or so after I start the
> > pacemaker/Corosync service. After which it becomes unreachable. However
> > when I restart the iptables service it becomes reachable again for
> > another 15 min.
> It could be some ARP cache problem. Maybe watch it.

Please check the ARP tables of your switches / routers. IP address clones use 
multicast MAC addresses for the unicast IP address. Some switches (esp Cisco) 
do not like that. You would have to configure the MAC addresses manually.

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] Regarding IP tables and IP Address clone

[Michael Schwartzkopff]

Am Mittwoch, 23. Dezember 2015, 19:17:25 schrieb Somanaththilak jeeva:
> > Am Mittwoch, 23. Dezember 2015, 12:28:06 schrieb Ulrich Windl:
> >* >>> Somanath Jeeva  ><http://clusterlabs.org/mailman/listinfo/users>> schrieb am 23.12.2015 um*
> >
> >* >>> 06:01 in*
> >
> >* Nachricht <4F5E5141ED95FF45B3128F3C7B1B2A6721ABE07B at
> >eusaamb109.ericsson.se <http://clusterlabs.org/mailman/listinfo/users>>:*
> >
> >* > Hi ,*
> >
> >* > *
> >
> >* > Thanks for the quick reply.*
> >
> >* > *
> >
> >* > I will check with our IT team regarding the multicast MAC at switch
> >level.*
> >
> >* > *
> >
> >* > But the Virtual IP is reachable for 15 minutes or so after I start the*
> >
> >* > pacemaker/Corosync service. After which it becomes unreachable.
> >However*
> >
> >* > when I restart the iptables service it becomes reachable again for*
> >
> >* > another 15 min.*
> >
> >* It could be some ARP cache problem. Maybe watch it.*
> >
> > Please check the ARP tables of your switches / routers. IP address clones
> > use
> > 
> > multicast MAC addresses for the unicast IP address. Some switches (esp
> > Cisco)
> > 
> > do not like that. You would have to configure the MAC addresses manually.
> 
> Do I have to configure this MAC address manually at switch level?. The
> Multicast MAC was automatically added in the iptables after started
> the pacemaker/Corosync service.

Please check the ARP tables of your switches / routers. IP address clones
use multicast MAC addresses for the unicast IP address. Some switches (esp
Cisco) do not like that. You would have to configure the MAC addresses 
manually.

Please do as advertised.

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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

[ClusterLabs] Multisite Clusters: how many servers?

[Michael Schwartzkopff]

Hi,

it is possible / advisable to set up a multisite cluster with booth with one 
server at each site?

So having three servers all together?

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] Loadbalancing using Pacemaker

[Michael Schwartzkopff]

Am Samstag, 7. November 2015, 09:40:47 schrieb didier tanti:
> Hello, i am new to Pacemaker and have a question concerning how to have my
> cluster services aware of the state and location of the other services in
> the cluster.  Example:
> Service A is running on Host XService B1 is running on Host XService B2 is
> running on Host Y Which API would allow my Service A to send IPC messages
> to services B1 and B2 in a round robin manner?(for example how Service A
> would be aware of which B is up and active (B1, B2 or both), and how A
> would even be able to know on which host B1 or B2 is running?) It looks
> very basic but i cannot find information on this on clusterlabs.org Is
> there basic tutorial that would explain how to achieve this ? (I guess i
> would need to link my service binaries with some pacemaker /corosync libs
> and use some API ?) Thanks for helping out,

Hi,

this task is beyond the ability of pacemaker. Your application has to know how 
to handle that.

Best solution would be to use virtual IP addresses for services B1 and B2. 
make sure that the IP addresses run together with the services. Now you 
service A only has to talk to the IP addresses, no matter on which host they 
run.

pacemaker could take care that they run on different hosts is possible.

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] Cluster monitoring

[Michael Schwartzkopff]

Am Mittwoch, 21. Oktober 2015, 18:50:15 schrieb Arjun Pandey:
> Hi folks
> 
> I had a question on monitoring of cluster events. Based on the
> documentation it seems that cluster monitor is the only method of
> monitoring the cluster events. Also since it seems to poll based on the
> interval configured it might miss some events. Is that the case ?

No. the cluser is event-based. So it won't miss any event. If you use the 
cluster's tools, they see hte events. If you monitor the events you won't miss 
any either.
 

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] difference between OCF return codes for monitor action

[Michael Schwartzkopff]

Am Mittwoch, 21. Oktober 2015, 15:44:17 schrieb Kostiantyn Ponomarenko:
> Hi,
> 
> What is the difference between "OCF_ERR_GENERIC" and "OCF_NOT_RUNNING"
> return codes in "monitor" action from the Pacemaker's point of view?
> 
> I was looking here
> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-oc
> f-return-codes.html , but I still don't see the difference clearly.
> 
> Thank you,
> Kostya

No differences from pacemaker point of view. Both are errors and pacemaker acts 
as configured. The return codes are for the admin to make it easier to find the 
cause.

Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] Pacemaker: Custom Health Checks possible?

[Michael Schwartzkopff]

Am Mittwoch, 23. September 2015, 14:10:52 schrieb Sebish:
> Dear all on clusterlabs mailing list,
> 
> there remains a question, even google could not deliver the answer for:
> 
>   * *Does Pacemaker + Heartbeat 2 / Corosync  (/openAIS) provide the
> possibility to use custom health checks?*

Yes.

>   * *Which part of the constellation must it be added to?*

Add your health check as a normal resource.

> Especially I need to be able to integrate a health check for a SIP Proxy
> (Kamailio) and perhaps openHAB.

Stop. That sounds like a monitoring task of a resource. You have to add this 
checks to the monitoring part of the SIP Proxy and / or openHA.


> SIP: Trying to establish call, getting ACK (or correct answer) back ->
> Check okay || No or false answer -> Check failed.

Basically:
Health checks are for testing the health or a cluster node, i.e. CPU load, 
free space on a partition or something like that.
If you want to check a resource (application) then you have to improve the 
monitoring function of the according Resource Agent.


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] a newbie --question

[Michael Schwartzkopff]

Am Dienstag, 15. September 2015, 13:38:59 schrieb H Yavari‬:
> Hi,
> Thanks for reply.
> The problem is Compute resource, the appY and appZ can't run on same Server.
> It is possible ?
> Regards,

As far as I understood:

You have the applications Y and Z and the servers A, B, C and D.

The applications Y and Z cannot run on the same node.



Solution1:
Make two clusters M (from node A and B) and Cluster N (from nodes C and D). 
Cluster M runs the application Y and Cluster N run the application Z.

Solution 2:
Make one big cluster from all four nodes and configure constraints that the 
applications will not run on the same node. Side note: Basically you only need 
three nodes in this scenario:
- application Y running on node A
- application Z running on node B
- in case of a failure of A or B the cluster starts the failed application on 
node C


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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] a newbie --question

[Michael Schwartzkopff]

Am Dienstag, 15. September 2015, 13:57:36 schrieb H Yavari‬:
> Hi,
> Thanks a lot. But can you give me some hints about configuration?

http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
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