I had the same problem when i started out my HA cluster. 

I gave up to search an "offcial OCF" DTD. I think document 
upgrade on the OCF hompage is pretty dead.

Attached a DTD i found somewhere (forgot from where) made. 

A good starting mount is just to grep trough the RA provided by
heartbeat itself.

It is the OCF DTD with follogin changes:
+ additional tags for "longdesc", "shortdesc" 
+ "parameter" tag has an additional attribute "required"
+ "action" attribute "name": use "monitor"/"validate-all instead 
of "status"/"

See the attachment (i habe no clue why i have an attribute 
"expert level" i the attribute).

An other question arises to me. Can anyone tell me if the "meta-data"
option is used by heartbeat (except for the graphical user interface)?

kind regards
Max

On Friday 15 June 2007, Takenaka Kazuhiro wrote:
> Hi Hu, thanks for your reply.
> 
> Hmm... The latest OCF RAs have 'longdesc' and 'shortdesc'
> in XML of meta_data method as child tags of 'resource-agent'.
> 
> But the DTD you ponited defines neither.
> 
> And both DTDs you and I pointed have a definition of 'special' tag
> and it is declared necessary, but no latest OCF RAs have it.
> 
> Does anyone know whether those three tags are necessary for
> a meta-data XML or not?
> 
> > I think the official source is still
> > 
> > http://opencf.org/cgi-bin/viewcvs.cgi/specs/ra/ra-api-1.dtd
> > 
> >> > Hi all.
> >> >
> >> > I am looking for the latest DTD of ra-api.
> >> >
> >> > I suppose a DTD written in following URL is it.
> >> >
> >> > http://lists.community.tummy.com/pipermail/ocf/2005-December/001370.html
> >> >
> >> > Is my thinking correct ?
> >> >
> >> > Sincerely.



-- 
Max Hofer
APUS Software G.m.b.H.
A-8074 Raaba, Bahnhofstraße 1/1
T| +43 316 401629 11
F| +43 316 401629 9
W| www.apus.co.at
E| [EMAIL PROTECTED]

Attachment: ra-api-1.dtd
Description: application/xml-dtd

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to