Re: initial draft of security scoping document/roadmap
Fixed link: https://docs.google.com/document/d/1Yu4iuIhaERwug1vS95yWDd_WzrNRIKvvVGUb31y-_mY/edit# -Will On Mon, Oct 17, 2016 at 9:42 PM, Dan Burkert wrote: > Hi all, > > We've been thinking about some of the particular details laid out in the > scope doc, and have come up with some alternatives. You can see the > alternative and discussion here: > > https://docs.google.com/document/d/1Yu4iuIhaERwug1vS95yWDd_ > WzrNRIKvvVGUb31y-_mY/edit# > > - Dan > > On Mon, Oct 10, 2016 at 9:07 PM, Todd Lipcon wrote: > > > Hey folks, > > > > I'm hoping to start breaking down some tasks from this document in the > next > > couple days. If you were planning to take a look, please try to do so > soon. > > > > -Todd > > > > On Mon, Oct 3, 2016 at 5:33 PM, Todd Lipcon wrote: > > > > > Hi all, > > > > > > Now that we've reached 1.0, one of the next big barriers to Kudu > adoption > > > is its lack of security features. I've started working on a document > > which > > > tries to scope out some initial support for authentication, > > authorization, > > > and data security: > > > > > > https://docs.google.com/document/d/1cPNDTpVkIUo676RlszpTF1gHZ8l0T > > > dbB7zFBAuOuYUw/edit#heading=h.gsibhnd5dyem > > > > > > The aim here is to lay out a roadmap that has some milestones that are > > > achievable in the next few upcoming releases. As noted in the last > > section > > > of the document, there will be more work to follow, but the goal here > is > > to > > > get us started with the base infrastructure. > > > > > > It's rough, yet, but please take a look and leave comments, questions, > > and > > > suggestions. > > > > > > Thanks > > > -Todd > > > -- > > > Todd Lipcon > > > Software Engineer, Cloudera > > > > > > > > > > > -- > > Todd Lipcon > > Software Engineer, Cloudera > > >
Re: initial draft of security scoping document/roadmap
Hi all, We've been thinking about some of the particular details laid out in the scope doc, and have come up with some alternatives. You can see the alternative and discussion here: https://docs.google.com/document/d/1Yu4iuIhaERwug1vS95yWDd_ WzrNRIKvvVGUb31y-_mY/edit# - Dan On Mon, Oct 10, 2016 at 9:07 PM, Todd Lipcon wrote: > Hey folks, > > I'm hoping to start breaking down some tasks from this document in the next > couple days. If you were planning to take a look, please try to do so soon. > > -Todd > > On Mon, Oct 3, 2016 at 5:33 PM, Todd Lipcon wrote: > > > Hi all, > > > > Now that we've reached 1.0, one of the next big barriers to Kudu adoption > > is its lack of security features. I've started working on a document > which > > tries to scope out some initial support for authentication, > authorization, > > and data security: > > > > https://docs.google.com/document/d/1cPNDTpVkIUo676RlszpTF1gHZ8l0T > > dbB7zFBAuOuYUw/edit#heading=h.gsibhnd5dyem > > > > The aim here is to lay out a roadmap that has some milestones that are > > achievable in the next few upcoming releases. As noted in the last > section > > of the document, there will be more work to follow, but the goal here is > to > > get us started with the base infrastructure. > > > > It's rough, yet, but please take a look and leave comments, questions, > and > > suggestions. > > > > Thanks > > -Todd > > -- > > Todd Lipcon > > Software Engineer, Cloudera > > > > > > -- > Todd Lipcon > Software Engineer, Cloudera >
Re: Plan for upcoming releases
Sounds good to me, thanks for volunteering. - Dan On Mon, Oct 17, 2016 at 5:27 PM, Jordan Birdsell wrote: > Seems reasonable to me, have a few things for Python left I'd like to get > in for 1.1: range partition implementation and alter table capabilities, > that should be enough time. > > Thanks Todd, > Jordan > > On Mon, Oct 17, 2016, 8:23 PM Todd Lipcon wrote: > > > Hey folks, > > > > I'd like to propose a release plan for the next few months. > > > > My suggestion is that we aim for Kudu 1.1 some time around mid-November > -- > > hopefully with enough time before Thanksgiving that no one here in the US > > needs to worry about an impending release over the holiday. So, I think > > that would be some time the week of 11/14. > > > > That gives us a month from now to make some progress on in-flight > features > > and fixes. My preference is that this should be a time-based rather than > > scope-based release, but I expect that some of the items that people are > > working on should be ready by then. Speaking for myself, the pre-election > > patch series can improve stability significantly in some cases and it > will > > be great to get that out to our users. I'm sure others have improvements > > pending that will be ready by then too. > > > > Following 1.1, I think we should plan for a 1.2 release early in January > > (6-8 weeks after 1.1). My hope is that we can get a good chunk of the > > security features that folks have started looking at done by then, as > well > > as various other work that people have been circulating design docs for. > > > > I'll also volunteer to RM these two releases. > > > > Thanks > > -Todd > > -- > > Todd Lipcon > > Software Engineer, Cloudera > > >
Re: Plan for upcoming releases
Seems reasonable to me, have a few things for Python left I'd like to get in for 1.1: range partition implementation and alter table capabilities, that should be enough time. Thanks Todd, Jordan On Mon, Oct 17, 2016, 8:23 PM Todd Lipcon wrote: > Hey folks, > > I'd like to propose a release plan for the next few months. > > My suggestion is that we aim for Kudu 1.1 some time around mid-November -- > hopefully with enough time before Thanksgiving that no one here in the US > needs to worry about an impending release over the holiday. So, I think > that would be some time the week of 11/14. > > That gives us a month from now to make some progress on in-flight features > and fixes. My preference is that this should be a time-based rather than > scope-based release, but I expect that some of the items that people are > working on should be ready by then. Speaking for myself, the pre-election > patch series can improve stability significantly in some cases and it will > be great to get that out to our users. I'm sure others have improvements > pending that will be ready by then too. > > Following 1.1, I think we should plan for a 1.2 release early in January > (6-8 weeks after 1.1). My hope is that we can get a good chunk of the > security features that folks have started looking at done by then, as well > as various other work that people have been circulating design docs for. > > I'll also volunteer to RM these two releases. > > Thanks > -Todd > -- > Todd Lipcon > Software Engineer, Cloudera >
Plan for upcoming releases
Hey folks, I'd like to propose a release plan for the next few months. My suggestion is that we aim for Kudu 1.1 some time around mid-November -- hopefully with enough time before Thanksgiving that no one here in the US needs to worry about an impending release over the holiday. So, I think that would be some time the week of 11/14. That gives us a month from now to make some progress on in-flight features and fixes. My preference is that this should be a time-based rather than scope-based release, but I expect that some of the items that people are working on should be ready by then. Speaking for myself, the pre-election patch series can improve stability significantly in some cases and it will be great to get that out to our users. I'm sure others have improvements pending that will be ready by then too. Following 1.1, I think we should plan for a 1.2 release early in January (6-8 weeks after 1.1). My hope is that we can get a good chunk of the security features that folks have started looking at done by then, as well as various other work that people have been circulating design docs for. I'll also volunteer to RM these two releases. Thanks -Todd -- Todd Lipcon Software Engineer, Cloudera
