date:20190509

Re: [ClusterLabs] Re: Fencing questions

2019-05-09 Thread Lopez, Francisco Javier [Global IT]

Thx Klaus, appreciate your feedback.

Regards
Javier

Francisco Javier   Lopez

IT System Engineer   |  Global IT

O: +34 619 728 249|  M: +34 619 728 
249|

franciscojavier.lo...@solera.com   
 |  Solera.com

Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida 16, A‑1 
(Diversia),   Alcobendas  ,   Madrid  ,   28108   , 
  Spain


[cid:image339311.png@D1525B14.71452121]



On 5/9/2019 1:14 PM, Klaus Wenninger wrote:

On 5/9/19 1:03 PM, Lopez, Francisco Javier [Global IT] wrote:


Good day guys !

I'm implementing fencing in my two node cluster with this detail:

- fence_vmware_soap
- PostgreSql release 10.X
- CentOS 7.X

As far as I know, to create the resources, I can use two different ways:

- Create only one resource for both nodes, following this way:

  # pcs -f stonith_cfg stonith create fence_nodes \
  fence_vmware_soap \
  ipaddr= \
  ssl_insecure=1 \
  login="" \
  passwd="" \
  action=reboot \
  pcmk_host_list="node_01,node_02" \
  power_wait=3 op monitor interval=60s

- Create two different resources, one for each node, following this way:

  # pcs -f stonith_cfg stonith create fence_node_01 \
  fence_vmware_soap  \
  ipaddr= \
  ssl_insecure=1 \
  login="" \
  passwd="" \
  action=reboot \
  pcmk_host_list="node_01" \
  power_wait=3 op monitor interval=60s

  # pcs -f stonith_cfg stonith create fence_node_02 \
  fence_vmware_soap  \
  ipaddr= \
  ssl_insecure=1 \
  login="" \
  passwd="" \
  action=reboot \
  pcmk_host_list="node_02" \
  power_wait=3 op monitor interval=60s

  With this method I understand I will have to add some constraints, etc.

Said this, my questions are:

- Which are the differences among them ? (if any).
- Is there any recommended option and why ?


For your 2-node-cluster there might be a definite reason why you'd
like to have 2 fence-resources as to prevent fence-races when both
are still alive but just don't see each other. If you make one
wait a little longer to fence you can determine which one would
rather win.
If the aim is just to prevent that they fence each other at the same
time introduction of a random delay should be fine as well.
(That is pcmk_delay_max and if you want to further tailor the delay
with astatic delay component you can use pcmk_delay_base on top.)

Klaus



Regards
Javier
Francisco Javier   Lopez

IT System Engineer   |  Global IT

O: *+34 619 728 249*  
 |
M: *+34 619 728 249*  
 |
*franciscojavier.lo...@solera.com*

   |  *Solera.com*


Audatex Datos, S.A.  |
Avda. de Bruselas, 36, Salida 16, A‑1 (Diversia),   Alcobendas  
,
Madrid  ,   28108   ,   Spain






" Este e-mail y sus archivos adjuntos son confidenciales y están
dirigidos exclusivamente a la(s) persona(s) destinataria prevista. Si
ha recibido este mensaje por error, por favor, notifique
inmediatamente al remitente y elimine este mensaje. La empresa no
firma contratos por e-mail y todas las negociaciones están sujetas a
la firma de un contrato por escrito.

This e-mail and any attached files are confidential and intended for
the named addressee(s) only. If you have received this message in
error, please notify the sender and delete the email immediately. The
company does not conclude contracts by email and all negotiations are
subject to written contract. "

___
Manage your subscription:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.clusterlabs.org%2Fmailman%2Flistinfo%2Fusers&data=01%7C01%7C%7C201d67c0bdaf4291190008d6d46f8b8e%7Cc45b48f313bb448b9356ba7b863c2189%7C1&sdata=Hgno43Tl4vCx5AEIwoZkT6Xq2AhzpKoaiQ9n%2FWcjGcQ%3D&reserved=0

ClusterLabs home: 
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.clusterlabs.org%2F&data=01%7C01%7C%7C201d67c0bdaf4291190008d6d46f8b8e%7Cc45b48f313bb448b9356ba7b863c2189%7C1&sdata=cCoTTaMC8MnieDaur7KPQSKHlGKBaeWMM6kRu6SOzE4%3D&reserved=0



___
Manage your subscription:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.clusterlabs.org%2Fmailman%2Flistinfo%2Fusers&data=01%7C01%7C%7C201d67c0bdaf4291190008d6d46f8b8e%7Cc45b48f313bb448b9356ba7b863c2189

Re: [ClusterLabs] Fencing questions

2019-05-09 Thread Klaus Wenninger

On 5/9/19 1:03 PM, Lopez, Francisco Javier [Global IT] wrote:
> Good day guys !
>
> I'm implementing fencing in my two node cluster with this detail:
>
> - fence_vmware_soap
> - PostgreSql release 10.X
> - CentOS 7.X
>
> As far as I know, to create the resources, I can use two different ways:
>
> - Create only one resource for both nodes, following this way:
>
>   # pcs -f stonith_cfg stonith create fence_nodes \
>   fence_vmware_soap \
>   ipaddr= \
>   ssl_insecure=1 \
>   login="" \
>   passwd="" \
>   action=reboot \
>   pcmk_host_list="node_01,node_02" \
>   power_wait=3 op monitor interval=60s
>
> - Create two different resources, one for each node, following this way:
>
>   # pcs -f stonith_cfg stonith create fence_node_01 \
>   fence_vmware_soap  \
>   ipaddr= \
>   ssl_insecure=1 \
>   login="" \
>   passwd="" \
>   action=reboot \
>   pcmk_host_list="node_01" \
>   power_wait=3 op monitor interval=60s
>
>   # pcs -f stonith_cfg stonith create fence_node_02 \
>   fence_vmware_soap  \
>   ipaddr= \
>   ssl_insecure=1 \
>   login="" \
>   passwd="" \
>   action=reboot \
>   pcmk_host_list="node_02" \
>   power_wait=3 op monitor interval=60s
>
>   With this method I understand I will have to add some constraints, etc.
>
> Said this, my questions are:
>
> - Which are the differences among them ? (if any).
> - Is there any recommended option and why ?
For your 2-node-cluster there might be a definite reason why you'd
like to have 2 fence-resources as to prevent fence-races when both
are still alive but just don't see each other. If you make one
wait a little longer to fence you can determine which one would
rather win.
If the aim is just to prevent that they fence each other at the same
time introduction of a random delay should be fine as well.
(That is pcmk_delay_max and if you want to further tailor the delay
with astatic delay component you can use pcmk_delay_base on top.)

Klaus
>
> Regards
> Javier
> Francisco Javier     Lopez
>
> IT System Engineer |  Global IT
>
> O: *+34 619 728 249*    | 
> M: *+34 619 728 249*    | 
>   *franciscojavier.lo...@solera.com*
>   |  *Solera.com*
> 
>
> Audatex Datos, S.A.    | 
> Avda. de Bruselas, 36, Salida 16, A‑1 (Diversia)  ,   Alcobendas  
> , 
> Madrid,   28108   ,   Spain
>
>  
>
>
> 
>
> " Este e-mail y sus archivos adjuntos son confidenciales y están
> dirigidos exclusivamente a la(s) persona(s) destinataria prevista. Si
> ha recibido este mensaje por error, por favor, notifique
> inmediatamente al remitente y elimine este mensaje. La empresa no
> firma contratos por e-mail y todas las negociaciones están sujetas a
> la firma de un contrato por escrito.
>
> This e-mail and any attached files are confidential and intended for
> the named addressee(s) only. If you have received this message in
> error, please notify the sender and delete the email immediately. The
> company does not conclude contracts by email and all negotiations are
> subject to written contract. "
>
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/

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

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

[ClusterLabs] Fencing questions

2019-05-09 Thread Lopez, Francisco Javier [Global IT]

Good day guys !

I'm implementing fencing in my two node cluster with this detail:

- fence_vmware_soap
- PostgreSql release 10.X
- CentOS 7.X

As far as I know, to create the resources, I can use two different ways:

- Create only one resource for both nodes, following this way:

  # pcs -f stonith_cfg stonith create fence_nodes \
  fence_vmware_soap \
  ipaddr= \
  ssl_insecure=1 \
  login="" \
  passwd="" \
  action=reboot \
  pcmk_host_list="node_01,node_02" \
  power_wait=3 op monitor interval=60s

- Create two different resources, one for each node, following this way:

  # pcs -f stonith_cfg stonith create fence_node_01 \
  fence_vmware_soap  \
  ipaddr= \
  ssl_insecure=1 \
  login="" \
  passwd="" \
  action=reboot \
  pcmk_host_list="node_01" \
  power_wait=3 op monitor interval=60s

  # pcs -f stonith_cfg stonith create fence_node_02 \
  fence_vmware_soap  \
  ipaddr= \
  ssl_insecure=1 \
  login="" \
  passwd="" \
  action=reboot \
  pcmk_host_list="node_02" \
  power_wait=3 op monitor interval=60s

  With this method I understand I will have to add some constraints, etc.

Said this, my questions are:

- Which are the differences among them ? (if any).
- Is there any recommended option and why ?

Regards
Javier
Francisco Javier   Lopez

IT System Engineer   |  Global IT

O: +34 619 728 249|  M: +34 619 728 
249|

franciscojavier.lo...@solera.com   
 |  Solera.com

Audatex Datos, S.A.  |  Avda. de Bruselas, 36, Salida 16, A‑1 
(Diversia),   Alcobendas  ,   Madrid  ,   28108   , 
  Spain


[cid:image660500.png@443BEB68.0955AF5D]






" Este e-mail y sus archivos adjuntos son confidenciales y están dirigidos 
exclusivamente a la(s) persona(s) destinataria prevista. Si ha recibido este 
mensaje por error, por favor, notifique inmediatamente al remitente y elimine 
este mensaje. La empresa no firma contratos por e-mail y todas las 
negociaciones están sujetas a la firma de un contrato por escrito.

This e-mail and any attached files are confidential and intended for the named 
addressee(s) only. If you have received this message in error, please notify 
the sender and delete the email immediately. The company does not conclude 
contracts by email and all negotiations are subject to written contract. "
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

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

[ClusterLabs] kronosnet v1.9 released

2019-05-09 Thread Fabio M. Di Nitto


All,

We are pleased to announce the general availability of kronosnet v1.9

kronosnet (or knet for short) is the new underlying network protocol for 
Linux HA components (corosync), that features ability to use multiple 
links between nodes, active/active and active/passive link failover 
policies, automatic link recovery, FIPS compliant encryption (nss and/or 
openssl), automatic PMTUd and in general better performances compared to 
the old network protocol.


Highlights in this release:

* Reduce minimum crypto key size requirement to 1024bit
* Drop libnss 3des support
* Lots of man pages improvements and cleanup
* Improved UDP error reporting from ICMP error messages

Known issues in this release:

* none

The source tarballs can be downloaded here:

https://www.kronosnet.org/releases/

Upstream resources and contacts:

https://kronosnet.org/
https://github.com/kronosnet/kronosnet/
https://ci.kronosnet.org/
https://trello.com/kronosnet (TODO list and activities tracking)
https://goo.gl/9ZvkLS (google shared drive with presentations and diagrams)
IRC: #kronosnet on Freenode
https://lists.kronosnet.org/mailman/listinfo/users
https://lists.kronosnet.org/mailman/listinfo/devel
https://lists.kronosnet.org/mailman/listinfo/commits

Cheers,
The knet developer team
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

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

Re: [ClusterLabs] Re: Fencing questions

Re: [ClusterLabs] Fencing questions

[ClusterLabs] Fencing questions

[ClusterLabs] kronosnet v1.9 released

4 matches

Site Navigation

Mail list logo

Footer information