Hi,
with two incompatible versions of RA-API-1, I think it's time to move to a two-level versioning pattern, like "RA-API-1.1". Besides that I think it's time to change the current version to "2.0" or so. From then on, compatible changes would increment the fractional part of the version, while incompatible changes would increment the integer part.
A bit more concrete:
I guess "parameter" allows multiple descriptions to support Internationalization (i18n) of descriptions:
<!ELEMENT parameter (longdesc+,shortdesc+,content)>
However the "resource-agent" does not allow multiple descriptions:
<!ELEMENT resource-agent (version,longdesc,shortdesc,parameters?,actions) >
(Some comments on I18n in the DTD would be fine.)
Now how would one actually select a language? The RA will always return the same metadata.
A personal thing I don't like is that "shortdesc" comes after "longdesc". Usually a heading comes before the body text, and I feel like that for shortdesc and longdesc.
For "type (string|integer|boolean|time)" I feel the DTD should have some comments on how "boolean" and "time" will be actually presented. The assumption for typed data is that the framework will actually check the types (i.e. trying to set a "boolean" parameter to "7" should be rejected, just as trying to set an "integer" parameter to "true" should be rejected). I think the documentation does not say a lot on that issue.
There should be a comment in the DTD on:
<!ATTLIST action
name (start|stop|recover|monitor|restart|migrate_to|migrate_from|promote
|demote|notify|status|reload|meta-data|usage|methods|validate-all) #REQUIRED
stating which methods are actually required.
Regards,
Ulrich
_______________________________________________
ha-wg-technical mailing list
ha-wg-technical@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/ha-wg-technical
with two incompatible versions of RA-API-1, I think it's time to move to a two-level versioning pattern, like "RA-API-1.1". Besides that I think it's time to change the current version to "2.0" or so. From then on, compatible changes would increment the fractional part of the version, while incompatible changes would increment the integer part.
A bit more concrete:
I guess "parameter" allows multiple descriptions to support Internationalization (i18n) of descriptions:
<!ELEMENT parameter (longdesc+,shortdesc+,content)>
However the "resource-agent" does not allow multiple descriptions:
<!ELEMENT resource-agent (version,longdesc,shortdesc,parameters?,actions) >
(Some comments on I18n in the DTD would be fine.)
Now how would one actually select a language? The RA will always return the same metadata.
A personal thing I don't like is that "shortdesc" comes after "longdesc". Usually a heading comes before the body text, and I feel like that for shortdesc and longdesc.
For "type (string|integer|boolean|time)" I feel the DTD should have some comments on how "boolean" and "time" will be actually presented. The assumption for typed data is that the framework will actually check the types (i.e. trying to set a "boolean" parameter to "7" should be rejected, just as trying to set an "integer" parameter to "true" should be rejected). I think the documentation does not say a lot on that issue.
There should be a comment in the DTD on:
<!ATTLIST action
name (start|stop|recover|monitor|restart|migrate_to|migrate_from|promote
|demote|notify|status|reload|meta-data|usage|methods|validate-all) #REQUIRED
stating which methods are actually required.
Regards,
Ulrich
_______________________________________________
ha-wg-technical mailing list
ha-wg-technical@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/ha-wg-technical