On Fri, Jun 08, 2012 at 03:47:56PM -0700, Matteo Bignotti wrote:
> No the nodes it's ok, shouldn't delete them.
>
> but to use the crm configure erase I would need to stop any resource
> that's running, correct?
Correct. And there's a good reason to enforce that.
> what is better? is the cibadm
No the nodes it's ok, shouldn't delete them.
but to use the crm configure erase I would need to stop any resource
that's running, correct?
what is better? is the cibadmin too invasive?
On 06/08/2012 03:05 AM, Dejan Muhamedagic wrote:
Hi,
On Thu, Jun 07, 2012 at 12:01:16PM -0700, Matteo Bign
Hi,
On Thu, Jun 07, 2012 at 12:01:16PM -0700, Matteo Bignotti wrote:
> Hi guys,
>
> I'm trying to configure in batch pacemaker, so far what I am doing
> in orders is
>
> # Flushing the old configuration
> cibadmin -E --force
You should use crm configure erase for this. Note that it
doesn't dele
Hi guys,
I'm trying to configure in batch pacemaker, so far what I am doing in
orders is
# Flushing the old configuration
cibadmin -E --force
#reloading the new one
crm configure load replace [filename]
and then restarting the machine
now, I find it kinda hard to believe that the only batch
