[ClusterLabs Developers] Resurrecting OCF
Oyvind Albrigtsen
oalbrigt at redhat.com
Wed Jul 20 06:56:43 UTC 2016
On 19/07/16 16:51, Klaus Wenninger wrote:
> On 07/19/2016 04:33 PM, Oyvind Albrigtsen wrote:
>> On 19/07/16 14:35, Lars Ellenberg wrote:
>>> On Mon, Jul 18, 2016 at 11:13:42AM -0500, Ken Gaillot wrote:
>>>> A suggestion came up recently to formalize a new version of the OCF
>>>> resource agent API standard[1].
>>>>
>>>> The main goal would be to formalize the API as it is actually used
>>>> today, and to replace the "unique" meta-data attribute with two new
>>>> attributes indicating uniqueness and reloadability. We could also add
>>>> the fence agent API as a new spec, or expand the RA spec to cover both.
> might think of alert-agents here as well ...
Good idea. That might be nice to include as well.
>
> having ambivalent thoughts about it myself:
>
> - new feature that might be altered as result of feedback frequently,
> maybe in an incompatible way
> so putting effort into formalizing the API might not be worth it or
> even make it harder to do
> incompatible changes
> - formalizing the API together with the other agent-APIs might foster
> usage of the feature -
> create feedback - lead to quicker approximation of the feature
>
>>>> The Open Cluster Framework (OCF) was originally created in 2003 as a
>>>> working group of the Free Standards Group, which itself was absorbed
>>>> into the Linux Foundation in 2007. Today, OCF isn't even listed among
>>>> the Linux Foundation's workgroups[2].
>>>>
>>>> The opencf.org domain name (and, IIRC, website) is owned by Linbit.
>>> To link with the last few times this came up:
>>>
>>> From: Lars Ellenberg, 2015-02-10 20:44:40 GMT
>>> Reviving the OCF OpenCF.org Open cluster framework
>>> http://thread.gmane.org/gmane.comp.clustering.opencf.general/31/focus=31
>>> http://thread.gmane.org/gmane.comp.clustering.opencf.general/31/focus=46
>>>
>>> ^^ that one seems relevant.
>>> Basically "we all" agreed that $someone should do $something,
>>> and we would point all available pointers we still
>>> have control over to the result.
>>>
>>> As it frequently is, no-one felt to be $someone,
>>> and so $something still needs to be done :-)
>> I can take care of formalizing the new OCF API.
>>
>>
>> Oyvind
>>> Thanks for picking it up again!
>>>
>>> Re "LF work group": I'm very bad with bureaucracy myself...
>>>
>>> Older:
>>>
>>> From: Marek "marx" Grac, 2014-10-27 10:23:05 GMT
>>> Who will maintain OCF standard? Proposal for changes in DTD for
>>> fence/resource agents
>>> http://thread.gmane.org/gmane.comp.clustering.opencf.general/21
>>> (in which Linbit was given opencf and linux-ha domains)
>>>
>>> ...
>>> http://thread.gmane.org/gmane.comp.clustering.opencf.general/
>>>
>>>> Does anyone have opinions about this, or suggestions about where to
>>>> start? Should we keep it on the mailing lists, and focus on the RA API?
>>>> Or should we figure out the status of OCF itself as an entity, and
>>>> resurrect it somehow?
>>>>
>>>> [1]
>>>> http://www.opencf.org/cgi-bin/viewcvs.cgi/specs/ra/resource-agent-api.txt?rev=HEAD
>>>>
>>>> [2] http://www.linuxfoundation.org/collaborate/workgroups
>>>> --
>>>> Ken Gaillot <kgaillot at redhat.com>
>> _______________________________________________
>> Developers mailing list
>> Developers at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/developers
>
> _______________________________________________
> Developers mailing list
> Developers at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/developers
More information about the Developers
mailing list