You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by Flavio Junqueira <fp...@yahoo.com> on 2013/05/22 02:07:58 UTC
[DISCUSS] Release 4.3.0
It is probably time to start thinking about wrapping up 4.3.0. There are 77
jiras marked for 4.3.0 and we have considered for this release the following
features:
* Security (SASL on bookie)
* NIOServerFactory -> Netty
The rack awareness work was not marked for this release, but I suppose it is
ok to include it here, since the patch Sijie proposed for BOOKKEEPER-592
seems to be in good shape. The Netty work is in BOOKKEEPER-555, which is in
already. We just need to work on the security part, which I think there has
been some progress recently. At least I have seen some progress from Rakesh.
Any thoughts about cutting a release say by mid-june?
-Flavio
Re: [DISCUSS] Release 4.3.0
Posted by Ivan Kelly <iv...@apache.org>.
4.3.0. For 4.2.2 the release process shouldn't take more than an hour
or two.
-Ivan
On Fri, May 31, 2013 at 12:19:38PM +0200, Flavio Junqueira wrote:
> I was referring to 4.3.0, since you've been the release manager for the 4.2 branch. Are you referring to 4.3.0 or 4.2.2?
>
> -Flavio
>
> On May 31, 2013, at 12:07 PM, Ivan Kelly <iv...@apache.org> wrote:
>
> > +1. I don't have time to do a release for the next few weeks.
> >
> > -Ivan
> >
> > On Fri, May 31, 2013 at 11:22:48AM +0200, Flavio Junqueira wrote:
> >> I didn't get an answer to my question about the release manager. If no one else volunteers, I volunteer to be the release manager.
> >>
> >> -Flavio
> >>
> >> On May 24, 2013, at 7:11 PM, Ivan Kelly <iv...@apache.org> wrote:
> >>
> >>> On Thu, May 23, 2013 at 11:49:44AM +0100, Flavio Junqueira wrote:
> >>>> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
> >>>> BOOKKEEPER-XXX: Provide support for bookie authentication
> >>>> BOOKKEEPER-390: Provide support for zookeeper authentication
> >>>> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
> >>>> characters max, which fundamentally limits them at 9 billion
> >>>> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
> >>>> BOOKKEEPER-592: allow application to recommend ledger data locality (ready
> >>>> to go)
> >>>> BOOKKEEPER-432: Improve performance of entry log range read per ledger
> >>>> entries
> >>>> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
> >>>>
> >>>> Are these the core jiras we need to resolve for 4.3.0?
> >>> Pretty much.
> >>>
> >>> -Ivan
> >>
>
Re: [DISCUSS] Release 4.3.0
Posted by Flavio Junqueira <fp...@yahoo.com>.
I was referring to 4.3.0, since you've been the release manager for the 4.2 branch. Are you referring to 4.3.0 or 4.2.2?
-Flavio
On May 31, 2013, at 12:07 PM, Ivan Kelly <iv...@apache.org> wrote:
> +1. I don't have time to do a release for the next few weeks.
>
> -Ivan
>
> On Fri, May 31, 2013 at 11:22:48AM +0200, Flavio Junqueira wrote:
>> I didn't get an answer to my question about the release manager. If no one else volunteers, I volunteer to be the release manager.
>>
>> -Flavio
>>
>> On May 24, 2013, at 7:11 PM, Ivan Kelly <iv...@apache.org> wrote:
>>
>>> On Thu, May 23, 2013 at 11:49:44AM +0100, Flavio Junqueira wrote:
>>>> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
>>>> BOOKKEEPER-XXX: Provide support for bookie authentication
>>>> BOOKKEEPER-390: Provide support for zookeeper authentication
>>>> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
>>>> characters max, which fundamentally limits them at 9 billion
>>>> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
>>>> BOOKKEEPER-592: allow application to recommend ledger data locality (ready
>>>> to go)
>>>> BOOKKEEPER-432: Improve performance of entry log range read per ledger
>>>> entries
>>>> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
>>>>
>>>> Are these the core jiras we need to resolve for 4.3.0?
>>> Pretty much.
>>>
>>> -Ivan
>>
Re: [DISCUSS] Release 4.3.0
Posted by Ivan Kelly <iv...@apache.org>.
+1. I don't have time to do a release for the next few weeks.
-Ivan
On Fri, May 31, 2013 at 11:22:48AM +0200, Flavio Junqueira wrote:
> I didn't get an answer to my question about the release manager. If no one else volunteers, I volunteer to be the release manager.
>
> -Flavio
>
> On May 24, 2013, at 7:11 PM, Ivan Kelly <iv...@apache.org> wrote:
>
> > On Thu, May 23, 2013 at 11:49:44AM +0100, Flavio Junqueira wrote:
> >> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
> >> BOOKKEEPER-XXX: Provide support for bookie authentication
> >> BOOKKEEPER-390: Provide support for zookeeper authentication
> >> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
> >> characters max, which fundamentally limits them at 9 billion
> >> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
> >> BOOKKEEPER-592: allow application to recommend ledger data locality (ready
> >> to go)
> >> BOOKKEEPER-432: Improve performance of entry log range read per ledger
> >> entries
> >> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
> >>
> >> Are these the core jiras we need to resolve for 4.3.0?
> > Pretty much.
> >
> > -Ivan
>
Re: [DISCUSS] Release 4.3.0
Posted by Flavio Junqueira <fp...@yahoo.com>.
I didn't get an answer to my question about the release manager. If no one else volunteers, I volunteer to be the release manager.
-Flavio
On May 24, 2013, at 7:11 PM, Ivan Kelly <iv...@apache.org> wrote:
> On Thu, May 23, 2013 at 11:49:44AM +0100, Flavio Junqueira wrote:
>> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
>> BOOKKEEPER-XXX: Provide support for bookie authentication
>> BOOKKEEPER-390: Provide support for zookeeper authentication
>> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
>> characters max, which fundamentally limits them at 9 billion
>> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
>> BOOKKEEPER-592: allow application to recommend ledger data locality (ready
>> to go)
>> BOOKKEEPER-432: Improve performance of entry log range read per ledger
>> entries
>> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
>>
>> Are these the core jiras we need to resolve for 4.3.0?
> Pretty much.
>
> -Ivan
Re: [DISCUSS] Release 4.3.0
Posted by Ivan Kelly <iv...@apache.org>.
On Thu, May 23, 2013 at 11:49:44AM +0100, Flavio Junqueira wrote:
> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
> BOOKKEEPER-XXX: Provide support for bookie authentication
> BOOKKEEPER-390: Provide support for zookeeper authentication
> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
> characters max, which fundamentally limits them at 9 billion
> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
> BOOKKEEPER-592: allow application to recommend ledger data locality (ready
> to go)
> BOOKKEEPER-432: Improve performance of entry log range read per ledger
> entries
> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
>
> Are these the core jiras we need to resolve for 4.3.0?
Pretty much.
-Ivan
Re: [DISCUSS] Release 4.3.0
Posted by Flavio Junqueira <fp...@yahoo.com>.
I believe we have committed these patches to trunk, but not for branch 4.2. We would need to do it.
Calling these API changes bugfixes is not exactly what I call orthodox, but fine, we can do it if it makes everyone happy.
Whitney, Could you confirm that this is what you'd like us to do?
-Flavio
On May 24, 2013, at 7:06 PM, Ivan Kelly <iv...@apache.org> wrote:
> On Thu, May 23, 2013 at 04:59:32PM -0400, Whitney Sorenson wrote:
>> I think having a release sooner than late July would be great (esp. since I
>> don't really care about security, but some of the other work that has been
>> done would be great to have.)
> I assume you're talking about the API changes
> (BookKeeperAdmin#listLedgers() & BookKeeper#isClosed(long))?
>
> If it's just this, then I think we could possibly do a spot release as
> 4.2.2. The minor version releases should only really be for
> bugfix releases, these changes are more like a bugfix than a
> feature. They don't change anything internal to bookkeeper. Really
> they just expose something that wasn't exposed previously.
>
> I'd feel more comfortable pushing it out as 4.2.2 rather than
> 4.3.0. The second number really should call for some meatier changes.
>
> -Ivan
Re: [DISCUSS] Release 4.3.0
Posted by Ivan Kelly <iv...@apache.org>.
On Thu, May 23, 2013 at 04:59:32PM -0400, Whitney Sorenson wrote:
> I think having a release sooner than late July would be great (esp. since I
> don't really care about security, but some of the other work that has been
> done would be great to have.)
I assume you're talking about the API changes
(BookKeeperAdmin#listLedgers() & BookKeeper#isClosed(long))?
If it's just this, then I think we could possibly do a spot release as
4.2.2. The minor version releases should only really be for
bugfix releases, these changes are more like a bugfix than a
feature. They don't change anything internal to bookkeeper. Really
they just expose something that wasn't exposed previously.
I'd feel more comfortable pushing it out as 4.2.2 rather than
4.3.0. The second number really should call for some meatier changes.
-Ivan
Re: [DISCUSS] Release 4.3.0
Posted by Whitney Sorenson <ws...@hubspot.com>.
I think having a release sooner than late July would be great (esp. since I
don't really care about security, but some of the other work that has been
done would be great to have.)
Just my 2c though.
On Thu, May 23, 2013 at 11:57 AM, Flavio Junqueira <fp...@yahoo.com>wrote:
> I also would rather releases sooner, but we need to reach agreement on what
> the release will contain. The release manager essentially decides where to
> cut. Do we have a release manager for 4.3.0 already or that is still open?
>
> For 4.3.0, we have promised security for release 4.3.0, so I think we need
> to have at least that. Some of the other features, like 592, are ready to
> get in, so we don't expect them to be in the way. The other jiras depend on
> the reporters to stepping up and saying if they need to be in and find
> someone to wrap up the work.
>
> As for having 4.2.2, we tend to use the last digit for bug fix releases,
> perhaps including some updates. This next release will have more than bug
> fixes.
>
> It sounds like you'd like us to have a release sooner, yes?
>
> -Flavio
>
> ----Original Message-----
> From: Whitney Sorenson [mailto:wsorenson@hubspot.com]
> Sent: 23 May 2013 15:30
> To: bookkeeper-dev@zookeeper.apache.org
> Subject: Re: [DISCUSS] Release 4.3.0
>
> As an outside stakeholder, I am curious if anyone has considered dividing
> up
> these releases since there hasn't been a release in a while.
>
> For the sake of shipping something sooner rather than continuing to append
> new features and ideas, what do you guys think about doing a 4.2.2 as an
> intermediate?
>
> If it's an unreasonable suggestion, I understand completely.
>
> -Whitney
>
>
>
> On Thu, May 23, 2013 at 6:49 AM, Flavio Junqueira
> <fp...@yahoo.com>wrote:
>
> > This is a summary according to my understanding of the discussion so far:
> >
> > BOOKKEEPER-575: Bookie SSL support (umbrella jira)
> > BOOKKEEPER-XXX: Provide support for bookie authentication
> > BOOKKEEPER-390: Provide support for zookeeper authentication
> > BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
> > characters max, which fundamentally limits them at 9 billion
> > BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
> > BOOKKEEPER-592: allow application to recommend ledger data locality
> > (ready to go)
> > BOOKKEEPER-432: Improve performance of entry log range read per ledger
> > entries
> > BOOKKEEPER-220: Managed ledger (optional, but nice to have)
> >
> > Are these the core jiras we need to resolve for 4.3.0?
> >
> > -Flavio
> >
> > -----Original Message-----
> > From: Ivan Kelly [mailto:ivank@apache.org]
> > Sent: 22 May 2013 14:43
> > To: bookkeeper-dev@zookeeper.apache.org
> > Subject: Re: [DISCUSS] Release 4.3.0
> >
> > >
> > > [fpj] Is there a jira for the SASL work? Do happen to know all jiras
> > > related to security we need to address?
> > There's no JIRA for sasl or auth yet. SSL is
> > https://issues.apache.org/jira/browse/BOOKKEEPER-575
> >
> > > > > - skiplist based ledger storage and other improvements on bookie
> > server
> > > > > side (there was already patches in 4.2.0 release)
> > > > This is pretty close to ready. It needs some testing though. I'll
> > > > try to
> > > get a set of tests carved
> > > > out by the end of the week. For 4.3.0 this will be disabled by
> > > > default in
> > > any case.
> > >
> > > [fpj] What's the jira or umbrella jira for this one?
> > BOOKKEEPER-432
> >
> > -Ivan
> >
> >
>
>
RE: [DISCUSS] Release 4.3.0
Posted by Flavio Junqueira <fp...@yahoo.com>.
I also would rather releases sooner, but we need to reach agreement on what
the release will contain. The release manager essentially decides where to
cut. Do we have a release manager for 4.3.0 already or that is still open?
For 4.3.0, we have promised security for release 4.3.0, so I think we need
to have at least that. Some of the other features, like 592, are ready to
get in, so we don't expect them to be in the way. The other jiras depend on
the reporters to stepping up and saying if they need to be in and find
someone to wrap up the work.
As for having 4.2.2, we tend to use the last digit for bug fix releases,
perhaps including some updates. This next release will have more than bug
fixes.
It sounds like you'd like us to have a release sooner, yes?
-Flavio
----Original Message-----
From: Whitney Sorenson [mailto:wsorenson@hubspot.com]
Sent: 23 May 2013 15:30
To: bookkeeper-dev@zookeeper.apache.org
Subject: Re: [DISCUSS] Release 4.3.0
As an outside stakeholder, I am curious if anyone has considered dividing up
these releases since there hasn't been a release in a while.
For the sake of shipping something sooner rather than continuing to append
new features and ideas, what do you guys think about doing a 4.2.2 as an
intermediate?
If it's an unreasonable suggestion, I understand completely.
-Whitney
On Thu, May 23, 2013 at 6:49 AM, Flavio Junqueira
<fp...@yahoo.com>wrote:
> This is a summary according to my understanding of the discussion so far:
>
> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
> BOOKKEEPER-XXX: Provide support for bookie authentication
> BOOKKEEPER-390: Provide support for zookeeper authentication
> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
> characters max, which fundamentally limits them at 9 billion
> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
> BOOKKEEPER-592: allow application to recommend ledger data locality
> (ready to go)
> BOOKKEEPER-432: Improve performance of entry log range read per ledger
> entries
> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
>
> Are these the core jiras we need to resolve for 4.3.0?
>
> -Flavio
>
> -----Original Message-----
> From: Ivan Kelly [mailto:ivank@apache.org]
> Sent: 22 May 2013 14:43
> To: bookkeeper-dev@zookeeper.apache.org
> Subject: Re: [DISCUSS] Release 4.3.0
>
> >
> > [fpj] Is there a jira for the SASL work? Do happen to know all jiras
> > related to security we need to address?
> There's no JIRA for sasl or auth yet. SSL is
> https://issues.apache.org/jira/browse/BOOKKEEPER-575
>
> > > > - skiplist based ledger storage and other improvements on bookie
> server
> > > > side (there was already patches in 4.2.0 release)
> > > This is pretty close to ready. It needs some testing though. I'll
> > > try to
> > get a set of tests carved
> > > out by the end of the week. For 4.3.0 this will be disabled by
> > > default in
> > any case.
> >
> > [fpj] What's the jira or umbrella jira for this one?
> BOOKKEEPER-432
>
> -Ivan
>
>
Re: [DISCUSS] Release 4.3.0
Posted by Whitney Sorenson <ws...@hubspot.com>.
As an outside stakeholder, I am curious if anyone has considered dividing
up these releases since there hasn't been a release in a while.
For the sake of shipping something sooner rather than continuing to append
new features and ideas, what do you guys think about doing a 4.2.2 as an
intermediate?
If it's an unreasonable suggestion, I understand completely.
-Whitney
On Thu, May 23, 2013 at 6:49 AM, Flavio Junqueira <fp...@yahoo.com>wrote:
> This is a summary according to my understanding of the discussion so far:
>
> BOOKKEEPER-575: Bookie SSL support (umbrella jira)
> BOOKKEEPER-XXX: Provide support for bookie authentication
> BOOKKEEPER-390: Provide support for zookeeper authentication
> BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
> characters max, which fundamentally limits them at 9 billion
> BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
> BOOKKEEPER-592: allow application to recommend ledger data locality (ready
> to go)
> BOOKKEEPER-432: Improve performance of entry log range read per ledger
> entries
> BOOKKEEPER-220: Managed ledger (optional, but nice to have)
>
> Are these the core jiras we need to resolve for 4.3.0?
>
> -Flavio
>
> -----Original Message-----
> From: Ivan Kelly [mailto:ivank@apache.org]
> Sent: 22 May 2013 14:43
> To: bookkeeper-dev@zookeeper.apache.org
> Subject: Re: [DISCUSS] Release 4.3.0
>
> >
> > [fpj] Is there a jira for the SASL work? Do happen to know all jiras
> > related to security we need to address?
> There's no JIRA for sasl or auth yet. SSL is
> https://issues.apache.org/jira/browse/BOOKKEEPER-575
>
> > > > - skiplist based ledger storage and other improvements on bookie
> server
> > > > side (there was already patches in 4.2.0 release)
> > > This is pretty close to ready. It needs some testing though. I'll
> > > try to
> > get a set of tests carved
> > > out by the end of the week. For 4.3.0 this will be disabled by
> > > default in
> > any case.
> >
> > [fpj] What's the jira or umbrella jira for this one?
> BOOKKEEPER-432
>
> -Ivan
>
>
RE: [DISCUSS] Release 4.3.0
Posted by Flavio Junqueira <fp...@yahoo.com>.
This is a summary according to my understanding of the discussion so far:
BOOKKEEPER-575: Bookie SSL support (umbrella jira)
BOOKKEEPER-XXX: Provide support for bookie authentication
BOOKKEEPER-390: Provide support for zookeeper authentication
BOOKKEEPER-421: ledger ids are long, but they are stored in zk as 10
characters max, which fundamentally limits them at 9 billion
BOOKKEEPER-590: Another Scan-And-Compare GC Implementation
BOOKKEEPER-592: allow application to recommend ledger data locality (ready
to go)
BOOKKEEPER-432: Improve performance of entry log range read per ledger
entries
BOOKKEEPER-220: Managed ledger (optional, but nice to have)
Are these the core jiras we need to resolve for 4.3.0?
-Flavio
-----Original Message-----
From: Ivan Kelly [mailto:ivank@apache.org]
Sent: 22 May 2013 14:43
To: bookkeeper-dev@zookeeper.apache.org
Subject: Re: [DISCUSS] Release 4.3.0
>
> [fpj] Is there a jira for the SASL work? Do happen to know all jiras
> related to security we need to address?
There's no JIRA for sasl or auth yet. SSL is
https://issues.apache.org/jira/browse/BOOKKEEPER-575
> > > - skiplist based ledger storage and other improvements on bookie
server
> > > side (there was already patches in 4.2.0 release)
> > This is pretty close to ready. It needs some testing though. I'll
> > try to
> get a set of tests carved
> > out by the end of the week. For 4.3.0 this will be disabled by
> > default in
> any case.
>
> [fpj] What's the jira or umbrella jira for this one?
BOOKKEEPER-432
-Ivan
Re: [DISCUSS] Release 4.3.0
Posted by Ivan Kelly <iv...@apache.org>.
>
> [fpj] Is there a jira for the SASL work? Do happen to know all jiras related
> to security we need to address?
There's no JIRA for sasl or auth yet. SSL is
https://issues.apache.org/jira/browse/BOOKKEEPER-575
> > > - skiplist based ledger storage and other improvements on bookie server
> > > side (there was already patches in 4.2.0 release)
> > This is pretty close to ready. It needs some testing though. I'll try to
> get a set of tests carved
> > out by the end of the week. For 4.3.0 this will be disabled by default in
> any case.
>
> [fpj] What's the jira or umbrella jira for this one?
BOOKKEEPER-432
-Ivan
RE: [DISCUSS] Release 4.3.0
Posted by FPJ <fp...@yahoo.com>.
In general, it would be nice to have at least one person on any major issue
we promise for 4.3.0. More inline:
-----Original Message-----
From: Ivan Kelly [mailto:ivank@apache.org]
Sent: 22 May 2013 11:36
To: bookkeeper-dev@zookeeper.apache.org
Subject: Re: [DISCUSS] Release 4.3.0
> > * Security (SASL on bookie)
> SASL != SSL. There's a patch for SSL[1] already but we need to get the
protobuf changes
> in beforehand, and then the SSL patch will need to be reworked. I don't
plan to come back
> to this until the skiplist stuff is in.
>
> The SASL stuff is somewhat independent of SSL but it too will require
protobuf. There's
> already a bookie level auth patch[2], which will need to be reworked.
>
> Then there's Rakesh's patch which is about security in the metadata level.
This needs to
> be made not depend on zk. We also need to figure it out.
[fpj] Is there a jira for the SASL work? Do happen to know all jiras related
to security we need to address?
> > The rack awareness work was not marked for this release, but I suppose
> > it is ok to include it here, since the patch Sijie proposed for
> > BOOKKEEPER-592 seems to be in good shape.
> I need to look at the latest BOOKKEEPER-592, but I think this is pretty
much ready to go.
[fpj] Agreed.
> > - skiplist based ledger storage and other improvements on bookie server
> > side (there was already patches in 4.2.0 release)
> This is pretty close to ready. It needs some testing though. I'll try to
get a set of tests carved
> out by the end of the week. For 4.3.0 this will be disabled by default in
any case.
[fpj] What's the jira or umbrella jira for this one?
> > - gc improvement (this is also left from 4.2.0)
> > - ledger id generation improvements (those patches made by Jiannan also
> > exists for a long time)
> I think these patches are almost there, we just need to refine them a
little.
[fpj] I'm ok with considering them for now, and I'm taking it as that there
are people still interested in these improvements.
> > - managed ledger (it also exists from 4.1.0)
> For me, this isn't super important for 4.3.0. I would prefer to have the
metadata issue solved
> (we're working on a prototype here) before putting it in also, as the mark
is stored in a separate
> ledger at the moment.
[fpj] Matteo is the one driving it and it is a separate module, so if he is
able to produce a patch we can commit, I don't mind having it in.
> > Any thoughts about cutting a release say by mid-june?
> I think mid-june is very optimistic to get all this in. Perhaps end of
july.
[fpj] As the list has grown since last night, I tend to agree that mid-june
is very optimistic. It is about time to have a release, though.
> Another thing, somewhat related to the skiplist stuff, though in a round
about way, is stats/metrics.
> The twitter guys have the beginnings of an generic interface for this,
which I used as a basis for
> sketching out a fuller interface last week [3]. We can plug twitter stats
or ostrich or codahale's
> metrics into this. I've already implemented a Twitter provider. This is a
separate discussion though,
> and it needs a lot of refinement.
>
> However, it is something I'd like to get into 4.3.0 so stuff can be easier
measured.
[fpj] I'm ok with giving it a try, but right now it is sounding too much and
we might consider leaving some stuff out later on. I would appreciate if you
could mark jiras accordingly.
> -Ivan
>
> [1] https://github.com/ivankelly/bookkeeper/tree/ssl
> [2] https://github.com/ivankelly/bookkeeper/tree/BookKeeperAuth
> [3]
https://github.com/ivankelly/bookkeeper/commit/fc765706949766e796e43e62a9692
9a997a6f0f7
Re: [DISCUSS] Release 4.3.0
Posted by Ivan Kelly <iv...@apache.org>.
> * Security (SASL on bookie)
SASL != SSL. There's a patch for SSL[1] already but we need to get the
protobuf changes in beforehand, and then the SSL patch will need to be
reworked. I don't plan to come back to this until the skiplist stuff
is in.
The SASL stuff is somewhat independent of SSL but it too will require
protobuf. There's already a bookie level auth patch[2], which will need
to be reworked.
Then there's Rakesh's patch which is about security in the
metadata level. This needs to be made not depend on zk. We also need
to figure it out.
> The rack awareness work was not marked for this release, but I suppose it is
> ok to include it here, since the patch Sijie proposed for BOOKKEEPER-592
> seems to be in good shape.
I need to look at the latest BOOKKEEPER-592, but I think this is
pretty much ready to go.
> - skiplist based ledger storage and other improvements on bookie server
> side (there was already patches in 4.2.0 release)
This is pretty close to ready. It needs some testing though. I'll try
to get a set of tests carved out by the end of the week. For 4.3.0
this will be disabled by default in any case.
> - gc improvement (this is also left from 4.2.0)
> - ledger id generation improvements (those patches made by Jiannan also
> exists for a long time)
I think these patches are almost there, we just need to refine them a
little.
> - managed ledger (it also exists from 4.1.0)
For me, this isn't super important for 4.3.0. I would prefer to have
the metadata issue solved (we're working on a prototype here) before
putting it in also, as the mark is stored in a separate ledger at the
moment.
> Any thoughts about cutting a release say by mid-june?
I think mid-june is very optimistic to get all this in. Perhaps end of july.
Another thing, somewhat related to the skiplist stuff, though in a
round about way, is stats/metrics. The twitter guys have the
beginnings of an generic interface for this, which I used as a basis
for sketching out a fuller interface last week [3]. We can plug
twitter stats or ostrich or codahale's metrics into this. I've already
implemented a Twitter provider. This is a separate discussion though,
and it needs a lot of refinement.
However, it is something I'd like to get into 4.3.0 so stuff can be
easier measured.
-Ivan
[1] https://github.com/ivankelly/bookkeeper/tree/ssl
[2] https://github.com/ivankelly/bookkeeper/tree/BookKeeperAuth
[3] https://github.com/ivankelly/bookkeeper/commit/fc765706949766e796e43e62a96929a997a6f0f7
Re: [DISCUSS] Release 4.3.0
Posted by Flavio Junqueira <fp...@yahoo.com>.
Thanks for feedback, Sijie. In principle, I don't have a problem with adding any of the points you mention below, but see some comments inline:
On May 22, 2013, at 7:09 AM, Sijie Guo <gu...@gmail.com> wrote:
> I think there are bunch of things left from 4.2.0 needs to be in 4.3.0.
>
> - skiplist based ledger storage and other improvements on bookie server
> side (there was already patches in 4.2.0 release)
I haven't followed the progress here very closely. How close to you think this is of getting into trunk?
> - gc improvement (this is also left from 4.2.0)
> - ledger id generation improvements (those patches made by Jiannan also
> exists for a long time)
I have to look at those jiras, but my recollection is that we haven't converged into a solution. Also, who is going to wrap them up?
> - managed ledger (it also exists from 4.1.0)
I also haven't seen a lot of progress with that patch, so I'm reluctant to depend upon that work for the release.
What do you think?
-Flavio
>
> -Sijie
>
>
>
> On Tue, May 21, 2013 at 5:07 PM, Flavio Junqueira <fp...@yahoo.com>wrote:
>
>> It is probably time to start thinking about wrapping up 4.3.0. There are 77
>> jiras marked for 4.3.0 and we have considered for this release the
>> following
>> features:
>>
>> * Security (SASL on bookie)
>> * NIOServerFactory -> Netty
>>
>> The rack awareness work was not marked for this release, but I suppose it
>> is
>> ok to include it here, since the patch Sijie proposed for BOOKKEEPER-592
>> seems to be in good shape. The Netty work is in BOOKKEEPER-555, which is in
>> already. We just need to work on the security part, which I think there has
>> been some progress recently. At least I have seen some progress from
>> Rakesh.
>>
>>
>>
>> Any thoughts about cutting a release say by mid-june?
>>
>>
>>
>> -Flavio
>>
>>
Re: [DISCUSS] Release 4.3.0
Posted by Sijie Guo <gu...@gmail.com>.
I think there are bunch of things left from 4.2.0 needs to be in 4.3.0.
- skiplist based ledger storage and other improvements on bookie server
side (there was already patches in 4.2.0 release)
- gc improvement (this is also left from 4.2.0)
- ledger id generation improvements (those patches made by Jiannan also
exists for a long time)
- managed ledger (it also exists from 4.1.0)
-Sijie
On Tue, May 21, 2013 at 5:07 PM, Flavio Junqueira <fp...@yahoo.com>wrote:
> It is probably time to start thinking about wrapping up 4.3.0. There are 77
> jiras marked for 4.3.0 and we have considered for this release the
> following
> features:
>
> * Security (SASL on bookie)
> * NIOServerFactory -> Netty
>
> The rack awareness work was not marked for this release, but I suppose it
> is
> ok to include it here, since the patch Sijie proposed for BOOKKEEPER-592
> seems to be in good shape. The Netty work is in BOOKKEEPER-555, which is in
> already. We just need to work on the security part, which I think there has
> been some progress recently. At least I have seen some progress from
> Rakesh.
>
>
>
> Any thoughts about cutting a release say by mid-june?
>
>
>
> -Flavio
>
>