Re: [ClusterLabs Developers] [ClusterLabs] FenceAgentAPI

2017-03-07 Thread Digimer 
On 07/03/17 05:09 AM, Jan Pokorný wrote:
> On 06/03/17 17:12 -0500, Digimer wrote:
>>   The old FenceAgentAPI document on fedorahosted is gone now that fedora
>> hosted is closed. So I created a copy on the clusterlabs wiki:
>>
>> http://wiki.clusterlabs.org/wiki/FenceAgentAPI
> 
> Note that just few days ago I've announced that the page has moved to
> https://docs.pagure.org/ClusterLabs.fence-agents/FenceAgentAPI.md, see
> http://oss.clusterlabs.org/pipermail/developers/2017-February/000438.html
> (that hit just the developers list, I don't think it's of interest of
> users of the stack as such).  Therefore that's another duplicate, just
> as http://wiki.clusterlabs.org/wiki/Fedorahosted.org_FenceAgentAPI
> (linked from the original fedorahosted.org page so as to allow for
> future flexibility should the content still be visible, which turned
> out to not be the case) is.
> 
> I will add you (or whoever wants to maintain that file) to linux-cluster
> group at pagure.io so you can edit the underlying Markdown file (just let
> me off-list know your Fedora Account System username).  The file itself 
> is tracked under git repository, access URLs were provided in the
> announcement email.

Ah! I missed that. Glad to see it was covered already. I was mainly
stepping up because I thought it was missed, but if you're on it, you
know the topic better than I do. So if you want help, I'm happy to do
what I can, but otherwise I'll stand back and let you do your thing. :)

>>   It desperately needs an update. Specifically, it needs '-o metadata'
>> properly explained. I am happy to update this document and change the
>> cman/cluster.conf example over to a pacemaker example, etc, but I do not
>> feel like I am authoritative on the XML validation side of things.
>>
>>   Can someone give me, even just point-form notes, how to explain this?
>> If so, I'll create 'FenceAgentAPI - Working' document and I will have
>> anyone interested comment before making it an official update.
>>
>> Comments?
> 
> 
> 
> ___
> Users mailing list: us...@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 


-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould

___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers

Re: [ClusterLabs Developers] FenceAgentAPI

2017-03-07 Thread Marek Grac 
Hi,

On Mon, Mar 6, 2017 at 11:12 PM, Digimer  wrote:

> Hi all,
>
>   The old FenceAgentAPI document on fedorahosted is gone now that fedora
> hosted is closed. So I created a copy on the clusterlabs wiki:
>
> http://wiki.clusterlabs.org/wiki/FenceAgentAPI
>
>   It desperately needs an update. Specifically, it needs '-o metadata'
> properly explained. I am happy to update this document and change the
> cman/cluster.conf example over to a pacemaker example, etc, but I do not
> feel like I am authoritative on the XML validation side of things.
>




Login name


required=1 is used only with login, ip address and plug number. Other
options are required too but their constraints are more complex: e.g.
passwd OR passwd_script is required.

unique=0 is set for every option, so it does not have to be documented.

content type=(string|integer|boolean|second|select)


  
  


Currently, 'second' is same as the 'integer'.



>   Can someone give me, even just point-form notes, how to explain this?
> If so, I'll create 'FenceAgentAPI - Working' document and I will have
> anyone interested comment before making it an official update.
>

I will add also 'list-status' that prints list of available plugs together
with their status.

Best Practise) take existing fence agent and modify it, there is no reason
(except python-intollerance) to not use fencing library

m,
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers

Re: [ClusterLabs Developers] FenceAgentAPI

2017-03-07 Thread Jan Pokorný 
On 06/03/17 17:12 -0500, Digimer wrote:
>   The old FenceAgentAPI document on fedorahosted is gone now that fedora
> hosted is closed. So I created a copy on the clusterlabs wiki:
> 
> http://wiki.clusterlabs.org/wiki/FenceAgentAPI

Note that just few days ago I've announced that the page has moved to
https://docs.pagure.org/ClusterLabs.fence-agents/FenceAgentAPI.md, see
http://oss.clusterlabs.org/pipermail/developers/2017-February/000438.html
(that hit just the developers list, I don't think it's of interest of
users of the stack as such).  Therefore that's another duplicate, just
as http://wiki.clusterlabs.org/wiki/Fedorahosted.org_FenceAgentAPI
(linked from the original fedorahosted.org page so as to allow for
future flexibility should the content still be visible, which turned
out to not be the case) is.

I will add you (or whoever wants to maintain that file) to linux-cluster
group at pagure.io so you can edit the underlying Markdown file (just let
me off-list know your Fedora Account System username).  The file itself 
is tracked under git repository, access URLs were provided in the
announcement email.

>   It desperately needs an update. Specifically, it needs '-o metadata'
> properly explained. I am happy to update this document and change the
> cman/cluster.conf example over to a pacemaker example, etc, but I do not
> feel like I am authoritative on the XML validation side of things.
> 
>   Can someone give me, even just point-form notes, how to explain this?
> If so, I'll create 'FenceAgentAPI - Working' document and I will have
> anyone interested comment before making it an official update.
> 
> Comments?

-- 
Jan (Poki)


pgpR6PrKqVgj_.pgp
Description: PGP signature
___
Developers mailing list
Developers@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers