[ClusterLabs] Minimum configuration for dynamically adding a node to a cluster

[Nikhil Utane]

OK. The reason I got confused is coz all tutorials have prior step as
creating user hacluster and then using pcs commands. Hence i thought it
relies on ssh. Thanks for the clarification.

On Wed, Jun 8, 2016 at 7:51 PM, Ken Gaillot <kgaillot at redhat.com> wrote:

> On 06/08/2016 06:54 AM, Jehan-Guillaume de Rorthais wrote:
> >
> >
> > Le 8 juin 2016 13:36:03 GMT+02:00, Nikhil Utane <
> nikhil.subscribed at gmail.com> a écrit :
> >> Hi,
> >>
> >> Would like to know the best and easiest way to add a new node to an
> >> already
> >> running cluster.
> >>
> >> Our limitation:
> >> 1) pcsd cannot be used since (as per my understanding) it communicates
> >> over
> >> ssh which is prevented.
> >
> > As far as i remember,  pcsd deamons use their own tcp port (not the ssh
> one) and communicate with each others using http queries (over ssl i
> suppose).
>
> Correct, pcsd uses port 2224. It encrypts all traffic. If you can get
> that allowed through your firewall between cluster nodes, that will be
> the easiest way.
>
> corosync.conf does need to be kept the same on all nodes, and corosync
> needs to be reloaded after any changes. pcs will handle this
> automatically when adding/removing nodes. Alternatively, it is possible
> to use corosync.conf with multicast, without explicitly listing
> individual nodes.
>
> > As far as i understand, crmsh uses ssh, not pcsd.
>
> _______________________________________________
> Users mailing list: Users at 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160609/8a0d37f8/attachment-0003.html>