Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A66C0DD70 for ; Tue, 17 Jul 2012 07:59:18 +0000 (UTC) Received: (qmail 80911 invoked by uid 500); 17 Jul 2012 07:59:17 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 80732 invoked by uid 500); 17 Jul 2012 07:59:17 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 80661 invoked by uid 99); 17 Jul 2012 07:59:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2012 07:59:14 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 74.125.83.50 as permitted sender) Received: from [74.125.83.50] (HELO mail-ee0-f50.google.com) (74.125.83.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2012 07:59:07 +0000 Received: by eeke49 with SMTP id e49so42530eek.37 for ; Tue, 17 Jul 2012 00:58:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mVk8FSad2FpyvmVm9y2Igw49hxJIP8CXG9CnRLgMBEA=; b=eUTUIZMLEEAYsp72+G0p13G6PIAqjNW6HpkaWPtW4yb4WMquBi844a9zll0fi+0RLQ +K8uZCQdV/Pz8Meiu9JZ5jMZ8JtALGBrboEOkmCftBoZd6GzKQHk4fttM+1Xlza2RKKK MzfRbedip0MjrkRd9OKzQMBI2m03QmcCs1RjsdnYoH1TZtQX68XN0wzmW1ilWYIsez95 pUHyQm1wD72nBDI6qQRTiWi69CHP0OeAf7+7kI/xgFZfXEc09KyXRhZazANis/ONOLfI aKNSjw32/xCNC9RxL/cD4VKWdtTdaXjTZ4HqQyiLcsO5jnLUV5bfBmedS5L3fRBTCOCy j3Cw== Received: by 10.14.0.130 with SMTP id 2mr1645042eeb.22.1342511926148; Tue, 17 Jul 2012 00:58:46 -0700 (PDT) Received: from Emmanuels-MacBook-Pro.local ([90.84.144.113]) by mx.google.com with ESMTPS id t6sm25201234eeo.17.2012.07.17.00.58.43 (version=SSLv3 cipher=OTHER); Tue, 17 Jul 2012 00:58:44 -0700 (PDT) Message-ID: <50051B34.3040200@gmail.com> Date: Tue, 17 Jul 2012 09:58:44 +0200 From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= Reply-To: elecharny@apache.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: Question about Replication of Config Partition and Schema Partition References: <5001FAB5.5090302@gmail.com> <50043839.5010203@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Le 7/17/12 12:28 AM, Alex Karasulu a écrit : > On Mon, Jul 16, 2012 at 6:50 PM, Emmanuel Lécharny wrote: > >> >> I was pretty much thinking that we could store those informations in a >> plain text file, but that would be a bit overkilling, when we can store >> them in a the DIT too. Maybe storing those information sinto the ou=config >> entry could be the right thing to do, assuming that the ou=config is not >> replicated (we will only replicate what's under ou=config, ie, its children) >> >> > Please please please let's not fuck with this. This is the worst idea I've > heard of yet. We don't need another one off here. That was just a suggestion, but I do agree this is more a hack than anything else. Plus after having checked the ou=config file, I don't even thinhk it's necessary. I totally buy the fact that implementing partial replication would solve the issue. The ou=config DIT starts with : version: 1 dn: ou=config ou: config objectclass: top objectclass: organizationalUnit dn: ads-directoryServiceId=default,ou=config objectclass: top objectclass: ads-directoryService ads-directoryserviceid: default ads-dsreplicaid: 1 ... As we can see, each configuration is specific to a service, here "default". If we correctly name the instances so that there is no possible confusion between them, then we should be safe even if we replicate everything. The thing we have to solve is about the instance name : how dos the server get its instance name ? I must admit that, even if I worked on those thing in the past, it's not really fresh in my mind... -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com