You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Jason Brown <ja...@gmail.com> on 2018/12/18 13:47:39 UTC
Re: Proposing an Apache Cassandra Management process
It looks like we have consensus to move forward with the sidecar
I will be shepherding the project, and to that end, I'll create a repo
against which we can start working.
Thanks,
-Jason
On Fri, Nov 30, 2018 at 7:54 AM sankalp kohli <ko...@gmail.com>
wrote:
> If no one has more feedback, we should create JIRAs for all the subtasks
> discussed in the proposal. I can see JIRA for Bulk command but not others.
>
> On Mon, Nov 19, 2018 at 2:12 AM dinesh.joshi@yahoo.com.INVALID
> <di...@yahoo.com.invalid> wrote:
>
> > Thanks, Mick & Stefan for your inputs. What should we do as next steps to
> > move this proposal forward?
> > Dinesh
> >
> > On Sunday, November 18, 2018, 11:57:54 AM PST, Stefan Podkowinski <
> > spod@apache.org> wrote:
> >
> > My goal for a side car would be to enable more people to contribute to
> > the project, by making it more accessible for anyone who’s not familiar
> > with the Cassandra code base, or not familiar with Java development in
> > general. Although most of the functionality described in the proposal
> > sounds useful to have, I’d already be happy to have a solid REST API for
> > the existing nodetool and JMX functionality. If an official side car,
> > installed separately on each node, would provide that, I’m sure we’d see
> > lots of new tools created by the community (web UIs, cli tools, ..)
> > based on that. This would also be a good foundation for other existing
> > tool to converge upon, e.g. by calling the REST APIs for repair
> > scheduling and progress tracking instead of JMX, or by continually
> > integrating and sharing useful helper calls. This would also give
> > Cassandra devs more leeway to replace some of the existing tooling
> > related code in Cassandra, e.g. by migrating to virtual tables, while at
> > the same time keep providing a stable API through the side car.
> >
> > What I’d also like to point out here is that implementing such a project
> > as an *official* side car, also implies to me having the same standards
> > when it comes to release quality. I’d also really prefer having feature
> > sets matching between Cassandra and the side car, e.g. authentication
> > and SSL should also be supported in the side car from the beginning,
> > ideally without any additional configuration.
> >
> >
> > On 06.11.18 10:40, Dinesh Joshi wrote:
> > > Hi all,
> > >
> > > Joey, Vinay & I have fleshed out the Management process proposal as the
> > very first CIP document (with Jason’s inputs). It is available on the
> cwiki
> > -
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652224
> > >
> > > Please comment on it and provide us any input that you may have. We
> want
> > to ideally time-box the period to 2 weeks so we avoid waiting
> indefinitely.
> > >
> > > Thanks,
> > >
> > > Dinesh
> > >
> > >> On Oct 22, 2018, at 7:30 AM, "dinesh.joshi@yahoo.com.INVALID" <
> > dinesh.joshi@yahoo.com.INVALID> wrote:
> > >>
> > >> Thanks for starting this, Mick. I will flesh it out.
> > >> Dinesh
> > >>
> > >> On Sunday, October 21, 2018, 1:52:10 AM PDT, Mick Semb Wever <
> > mck@apache.org> wrote:
> > >>
> > >>
> > >>> But I'll try to put together a strawman proposal for the doc(s) over
> > the
> > >>> weekend.
> > >>
> > >> I've thrown something quickly together here:
> > >> -
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201
> > >> -
> >
> https://cwiki.apache.org/confluence/display/CASSANDRA/CIP-1%3A+Proposing+an+Apache+Cassandra+Management+process
> > >>
> > >> The former is a blatant rip-off from the Kafka and Spark design
> > proposal pages that Dinesh previously mentioned. I'd hoped to do more of
> an
> > analysis of the existing C* habits and precedence on design proposals
> > (implicit in jira tickets), but in lei of that this is a strawman to
> start
> > the discussion.
> > >>
> > >> The latter still needs to be fleshed out. Dinesh, can you do this? I
> > can add a subpage/section that describes the alternative/consuming
> > third-party tools out there.
> > >>
> > >> regards,
> > >> Mick
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > >> For additional commands, e-mail: dev-help@cassandra.apache.org
> > >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >
>
Re: Proposing an Apache Cassandra Management process
Posted by Dinesh Joshi <di...@yahoo.com.INVALID>.
Thanks, Jason!
Dinesh
> On Dec 18, 2018, at 5:47 AM, Jason Brown <ja...@gmail.com> wrote:
>
> It looks like we have consensus to move forward with the sidecar
> I will be shepherding the project, and to that end, I'll create a repo against which we can start working.
>
> Thanks,
>
> -Jason
>
>> On Fri, Nov 30, 2018 at 7:54 AM sankalp kohli <ko...@gmail.com> wrote:
>> If no one has more feedback, we should create JIRAs for all the subtasks
>> discussed in the proposal. I can see JIRA for Bulk command but not others.
>>
>> On Mon, Nov 19, 2018 at 2:12 AM dinesh.joshi@yahoo.com.INVALID
>> <di...@yahoo.com.invalid> wrote:
>>
>> > Thanks, Mick & Stefan for your inputs. What should we do as next steps to
>> > move this proposal forward?
>> > Dinesh
>> >
>> > On Sunday, November 18, 2018, 11:57:54 AM PST, Stefan Podkowinski <
>> > spod@apache.org> wrote:
>> >
>> > My goal for a side car would be to enable more people to contribute to
>> > the project, by making it more accessible for anyone who’s not familiar
>> > with the Cassandra code base, or not familiar with Java development in
>> > general. Although most of the functionality described in the proposal
>> > sounds useful to have, I’d already be happy to have a solid REST API for
>> > the existing nodetool and JMX functionality. If an official side car,
>> > installed separately on each node, would provide that, I’m sure we’d see
>> > lots of new tools created by the community (web UIs, cli tools, ..)
>> > based on that. This would also be a good foundation for other existing
>> > tool to converge upon, e.g. by calling the REST APIs for repair
>> > scheduling and progress tracking instead of JMX, or by continually
>> > integrating and sharing useful helper calls. This would also give
>> > Cassandra devs more leeway to replace some of the existing tooling
>> > related code in Cassandra, e.g. by migrating to virtual tables, while at
>> > the same time keep providing a stable API through the side car.
>> >
>> > What I’d also like to point out here is that implementing such a project
>> > as an *official* side car, also implies to me having the same standards
>> > when it comes to release quality. I’d also really prefer having feature
>> > sets matching between Cassandra and the side car, e.g. authentication
>> > and SSL should also be supported in the side car from the beginning,
>> > ideally without any additional configuration.
>> >
>> >
>> > On 06.11.18 10:40, Dinesh Joshi wrote:
>> > > Hi all,
>> > >
>> > > Joey, Vinay & I have fleshed out the Management process proposal as the
>> > very first CIP document (with Jason’s inputs). It is available on the cwiki
>> > -
>> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652224
>> > >
>> > > Please comment on it and provide us any input that you may have. We want
>> > to ideally time-box the period to 2 weeks so we avoid waiting indefinitely.
>> > >
>> > > Thanks,
>> > >
>> > > Dinesh
>> > >
>> > >> On Oct 22, 2018, at 7:30 AM, "dinesh.joshi@yahoo.com.INVALID" <
>> > dinesh.joshi@yahoo.com.INVALID> wrote:
>> > >>
>> > >> Thanks for starting this, Mick. I will flesh it out.
>> > >> Dinesh
>> > >>
>> > >> On Sunday, October 21, 2018, 1:52:10 AM PDT, Mick Semb Wever <
>> > mck@apache.org> wrote:
>> > >>
>> > >>
>> > >>> But I'll try to put together a strawman proposal for the doc(s) over
>> > the
>> > >>> weekend.
>> > >>
>> > >> I've thrown something quickly together here:
>> > >> -
>> > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201
>> > >> -
>> > https://cwiki.apache.org/confluence/display/CASSANDRA/CIP-1%3A+Proposing+an+Apache+Cassandra+Management+process
>> > >>
>> > >> The former is a blatant rip-off from the Kafka and Spark design
>> > proposal pages that Dinesh previously mentioned. I'd hoped to do more of an
>> > analysis of the existing C* habits and precedence on design proposals
>> > (implicit in jira tickets), but in lei of that this is a strawman to start
>> > the discussion.
>> > >>
>> > >> The latter still needs to be fleshed out. Dinesh, can you do this? I
>> > can add a subpage/section that describes the alternative/consuming
>> > third-party tools out there.
>> > >>
>> > >> regards,
>> > >> Mick
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> > >> For additional commands, e-mail: dev-help@cassandra.apache.org
>> > >>
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
>> > For additional commands, e-mail: dev-help@cassandra.apache.org
>> >
>> >