Re: using SRV-records in syncrepl

2023-01-20 Thread Norman Gray
Ondřej, hello. On 20 Jan 2023, at 16:19, Ondřej Kuzník wrote: > DNS retrieval and parsing of SRV records is the easy part, and libevent > has code to help us with that already. It's the management of the > backends on the tier (shutting down those that aren't listed anymore, > adding those t

Re: using SRV-records in syncrepl

2023-01-20 Thread Ondřej Kuzník
On Fri, Jan 20, 2023 at 03:33:21PM +, Norman Gray wrote: > Ondřej, hello. > > On 20 Jan 2023, at 10:47, Ondřej Kuzník wrote: >> That said, patches implementing some kind of SRV are welcome. The easiest >> way might be to introduce an lloadd tier implementation that manages its >> backend col

Re: using SRV-records in syncrepl

2023-01-20 Thread Howard Chu
Norman Gray wrote: > > Ondřej, hello. > > On 20 Jan 2023, at 10:47, Ondřej Kuzník wrote: > >> That said, patches implementing some kind of SRV are welcome. The easiest >> way might be to introduce an lloadd tier implementation that manages its >> backend collection accordingly. > > It's not a

Re: using SRV-records in syncrepl

2023-01-20 Thread Norman Gray
Quanah, hello. On 20 Jan 2023, at 15:43, Quanah Gibson-Mount wrote: > There is no license noted in this file, which would be a requirement to even > look at it. No problem -- I've reattached a version with the BSD 2-clause licence included. Is that an OK one for you? Best wishes, Norman

Re: using SRV-records in syncrepl

2023-01-20 Thread Norman Gray
And... On 20 Jan 2023, at 15:33, Norman Gray wrote: > This exposes a function > > char* get_sorted_srv_records(const char* domain); > > which does a SRV lookup, and orders the records that come back according to > the specification of RFC 2782 (though in a single pass, rather than the > clu

Re: using SRV-records in syncrepl

2023-01-20 Thread Quanah Gibson-Mount
--On Friday, January 20, 2023 3:33 PM + Norman Gray wrote: Ondřej, hello. On 20 Jan 2023, at 10:47, Ondřej Kuzník wrote: That said, patches implementing some kind of SRV are welcome. The easiest way might be to introduce an lloadd tier implementation that manages its backend coll

Re: using SRV-records in syncrepl

2023-01-20 Thread Norman Gray
Ondřej, hello. On 20 Jan 2023, at 10:47, Ondřej Kuzník wrote: > That said, patches implementing some kind of SRV are welcome. The easiest > way might be to introduce an lloadd tier implementation that manages its > backend collection accordingly. It's not an OpenLDAP patch, but I've attached

Re: using SRV-records in syncrepl

2023-01-20 Thread Ondřej Kuzník
On Thu, Jan 19, 2023 at 04:39:26PM +0100, Stefan Kania wrote: > Hi Ondřej, > > I know, that I can put more then one uri to the "provider"-entry of > syncrepl. The questions comes up wile installing and testing lloadd. So it > not a special lloadd-thing. In general I would like to know if I could u

Re: using SRV-records in syncrepl

2023-01-19 Thread Stefan Kania
Hi Ondřej, I know, that I can put more then one uri to the "provider"-entry of syncrepl. The questions comes up wile installing and testing lloadd. So it not a special lloadd-thing. In general I would like to know if I could use the SRV-records. That would make changing an OpenLDAP-Server (an

Re: using SRV-records in syncrepl

2023-01-19 Thread Ondřej Kuzník
On Thu, Jan 19, 2023 at 11:48:45AM +0100, Stefan Kania wrote: > hi to all, > > is it somehow possible to finde the provider in "syncrepl" of a consumer via > DNS SRV-records. > If I have several providers with lloadd in front of it and the consumers are > only contacting the loadbalancer, the it w

using SRV-records in syncrepl

2023-01-19 Thread Stefan Kania
hi to all, is it somehow possible to finde the provider in "syncrepl" of a consumer via DNS SRV-records. If I have several providers with lloadd in front of it and the consumers are only contacting the loadbalancer, the it would be nice to use the SRV-Records of the DNS. I could then set up tw