On 05/15/2013 04:07 AM, Dejan Muhamedagic wrote:
> Hi Alan,
>
> On Tue, May 14, 2013 at 07:52:30PM -0600, Alan Robertson wrote:
>> It's best if we understand how to model their configurability.
>>
>> For example, in the OCF RA APIs, there is an action called meta-data
>> which spits out an XML snippet describing how to configure them (what
>> parameters, etc). It's not hard to write an OCF resource agent (in
>> spite of the XML), but it _is_ non-zero work to write and to debug them.
> There is an extension to pacemaker available with the latest
> SLE11SP3 (also upstream since v1.1.8 or v1.1.9, I think) which
> allows use of nagios agents with an OCF RA configuration. Right
> now, the meta-data is just a file on the disk which has been
> semi-automatically created for several agents. The nagios upstream
> didn't want the patches that would enable agents to produce OCF RA
> XML meta-data. See:
I was assuming we'd have to do something similar. Is there any
documentation on this "semi-automatic" tool that helps create the meta-data?
Is this file part of pacemaker? It makes sense to me to make this data
part of the resource agent project.
Is the LRM (or equivalent) modified to know about this class of agents,
or is there a "universal Nagios RA" or similar?
How many agents have the meta data been written for?
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
