Re: [Linux-cluster] Problem with automating ricci & ccs

2013-01-18 Thread Jan Pokorný
On 18/01/13 20:44 +0100, Jakov Sosic wrote: > On 01/18/2013 07:44 PM, Jakov Sosic wrote: >> >> Thank you for your explanation. I've figured that out later myself :) >> >> So, instead of using the sha1sum to avoide collisions, I use nodename. >> So my client_cert names look like this: >> >> clien

Re: [Linux-cluster] [RESOLVED] HA iSCSI with DRBD

2013-01-18 Thread Eric
After rebooting both nodes, I checked the cluster status again and found this: Code: > san1:~ # crm_mon -1 > > Last updated: Fri Jan 18 11:51:28 2013 > Last change: Fri Jan 18 09:00:03 2013 by root via cibadmin on san2 > Stack: openais > Current DC: san2 - partition with quorum > Vers

Re: [Linux-cluster] Problem with automating ricci & ccs

2013-01-18 Thread Jakov Sosic
On 01/18/2013 07:44 PM, Jakov Sosic wrote: > On 01/16/2013 02:14 PM, Jan Pokorný wrote: > >> The point here is that once the public certificate of ccs is recognized by >> ricci as authorized by supplying the password within the initial session, >> any other other session will be passwordless, base

Re: [Linux-cluster] Problem with automating ricci & ccs

2013-01-18 Thread Jakov Sosic
On 01/16/2013 02:14 PM, Jan Pokorný wrote: > The point here is that once the public certificate of ccs is recognized by > ricci as authorized by supplying the password within the initial session, > any other other session will be passwordless, based only on the "proved" > client's certificate. >