<html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hello, <blockquote>The subject of provisioning was discussed <a class="moz-txt-link-freetext" href="https://www.redhat.com/archives/freeipa-devel/2016-May/msg00065.html">https://www.redhat.com/archives/freeipa-devel/2016-May/msg00065.html</a>. The documentation of the provisioning procedure is still going on but reviewing it I have a doubt about RetroCL/Content_Sync. Provisioning will be done with high recommendations/constraints: <ul> <li>The provisioned instance should not be accessed by ldap client during provisioning. </li> <li>The IPA deployment should contain only one server (the one used for provisioning) in order to prevent replication latency</li> </ul> During provisioning, disabling RetroCL/Content_Sync gives a ~10% improvements (reducing the #ADD). The drawback of disabling RetroCL/Content_Sync is that the provisioned instance will not be able to send provisioned entries through syncRepl. Now considering that the provisioned instance is unique in the topology and will do full init of replicas, I think SyncRepl is useless and then we can disable RetroCL/Content_Sync during provisioning. Anyone is seeing a problem if those plugins are disabled during provisioning ? thanks thierry </blockquote> </body> </html>