Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates
 64.233.162.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
        b=do9uO6Y1RaJau9imn9t3mnAy+VbKsBD62fBfjRNXZpXtCr2Tobs5bVRpADsBUS1CLaUui/jmpKVpmKUIoLA1Zi1Qta1sFvHXzlI98isYX7ozLDppCKvVvz6W3wfuulDzxi1t3Av5yDaSDBBQr/Ocxlgp17Wt6XfIYuii33oKUPY=
Message-ID: <a32f6b020706060341r140a0a73mdabde0f33c02e60f@mail.gmail.com>
Date: Wed, 6 Jun 2007 12:41:25 +0200
From: "Alex Karasulu" <akarasulu@apache.org>
Sender: akarasulu@gmail.com
To: "Apache Directory Developers List" <dev@directory.apache.org>,
	elecharny@iktek.com
Subject: Re: New configuration
In-Reply-To: <d45b08f00706060025r732b0054tc78ed7b4a261e206@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22325_31742239.1181126485290"
References: <d45b08f00706060025r732b0054tc78ed7b4a261e206@mail.gmail.com>

------=_Part_22325_31742239.1181126485290
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Great idea regarding a migration page to the new configuration layout.
Let's make this
guide as easy as possible and reflect these changes in the Studio
configuration plugin.

Looking forward to your summary since I can really use a refresher.  Thanks
for this E.

Alex

On 6/6/07, Emmanuel Lecharny <elecharny@gmail.com> wrote:
>
> Hi,
>
> we recently have had some issues regarding the configuration modification
> brought by the SASL inclusion. Those problems were not big, but we need t=
o
> address them in order to avoid a flury of mails from our current users wh=
en
> we will release 1.5.1 (I guess that with SASL, we need to deliver a new
> version).
>
> I would like to check if we can see which parts of the server are impacte=
d
> by such a modification, and to what extent :
> - first of all, documentation. We need to update the site, and also give
> the users a clear migration guide from the previous server.xml to the new
> one
> - the Studio 'Server Configuration Edirot' plugin : how much time to
> handle these modification do we need?
>
> Also, I think we should also discuss a little bit further about the
> configuration structure. I will try to gather the different convos we hav=
e
> had in the last three months about it, including the 'config in DIT' thre=
ad.
> This is important that we soon try to find an agreement and stabilize thi=
s
> configuration, and inform the 'world' about this move.
>
> I'm also thinking about Stefan Z=F6rner who is writing his third version =
of
> his book, I don't want him to have to rewrite parts of it just because he
> has snapshots of the old config in it ;) (may be it's a good way for him =
to
> get a contract for a forth version of his book ;)
>
> Emmanuel
>
> --
> Regards,
> Cordialement,
> Emmanuel L=E9charny
> www.iktek.com

------=_Part_22325_31742239.1181126485290
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Great idea regarding a migration page to the new configuration layout.&nbsp=
; Let&#39;s make this<br>guide as easy as possible and reflect these change=
s in the Studio configuration plugin.<br><br>Looking forward to your summar=
y since I can really use a refresher.&nbsp; Thanks for this E.
<br><br>Alex<br><br><div><span class=3D"gmail_quote">On 6/6/07, <b class=3D=
"gmail_sendername">Emmanuel Lecharny</b> &lt;<a href=3D"mailto:elecharny@gm=
ail.com">elecharny@gmail.com</a>&gt; wrote:</span><blockquote class=3D"gmai=
l_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0p=
t 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>we recently have had some issues regarding the configuration mod=
ification brought by the SASL inclusion. Those problems were not big, but w=
e need to address them in order to avoid a flury of mails from our current =
users when we will release=20
1.5.1 (I guess that with SASL, we need to deliver a new version).<br><br>I =
would like to check if we can see which parts of the server are impacted by=
 such a modification, and to what extent :<br>- first of all, documentation=
. We need to update the site, and also give the users a clear migration gui=
de from the previous=20
server.xml to the new one<br>- the Studio &#39;Server Configuration Edirot&=
#39; plugin : how much time to handle these modification do we need?<br><br=
>Also, I think we should also discuss a little bit further about the config=
uration structure. I will try to gather the different convos we have had in=
 the last three months about it, including the &#39;config in DIT&#39; thre=
ad. This is important that we soon try to find an agreement and stabilize t=
his configuration, and inform the &#39;world&#39; about this move.
<br><br>I&#39;m also thinking about Stefan Z=F6rner who is writing his thir=
d version of his book, I don&#39;t want him to have to rewrite parts of it =
just because he has snapshots of the old config in it ;) (may be it&#39;s a=
 good way for him to get a contract for a forth version of his book ;)
<br><br>Emmanuel<br clear=3D"all"><span class=3D"sg"><br>-- <br>Regards,<br=
>Cordialement,<br>Emmanuel L=E9charny<br><a href=3D"http://www.iktek.com" t=
arget=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,this)">w=
ww.iktek.com
</a>
</span></blockquote></div><br>

------=_Part_22325_31742239.1181126485290--