[Pacemaker] Batch pacemaker configuration

[Dejan Muhamedagic]

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 cibadmin too invasive?

crm uses cibadmin in the background, but it is easier on users.

Thanks,

Dejan

> On 06/08/2012 03:05 AM, Dejan Muhamedagic wrote:
>> 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 delete nodes (nodes are somewhat special).
>>
>>> #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 command to
>>> refresh the configuration needs to be forced.
>> There should be a reason, doesn't it mention why?
>>
>>> Also, is there any
>>> other way to load a configuration file? (non xml) because the crm
>>> configure sometimes prompts me for a question, which would be always
>>> "Y" but I can't find anywhere in the documentation how to set an
>>> auto "yes" in the command line.
>> Just use -F (force).
>>
>> Thanks,
>>
>> Dejan
>>
>>> thank you guys
>>>
>>> Matteo
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at 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 at 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 at 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
> 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 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 delete nodes (nodes are somewhat special).
>>
>>> #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 command to
>>> refresh the configuration needs to be forced.
>> There should be a reason, doesn't it mention why?
>>
>>> Also, is there any
>>> other way to load a configuration file? (non xml) because the crm
>>> configure sometimes prompts me for a question, which would be always
>>> "Y" but I can't find anywhere in the documentation how to set an
>>> auto "yes" in the command line.
>> Just use -F (force).
>>
>> Thanks,
>>
>> Dejan
>>
>>> thank you guys
>>>
>>> Matteo
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker at 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 at 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 at 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