Re: [VOTE] Change Jira Workflow

[Sylvain Lebresne]

+1
--
Sylvain


On Tue, Dec 18, 2018 at 9:34 AM Oleksandr Petrov 
wrote:

> +1
>
> On Mon, Dec 17, 2018 at 7:12 PM Nate McCall  wrote:
> >
> > On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith
> >  wrote:
> > >
> > > I propose these changes <
> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals>*
> to the Jira Workflow for the project.  The vote will be open for 72 hours**.
> > >
> >
> >
> > +1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
>
>
> --
> alex p
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] Change Jira Workflow

[Oleksandr Petrov]

+1

On Mon, Dec 17, 2018 at 7:12 PM Nate McCall  wrote:
>
> On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith
>  wrote:
> >
> > I propose these changes 
> > *
> >  to the Jira Workflow for the project.  The vote will be open for 72 
> > hours**.
> >
>
>
> +1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>


-- 
alex p

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Change Jira Workflow

[Joseph Lynch]

+1 non-binding

On Tue, Dec 18, 2018 at 1:15 AM Sylvain Lebresne  wrote:

> +1
> --
> Sylvain
>
>
> On Tue, Dec 18, 2018 at 9:34 AM Oleksandr Petrov <
> oleksandr.pet...@gmail.com>
> wrote:
>
> > +1
> >
> > On Mon, Dec 17, 2018 at 7:12 PM Nate McCall  wrote:
> > >
> > > On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith
> > >  wrote:
> > > >
> > > > I propose these changes <
> >
> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals
> >*
> > to the Jira Workflow for the project.  The vote will be open for 72
> hours**.
> > > >
> > >
> > >
> > > +1
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >
> >
> >
> > --
> > alex p
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: [VOTE] Change Jira Workflow

[Aleksey Yeshchenko]

Sure, +1

> On 18 Dec 2018, at 09:42, Joseph Lynch  wrote:
> 
> +1 non-binding
> 
> On Tue, Dec 18, 2018 at 1:15 AM Sylvain Lebresne  wrote:
> 
>> +1
>> --
>> Sylvain
>> 
>> 
>> On Tue, Dec 18, 2018 at 9:34 AM Oleksandr Petrov <
>> oleksandr.pet...@gmail.com>
>> wrote:
>> 
>>> +1
>>> 
>>> On Mon, Dec 17, 2018 at 7:12 PM Nate McCall  wrote:
 
 On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith
  wrote:
> 
> I propose these changes <
>>> 
>> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals
>>> *
>>> to the Jira Workflow for the project.  The vote will be open for 72
>> hours**.
> 
 
 
 +1
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
 For additional commands, e-mail: dev-h...@cassandra.apache.org
 
>>> 
>>> 
>>> --
>>> alex p
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>> 
>>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Change Jira Workflow

[Sam Tunnicliffe]

+1

On Tue, 18 Dec 2018 at 13:47, Joshua McKenzie  wrote:

> +1
>
> On Tue, Dec 18, 2018 at 7:30 AM Aleksey Yeshchenko
>  wrote:
>
> > Sure, +1
> >
> > > On 18 Dec 2018, at 09:42, Joseph Lynch  wrote:
> > >
> > > +1 non-binding
> > >
> > > On Tue, Dec 18, 2018 at 1:15 AM Sylvain Lebresne 
> > wrote:
> > >
> > >> +1
> > >> --
> > >> Sylvain
> > >>
> > >>
> > >> On Tue, Dec 18, 2018 at 9:34 AM Oleksandr Petrov <
> > >> oleksandr.pet...@gmail.com>
> > >> wrote:
> > >>
> > >>> +1
> > >>>
> > >>> On Mon, Dec 17, 2018 at 7:12 PM Nate McCall 
> > wrote:
> > 
> >  On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith
> >   wrote:
> > >
> > > I propose these changes <
> > >>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals
> > >>> *
> > >>> to the Jira Workflow for the project.  The vote will be open for 72
> > >> hours**.
> > >
> > 
> > 
> >  +1
> > 
> > 
> -
> >  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >  For additional commands, e-mail: dev-h...@cassandra.apache.org
> > 
> > >>>
> > >>>
> > >>> --
> > >>> alex p
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > >>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >>>
> > >>>
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Sidecar repo created

[Jason Brown]

Hello all,

In moving the sidecar project forward, I've created a gitbox [1] repo for
the cassandra-sidecar which is located at:

git: https://gitbox.apache.org/repos/asf/cassandra-sidecar.git
github: https://github.com/apache/cassandra-sidecar

There are additional behaviors we can set on the repo [2]:


   1. Any Pull Request that gets opened, closed, reopened or commented on
   can get recorded on the project's mailing list
   2. If a project has a JIRA instance, any PRs or comments on PRs that
   include a JIRA ticket ID will trigger an update on that specific ticket
   (unless opted out of)
   3. GitHub activity can be relayed to IRC channels on the Freenode
   network.

I think we probably want to enable #1 & #2 to maintain parity with what we
have already with the main cassandra repo.

Thanks,

-Jason

[1] https://gitbox.apache.org/
[2] https://reference.apache.org/pmc/github

Re: Proposing an Apache Cassandra Management process

[Jason Brown]

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 
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.jo...@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 <
> > s...@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.jo...@yahoo.com.INVALID" <
> > dinesh.jo...@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 <
> > m...@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-unsubscr...@cassandra.apache.org
> > >> For additional commands, e-mail: dev-h...@cassandra.apache.org
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: [VOTE] Change Jira Workflow

[Joshua McKenzie]

+1

On Tue, Dec 18, 2018 at 7:30 AM Aleksey Yeshchenko
 wrote:

> Sure, +1
>
> > On 18 Dec 2018, at 09:42, Joseph Lynch  wrote:
> >
> > +1 non-binding
> >
> > On Tue, Dec 18, 2018 at 1:15 AM Sylvain Lebresne 
> wrote:
> >
> >> +1
> >> --
> >> Sylvain
> >>
> >>
> >> On Tue, Dec 18, 2018 at 9:34 AM Oleksandr Petrov <
> >> oleksandr.pet...@gmail.com>
> >> wrote:
> >>
> >>> +1
> >>>
> >>> On Mon, Dec 17, 2018 at 7:12 PM Nate McCall 
> wrote:
> 
>  On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith
>   wrote:
> >
> > I propose these changes <
> >>>
> >>
> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals
> >>> *
> >>> to the Jira Workflow for the project.  The vote will be open for 72
> >> hours**.
> >
> 
> 
>  +1
> 
>  -
>  To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>  For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> >>>
> >>>
> >>> --
> >>> alex p
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> >>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> >>>
> >>>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] Change Jira Workflow

[Ariel Weisberg]

+1

On Mon, Dec 17, 2018, at 10:19 AM, Benedict Elliott Smith wrote:
> I propose these changes 
> *
>  
> to the Jira Workflow for the project.  The vote will be open for 72 
> hours**.
> 
> I am, of course, +1.
> 
> * With the addendum of the mailing list discussion 
> ;
>  
> in case of any conflict arising from a mistake on my part in the wiki, 
> the consensus reached by polling the mailing list will take precedence.
> ** I won’t be around to close the vote, as I will be on vacation.  
> Everyone is welcome to ignore the result until I get back in a couple of 
> weeks, or if anybody is eager feel free to close the vote and take some 
> steps towards implementation.

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Proposing an Apache Cassandra Management process

[Dinesh Joshi]

Thanks, Jason!

Dinesh

> On Dec 18, 2018, at 5:47 AM, Jason Brown  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  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.jo...@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 <
>> > s...@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.jo...@yahoo.com.INVALID" <
>> > dinesh.jo...@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 <
>> > m...@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-unsubscr...@cassandra.apache.org
>> > >> For additional commands, e-mail: dev-h...@cassandra.apache.org
>> > >>
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> > For additional commands, e-mail: dev-h...@cassandra.apache.org
>> >
>> >

Re: [VOTE] Change Jira Workflow

[sankalp kohli]

+1

On Tue, Dec 18, 2018 at 9:16 PM Ariel Weisberg  wrote:

> +1
>
> On Mon, Dec 17, 2018, at 10:19 AM, Benedict Elliott Smith wrote:
> > I propose these changes
> > <
> https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals>*
>
> > to the Jira Workflow for the project.  The vote will be open for 72
> > hours**.
> >
> > I am, of course, +1.
> >
> > * With the addendum of the mailing list discussion
> > <
> https://lists.apache.org/thread.html/e4668093169aa4ef52f2bea779333f04a0afde8640c9a79a8c86ee74@%3Cdev.cassandra.apache.org%3E>;
>
> > in case of any conflict arising from a mistake on my part in the wiki,
> > the consensus reached by polling the mailing list will take precedence.
> > ** I won’t be around to close the vote, as I will be on vacation.
> > Everyone is welcome to ignore the result until I get back in a couple of
> > weeks, or if anybody is eager feel free to close the vote and take some
> > steps towards implementation.
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>