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:[email protected]] Sent: 22 May 2013 11:36 To: [email protected] 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
