<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 30/07/15 15:43, Ludwig Krispenz wrote: </div> <blockquote cite="mid:55BA2A05.2050900@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 07/30/2015 03:14 PM, Martin Basti wrote: </div> <blockquote cite="mid:55BA2321.4070201@redhat.com" type="cite"> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> <div class="moz-cite-prefix">On 22/07/15 17:03, Martin Basti wrote: </div> <blockquote cite="mid:55AFB0CE.3020508@redhat.com" type="cite">On 20/07/15 19:04, Mark Reynolds wrote: <blockquote type="cite"> On 07/20/2015 12:50 PM, Martin Basti wrote: <blockquote type="cite">On 20/07/15 17:48, Petr Vobornik wrote: <blockquote type="cite">On 07/20/2015 05:24 PM, Rob Crittenden wrote: <blockquote type="cite">Martin Basti wrote: <blockquote type="cite"><a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://fedorahosted.org/freeipa/ticket/5086">https://fedorahosted.org/freeipa/ticket/5086</a> Patch attached. </blockquote> Is this going to be a shock on upgrades for people who until now may be relying on the fact that there is no limit? </blockquote> Not making any point, but have to note: Ludwig raised a question on users list but there was no feedback from users. <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.redhat.com/archives/freeipa-users/2015-July/msg00022.html">https://www.redhat.com/archives/freeipa-users/2015-July/msg00022.html</a> <blockquote type="cite"> Should there be a way for an admin to manage this, via the config module perhaps? IMHO this is a significant change and red flags need to be raised so users are aware of it. rob </blockquote> </blockquote> IIUC there is purge delay 7 days, so if changelog max age is 7 or more days, it will not break replication. The issue is if somebody uses changelog for different purpose, right? </blockquote> Well the replication changelog can not be used for anything else but the multimaster replication plugin. If a customer increased the replication purge delay you could potentially run into issues, but again this only comes into play when a replica is down for a very long time. I'm not sure if IPA even provides the option to adjust the replication purge delay, but that doesn't mean a customer can not adjust these settings on their own. Mark </blockquote> I'm attaching new patch, that modifies behavior of 'addifnew' keyword in update files. addifnew will no create new entry if doesn't exist. This is required for proper working of patch 292 Rob are you okay with these patches, as Mark wrote, changelog is used only for replication plugins, so it should not cause any issues to users. Martin^2 <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> These patches are ready to be reviewed. I'm just not sure if would be better to have replication changelog max age 8days, just to be sure. Should I explicitly set purge delay to 7days, or are we fine with 7days as default? </blockquote> I think 7d is a quite common setting, so it should be ok </blockquote> 7 days for changelog max age, or for purge delay, or for both? Should I explicitly set purge delay then? I'm thinking about the case when admin changed purge delay before upgrade, IMO I should check this value and set same value for changelog max age or don't upgrade changelog. Martin^2 <blockquote cite="mid:55BA2A05.2050900@redhat.com" type="cite"> <blockquote cite="mid:55BA2321.4070201@redhat.com" type="cite"> <pre class="moz-signature" cols="72">-- Martin Basti</pre> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> <pre class="moz-signature" cols="72">-- Martin Basti</pre> </body> </html>