[OCF]Updates Resource Agent API

[Ragnar Kjørstad]

On Fri, Aug 01, 2003 at 11:08:06AM +0200, Lars Marowsky-Bree wrote:
> On 2003-08-01T11:11:57,
>    Horms <horms@verge.net.au> said:
> 
> > * Section 3.2
> > 
> >   "The subdirectories allow the installation of multiple RAs for the same
> >   type, but from different vendors or package versions.
> > 
> >   TODO: As the resource type is also embedded in the metadata returned
> >   from the RA, should this sentence go away and instead have the RM
> >   discover the installed resource types?"
> > 
> >   I don't see any advantage to this. The proposed directory
> >   structure seems both logical and conenient.
> 
> Well, but it also means that the filenames have special meanings which
> is redundant wrt the metadata. I was just asking whether that was a good
> idea.
> 
> What do the others think?

I think enforcing filename==resource-type is a good idea. 

It would be very confusing if to start resource-type A you would have to
run script B - I can hardly see any reasons to do this.

So what about the redundant metadata?
I think we should either remove it, or state that it has to have the
same name as the filename of the script.


At least that's my initial thought - unless you have a convincing
argument why it would be useful to remove the filename/resource-type
binding?



-- 
Ragnar Kjørstad