TWiki> EGEE Web>InformationSystem>SyncRepl (revision 1)EditAttachPDF

snip Syncrepl supports both partial and sparse replications. The shadow DIT fragment is defined by a general search criteria consisting of base, scope, filter, and attribute list. The replica content is also subject to the access privileges of the bind identity of the syncrepl replication connection. snip

Taken from: http://www.bind9.net/manual/openldap/2.3/syncrepl.html

So partial dataset: No problems; you can specify accessible attributes in the ACL for the syncrepl user on the provider, or the attributes to replicate via the filter on the consumer.

As for the rest of the tree; since you have specified a leaf of the DIT on the consumer to be replicated from a provider (with a scope), it will ignore everything above it (and outside the scope) and just replicate the provider into this leaf of the consumer DIT. So no problems here.

The thing I have NOT seen is replicating a section of a DIT to another dn:

i.e. Provider DN: o=grid,ou=luxy - Containing the entry: uid=hotness Consumer DN: o=grid,c=taiwan,ou=luxy

Is suspect this is not possible but I have not looked into it enough, and never had cause to test it.

> >
> > Also do you know where I can find pre build rpms for RHL5 and RHL4?

Always had luck with this guys work:

/etc/yum.repos.d/OpenLDAP.repo

# # OpenLDAP RPMs provided by Buchan Milne. No warranty or support provided on # these packages. # # 1)Save as /etc/yum.repos.d/OpenLDAP.repo # wget http://staff.telkomsa.net/packages/OpenLDAP.repo -O /etc/yum.repos.d/OpenLDAP.repo # 2) # RHEL5: # yum upgrade openldap-servers # or # yum install openldap2.4-servers # RHEL4 and older: # yum install openldap2.3-servers # or # yum install openldap2.4-servers # Install libhoard or lib64hoard for a better memory allocator

[OpenLDAP - Buchan Milne] name=OpenLDAP-$releasever baseurl=http://staff.telkomsa.net/packages/rhel $releasever/openldap/$basearch gpgcheck=1 gpgkey=http://staff.telkomsa.net/packages/bgmilne.asc enabled=1

> >
> > The other thing that we do in the top level BDII is to use the FCR
> > mechanism to delete come attributes. Is there any way to do this with
> > the sync repel method. Sync the DB but with one or two attributes do
> > something different?

As above the filter on the consumer or the ACL on the provider should take care of what gets replicated.

Just one question, what is FCR??

FYI

-- LaurenceField - 16 Dec 2008

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 2008-12-16 - LaurenceField
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback