[OCF]Updates Resource Agent API

[Ragnar Kjørstad]

On Fri, Aug 01, 2003 at 08:27:33PM +0200, Ragnar Kjørstad wrote:
> Enforcing uniqueness may be usefull, but this change only solves part of
> the problem. Problem is that it only handles cases were a single field
> is unique by itself - not cases were two or more fields in combination
> must be unique. 

After rereading the spec, I see that that this property is in fact
handled by the unique-flag - it is the "each attribute by itself must be
unique"-property that is not handled.

E.g. if a RA has attributes "directory" and "tcp-port", and both need to
be unique, there is no way to specify that.

The original argument is still valid though. The current unique-property
solves the majority of cases, a more complicated scheeme could be
introduced in the next version of the API to solve them better (in which
case we would be better of not including unique-flags at all now), but
no matter how hard we try we're not going to solve cross-resource
conflicts completely, so the last option is simply not to try.


-- 
Ragnar Kjørstad