On 25/07/2013, at 9:22 PM, Jacobo García <jacobo.gar...@gmail.com> wrote:
> Hello, > > As suggested I'm trying to add the nodes via corosync-objctl. > > My current config file is this one: > https://gist.github.com/therobot/4327cd0a2598d1d6bb93 using 5001 as the > nodeid on the second node. > > Then I try to add the nodes with the following commands: > > corosync-objctl -n totem.interface.member.memberaddr=10.34.191.212 > corosync-objctl -n runtime.totem.pg.mrp.srp.members.5001.join_count=1 > corosync-objctl -n runtime.totem.pg.mrp.srp.members.5000.status=joined > corosync-objctl -n untime.totem.pg.mrp.srp.members.5001.ip=r(0) > ip(10.34.191.212) > > > (I have a problem because the space between r(0) and ip is not respected by > corosync-objctl) > > Am I on the right track? Sounds plausible. Perhaps check out the code for pcs (on github) and see what Chris does > Should I abandon my quest to have an HA solution on EC2 public network? > > Thanks, > > > > Jacobo García López de Araujo > http://thebourbaki.com | http://twitter.com/clapkent > > > On Wed, Jul 24, 2013 at 2:43 PM, Andrew Beekhof <and...@beekhof.net> wrote: > > On 24/07/2013, at 10:09 PM, Lars Marowsky-Bree <l...@suse.com> wrote: > > > On 2013-07-24T21:40:40, Andrew Beekhof <and...@beekhof.net> wrote: > > > >>> Statically assigned nodeids? > >> Wouldn't hurt, but you still need to bring down the still-active node to > >> get it to talk to the new node. > >> Which sucks > > > > Hm. But ... corosync/pacemaker ought to identify the node via the > > nodeid. If it comes back with a different IP address, that shouldn't be > > a problem. > > > > Oh. *thud* Just realized that it's bound to be one for unicast > > communications, not so much mcast. > > Exactly. > > > Seems we may need some corosync magic > > commands to edit the nodelist at runtime. (Or is that already possible > > and I just don't know how? ;-) > > I believe it might be possible - I just don't know it. > Might even be better to have it happen automagically - after-all the new node > knows the existing node's address. > > But good luck getting that one through. > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
