Re: PIP 20: Mechanism to revoke TLS authentication

> Instead of using zookeeper, can we consider using a managed ledger or a system topic for keeping all these revoked keys? Do we already have an example of a system topic in use? Is there a custom namespace that's restricted to the admin role? -Ivan

Re: PIP 20: Mechanism to revoke TLS authentication

> Here, we would like to configure "subject-key-identifier" at every broker in the cluster dynamically. We also want to perform certain actions once this configuration-value has been changed. Ah, i didn't know this existed. Very useful. I will consider both this and system topics and update the PI

Re: PIP 20: Mechanism to revoke TLS authentication

On Mon, Aug 20, 2018 at 5:59 AM Ivan Kelly wrote: > > Instead of using zookeeper, can we consider using a managed ledger or a > system topic for keeping all these revoked keys? > > Do we already have an example of a system topic in use? Functions is using system topics. And all its topics are u

Jenkins build is still unstable: pulsar-master #727

See

Re: Planning for Pulsar 2.2 release

Anyone volunteer for releasing 2.2? - Sijie On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo wrote: > Any committer volunteer for releasing 2.2? > > - Sijie > > On Wed, Aug 8, 2018 at 11:43 AM Sanjeev Kulkarni > wrote: > >> The timeline sounds good! >> One more thing that users have asked about is f

Re: Planning for Pulsar 2.2 release

I will volunteer. -Ali On Mon, Aug 20, 2018 at 2:45 PM Sijie Guo wrote: > Anyone volunteer for releasing 2.2? > > - Sijie > > On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo wrote: > > > Any committer volunteer for releasing 2.2? > > > > - Sijie > > > > On Wed, Aug 8, 2018 at 11:43 AM Sanjeev Kulka

Re: Planning for Pulsar 2.2 release

Ok if no one else is there i will take this Joe On Mon, Aug 20, 2018, 2:45 PM Sijie Guo wrote: > Anyone volunteer for releasing 2.2? > > - Sijie > > On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo wrote: > > > Any committer volunteer for releasing 2.2? > > > > - Sijie > > > > On Wed, Aug 8, 2018 at

Re: Planning for Pulsar 2.2 release

Thank you Ali. However the release manager has be an Apache committer first, since it requires permissions to access ASF infrastructure for the whole release process. - Sijie On Mon, Aug 20, 2018 at 2:50 PM Ali Ahmed wrote: > I will volunteer. > > -Ali > > On Mon, Aug 20, 2018 at 2:45 PM Sijie

Re: Planning for Pulsar 2.2 release

Thank you Joe! :) - Sijie On Mon, Aug 20, 2018 at 2:51 PM Joe F wrote: > Ok if no one else is there i will take this > > Joe > > On Mon, Aug 20, 2018, 2:45 PM Sijie Guo wrote: > > > Anyone volunteer for releasing 2.2? > > > > - Sijie > > > > On Thu, Aug 16, 2018 at 12:02 AM Sijie Guo wrote: >

Re: PIP 20: Mechanism to revoke TLS authentication

> I will consider both this and system topics and update the PIP. I think we should avoid more complexity by introducing system topic to store "subject key" and then process it. Instead we can store it to global/config zk as it requires to store keys with few bytes. I think dynamic-configuration m

Jenkins build is unstable: pulsar-master #729

See