Michael, The ssl work in now being done in https://issues.apache.org/jira/browse/KAFKA-1690. It would be great if you can help review it too. Also updated the top level security jira accordingly.
Thanks, Jun On Wed, May 13, 2015 at 11:23 AM, Michael Herstine < mherst...@linkedin.com.invalid> wrote: > Regarding the SSL code‹ is there an RB available? I don¹t see a recent > patch uploaded to https://issues.apache.org/jira/browse/KAFKA-1684Š How > can other folks see the code? > > On 5/12/15, 12:07 PM, "Gwen Shapira" <gshap...@cloudera.com> wrote: > > >My notes from the hangout: > > > >* KIP-11: Based on feedback from Joel - group privileges will become READ. > >Parth will open a new thread with a summary and re-open the vote. > > > >* Updated that I¹m still working on KAFKA-1928, Jay clarified that some of > >the assertions may no longer be valid, but we should add the ones that > >make > >sense > > > >* Harsha asked for review of SSL code, Jun will pick it up. > > > >* KIP-19: Even though using MetaData timeout for requests is confusing, it > >makes sense to use for data still in accumulator when leader is not > >available. Request timeout will be used for data out of accumulator. > >Configuration should tie replication timeout and request timeout together > >by default, to simplify. Also validate that request timeout is longer than > >replication timeout. We need reasonable default values as well. Long > >discussion on names of parameters. Guozhang will summarize issues > >identified - mainly around retries. > > > >* KIP-21: We will go with hybrid approach - server configuration will > >remain in files and static (i.e. no SIGHUP), dynamic entities (topic, > >clients, users, whatever) can have overrides in ZK. Aditya will update KIP > >with details. > > > >As usual, correct me if I got it wrong! > > > >Gwen > >
