Hi Andrew, not big effort, as I usually address lots of little HA clusters in a HPC cluster, so most of modifications are scripted and performed from a central node .
I agree that this way of change must be exceptional , but in certain cases it would have be useful for me. Just an example that cames to my mind : when Pacemaker has been stopped on all nodes with all resources Started, and for any reason you want to start Pacemaker but being sure that none of the resources will start , you could set all target-role to Stopped before launching Pacemaker. That 's an example among some others. And another example would be to set a first configuration before the first start of Pacemaker, just by putting a cib.xml file in place, with all resources configured in the file. But I'm not sure that this case will work with the rm -f *.sig because there are not yet any .sig file as Pacemaker has never been started yet, so ... I'm quite sure it is not possible to pre-configure all things before starting Pacemaker (just like with the RH Cluster Suite where you can put in place a pre-configured cluster.conf with all infos/resources inside and then start the CS) Alain De : Andrew Beekhof <and...@beekhof.net> A : General Linux-HA mailing list <linux-ha@lists.linux-ha.org> Date : 21/06/2012 03:56 Objet : Re: [Linux-HA] I need to edit my cib.xml manually Envoyé par : linux-ha-boun...@lists.linux-ha.org On Wed, Jun 20, 2012 at 8:48 PM, <alain.mou...@bull.net> wrote: > Hi Andrew, > > my try was this one : > 1/stop pacemaker on all nodes > 2/remove all .sig on both nodes > 3/remove the cib.xml on all nodes except one > 4/modify one parameter in the remaining cib.xml That seems like a lot of effort. What was the parameter and why not modify it before the cluster was shutdown or after it came back up? > 5/and then start again Pacemaker on all nodes > and it seems to work fine. > (but for now, I test with a two-nodes cluster only) > > Alain > > > > De : Andrew Beekhof <and...@beekhof.net> > A : General Linux-HA mailing list <linux-ha@lists.linux-ha.org> > Date : 20/06/2012 11:58 > Objet : Re: [Linux-HA] I need to edit my cib.xml manually > Envoyé par : linux-ha-boun...@lists.linux-ha.org > > > > On Wed, Jun 20, 2012 at 7:21 PM, <alain.mou...@bull.net> wrote: >> Effectively, it seems to work fine to remove all .sig, modify cib.xml > and >> start again Pacemaker ! That's really new for me who has looked, one > year >> ago, for >> a way to configure Pacemaker from scratch, without starting it, and also >> in certain cases patch the configuration of Pacemaker before starting it >> ... >> Could someone from Pacemaker team confirm that it should work in >> any cases ? even if there is a risk to do such manual patch out of crm > api >> which checks before apply ... but in certain cases, it could be very > very >> useful, if we are sure it always work. > > It will always work, but it is not encouraged because you need to do > it on every node. > cibadmin --erase (or the shell equivalent) ensures the version number > is correctly bumped. > >> >> Thanks >> Alain >> >> >> >> De : mike <mgbut...@nbnet.nb.ca> >> A : General Linux-HA mailing list <linux-ha@lists.linux-ha.org> >> Date : 19/06/2012 19:15 >> Objet : Re: [Linux-HA] I need to edit my cib.xml manually >> Envoyé par : linux-ha-boun...@lists.linux-ha.org >> >> >> >> Ends up that simply deleting cib.xml.sig and editing cib.xml works fine. >> HA fired right up with the new IPs. >> >> >> On 12-06-19 11:40 AM, Dan Frincu wrote: >>> Hi, >>> >>> On Tue, Jun 19, 2012 at 5:16 PM, mike<mgbut...@nbnet.nb.ca> wrote: >>>> Thanks Dan but I think the cluster has to be up and running to do a >> load >>>> replace doesn't it? Maybe if I create a bogus empty cib configuration >>>> first? Perhaps then I could fire it up and replace it. >>> Up and running would mean in this case that your communication layer >>> is working (Heartbeat/Corosync) and Pacemaker is started. At best the >>> configuration would hold the nodes' information about each other. >>> That's when you can jump in with the crm configure load replace. >>> >>> There's also a cibadmin --md5-sum, maybe in your case this would work >> better. >>> >>> HTH, >>> Dan >>> >>>> >>>> On 12-06-19 10:41 AM, Dan Frincu wrote: >>>>> Hi, >>>>> >>>>> On Tue, Jun 19, 2012 at 4:31 PM, mike<mgbut...@nbnet.nb.ca> wrote: >>>>>> We're setting up a DR type of situation where we have restored our > HA >>>>>> servers and MySQL successfully. Typically I would fire up HA, use >>>>>> cibadmin to dump the cib to a temp file and then change the VIP to >> the >>>>>> one on the DR site. Here's the problem though. The two networks are >> able >>>>>> to talk to one another (a mistake by network folks - can't be >> corrected >>>>>> now) and so I cannot start HA because it will cause a problem with >>>>>> production. I have read that you cannot edit the cib.xml directly > but >>>>>> was wondering how true that is. All I need to do is change the one >> VIP >>>>>> in the configuration file and start HA. What are the ramifications > of >>>>>> editing it by hand and will HA allow me to do that? >>>>> How about crm configure save file.crm then edit file.crm then crm > load >>>>> replace file.crm on the other side? >>>>> >>>>> HTH, >>>>> Dan >>>>>> Thanks >>>>>> -mike >>>>>> >>>>>> _______________________________________________ >>>>>> Linux-HA mailing list >>>>>> Linux-HA@lists.linux-ha.org >>>>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha >>>>>> See also: http://linux-ha.org/ReportingProblems >>>>> >>>> _______________________________________________ >>>> Linux-HA mailing list >>>> Linux-HA@lists.linux-ha.org >>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha >>>> See also: http://linux-ha.org/ReportingProblems >>> >>> >> >> _______________________________________________ >> Linux-HA mailing list >> Linux-HA@lists.linux-ha.org >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> >> _______________________________________________ >> Linux-HA mailing list >> Linux-HA@lists.linux-ha.org >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
