Re: [Pacemaker] Resource agents: parameter type enforcement and normalization

2009-07-14 Thread Lars Marowsky-Bree
On 2009-07-14T18:01:15, Florian Haas wrote: > That is true, and I am not contesting that they need to validate. I was > actually asking for, what shall we call it, instance attribute value > normalization. Yeah, I agree. Though RAs can simply "enforce" this by only accepting 'true/false' or 'yes

Re: [Pacemaker] Resource agents: parameter type enforcement and normalization

2009-07-14 Thread Florian Haas
Lars, On 07/14/2009 05:15 PM, Lars Marowsky-Bree wrote: >> Now considering the CIB already does, for example, IDREF validation, I >> really wonder why it shouldn't be doing content validation as well. > > It could, of course. > > But the problem would remain - the CLI/GUI would need to do their

Re: [Pacemaker] Resource agents: parameter type enforcement and normalization

2009-07-14 Thread Lars Marowsky-Bree
On 2009-07-03T08:55:21, Florian Haas wrote: > do nothing to actually enforce parameter types in the CIB. Instead, that > metadata is intended simply as a hint for the GUI or the CRM shell, and > parameter type enforcement is left to them. In other words, if a > parameter is declared as 'content t

Re: [Pacemaker] Resource agents: parameter type enforcement and normalization

2009-07-07 Thread Dejan Muhamedagic
Hi Florian, On Fri, Jul 03, 2009 at 08:55:21AM +0200, Florian Haas wrote: > Hello, > > continuing a discussion I started, briefly, with Andrew and Dejan yesterday. > > As I hear from Andrew, when we define parameters in resource agents and > describe them in the RA metadata information, then the