<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 07/30/2015 03:14 PM, Martin Basti
wrote:<br>
</div>
<blockquote cite="mid:55BA2321.4070201@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 22/07/15 17:03, Martin Basti
wrote:<br>
</div>
<blockquote cite="mid:55AFB0CE.3020508@redhat.com" type="cite">On
20/07/15 19:04, Mark Reynolds wrote: <br>
<blockquote type="cite"> <br>
<br>
On 07/20/2015 12:50 PM, Martin Basti wrote: <br>
<blockquote type="cite">On 20/07/15 17:48, Petr Vobornik
wrote: <br>
<blockquote type="cite">On 07/20/2015 05:24 PM, Rob
Crittenden wrote: <br>
<blockquote type="cite">Martin Basti wrote: <br>
<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>
<br>
<br>
Patch attached. <br>
</blockquote>
<br>
Is this going to be a shock on upgrades for people who
until now may be <br>
relying on the fact that there is no limit? <br>
</blockquote>
<br>
Not making any point, but have to note: Ludwig raised a
question on users list but there was no feedback from
users. <br>
<br>
<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>
<br>
<br>
<blockquote type="cite"> <br>
Should there be a way for an admin to manage this, via
the config module <br>
perhaps? <br>
<br>
IMHO this is a significant change and red flags need to
be raised so <br>
users are aware of it. <br>
<br>
rob <br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
IIUC there is purge delay 7 days, so if changelog max age is
7 or more days, it will not break replication. <br>
The issue is if somebody uses changelog for different
purpose, right? <br>
</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. <br>
<br>
Mark <br>
<br>
</blockquote>
<br>
I'm attaching new patch, that modifies behavior of 'addifnew'
keyword in update files. <br>
addifnew will no create new entry if doesn't exist. <br>
This is required for proper working of patch 292 <br>
<br>
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. <br>
<br>
Martin^2 <br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
These patches are ready to be reviewed.<br>
I'm just not sure if would be better to have replication changelog
max age 8days, just to be sure.<br>
Should I explicitly set purge delay to 7days, or are we fine with
7days as default?<br>
</blockquote>
I think 7d is a quite common setting, so it should be ok<br>
<blockquote cite="mid:55BA2321.4070201@redhat.com" type="cite">
<pre class="moz-signature" cols="72">--
Martin Basti</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>