Re: Sidecar meeting notes from 2020-03-10
Sidecar discussions so far have been on the dev list, CEP-1[1], JIRA[2], and seem to be working at its current volume. All the work is currently tracked under 'sidecar' component in Apache Cassandra jira[2]. So with this context and the low volume, I am +1 on Jon's approach. [1]: CEP-1 - https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652224 [2]: Sidecar componet - https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20component%20%3D%20Sidecar Thanks, Vinay On Fri, Mar 13, 2020 at 2:12 PM Brandon Williams wrote: > I agree with Jon, and dev goes directly to my inbox. > > On Fri, Mar 13, 2020 at 4:07 PM Jon Haddad wrote: > > > > I think we're low volume enough across the board that we can continue > > sidecar discussion on dev, and if we start to see too much noise, split > > things up. > > > > On Fri, Mar 13, 2020 at 1:46 PM Patrick McFadin > wrote: > > > > > I think Vinay just pinged everyone working on the project, but to > Josh's > > > point. is this even traffic for the cassandra dev ml? Or does a new one > > > need to be created? > > > > > > On Fri, Mar 13, 2020 at 1:29 PM Nate McCall > wrote: > > > > > > > Where was this announced? I didnt hear anything about it (it's > possible I > > > > missed an email but don't see anything). > > > > > > > > On Sat, Mar 14, 2020 at 8:26 AM Patrick McFadin > > > > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > This week, a small group of us met on Zoom on how to contribute > best to > > > > the > > > > > sidecar project (CEP-1). DataStax is open sourcing several > components, > > > > one > > > > > of which includes a management sidecar. This was open conversation > > > about > > > > > what's being released and how best to participate in CEP-1 in the > > > future. > > > > > Thanks to Vinay Chella for organizing such a diverse group! > > > > > > > > > > As a matter of tracking any discussions, notes were added to CEP-1 > in > > > the > > > > > Apache cwiki. > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 > > > > > > > > > > Thanks, > > > > > > > > > > Patrick > > > > > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
Re: Sidecar meeting notes from 2020-03-10
I agree with Jon, and dev goes directly to my inbox. On Fri, Mar 13, 2020 at 4:07 PM Jon Haddad wrote: > > I think we're low volume enough across the board that we can continue > sidecar discussion on dev, and if we start to see too much noise, split > things up. > > On Fri, Mar 13, 2020 at 1:46 PM Patrick McFadin wrote: > > > I think Vinay just pinged everyone working on the project, but to Josh's > > point. is this even traffic for the cassandra dev ml? Or does a new one > > need to be created? > > > > On Fri, Mar 13, 2020 at 1:29 PM Nate McCall wrote: > > > > > Where was this announced? I didnt hear anything about it (it's possible I > > > missed an email but don't see anything). > > > > > > On Sat, Mar 14, 2020 at 8:26 AM Patrick McFadin > > > wrote: > > > > > > > Hi everyone, > > > > > > > > This week, a small group of us met on Zoom on how to contribute best to > > > the > > > > sidecar project (CEP-1). DataStax is open sourcing several components, > > > one > > > > of which includes a management sidecar. This was open conversation > > about > > > > what's being released and how best to participate in CEP-1 in the > > future. > > > > Thanks to Vinay Chella for organizing such a diverse group! > > > > > > > > As a matter of tracking any discussions, notes were added to CEP-1 in > > the > > > > Apache cwiki. > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 > > > > > > > > Thanks, > > > > > > > > Patrick > > > > > > > > > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Sidecar meeting notes from 2020-03-10
I think we're low volume enough across the board that we can continue sidecar discussion on dev, and if we start to see too much noise, split things up. On Fri, Mar 13, 2020 at 1:46 PM Patrick McFadin wrote: > I think Vinay just pinged everyone working on the project, but to Josh's > point. is this even traffic for the cassandra dev ml? Or does a new one > need to be created? > > On Fri, Mar 13, 2020 at 1:29 PM Nate McCall wrote: > > > Where was this announced? I didnt hear anything about it (it's possible I > > missed an email but don't see anything). > > > > On Sat, Mar 14, 2020 at 8:26 AM Patrick McFadin > > wrote: > > > > > Hi everyone, > > > > > > This week, a small group of us met on Zoom on how to contribute best to > > the > > > sidecar project (CEP-1). DataStax is open sourcing several components, > > one > > > of which includes a management sidecar. This was open conversation > about > > > what's being released and how best to participate in CEP-1 in the > future. > > > Thanks to Vinay Chella for organizing such a diverse group! > > > > > > As a matter of tracking any discussions, notes were added to CEP-1 in > the > > > Apache cwiki. > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 > > > > > > Thanks, > > > > > > Patrick > > > > > >
Re: Sidecar meeting notes from 2020-03-10
I think Vinay just pinged everyone working on the project, but to Josh's point. is this even traffic for the cassandra dev ml? Or does a new one need to be created? On Fri, Mar 13, 2020 at 1:29 PM Nate McCall wrote: > Where was this announced? I didnt hear anything about it (it's possible I > missed an email but don't see anything). > > On Sat, Mar 14, 2020 at 8:26 AM Patrick McFadin > wrote: > > > Hi everyone, > > > > This week, a small group of us met on Zoom on how to contribute best to > the > > sidecar project (CEP-1). DataStax is open sourcing several components, > one > > of which includes a management sidecar. This was open conversation about > > what's being released and how best to participate in CEP-1 in the future. > > Thanks to Vinay Chella for organizing such a diverse group! > > > > As a matter of tracking any discussions, notes were added to CEP-1 in the > > Apache cwiki. > > > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 > > > > Thanks, > > > > Patrick > > >
Re: Sidecar meeting notes from 2020-03-10
Where was this announced? I didnt hear anything about it (it's possible I missed an email but don't see anything). On Sat, Mar 14, 2020 at 8:26 AM Patrick McFadin wrote: > Hi everyone, > > This week, a small group of us met on Zoom on how to contribute best to the > sidecar project (CEP-1). DataStax is open sourcing several components, one > of which includes a management sidecar. This was open conversation about > what's being released and how best to participate in CEP-1 in the future. > Thanks to Vinay Chella for organizing such a diverse group! > > As a matter of tracking any discussions, notes were added to CEP-1 in the > Apache cwiki. > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 > > Thanks, > > Patrick >
Re: Sidecar meeting notes from 2020-03-10
One thing that I wasn't aware of is we have an official JIRA for it now as mentioned in the notes: https://issues.apache.org/jira/projects/CASSANDRASC/issues/CASSANDRASC-1?filter=allopenissues Was talking to someone else earlier today on a different topic about the merits of JIRA vs. using github issues / milestones / releases. I don't particularly have any religion on it but is there a semi-formal or formal apache stance (or a general community orientation here) on project work tracking outside the ML discussions, specifically w/regard to tooling? On Fri, Mar 13, 2020 at 3:26 PM Patrick McFadin wrote: > Hi everyone, > > This week, a small group of us met on Zoom on how to contribute best to the > sidecar project (CEP-1). DataStax is open sourcing several components, one > of which includes a management sidecar. This was open conversation about > what's being released and how best to participate in CEP-1 in the future. > Thanks to Vinay Chella for organizing such a diverse group! > > As a matter of tracking any discussions, notes were added to CEP-1 in the > Apache cwiki. > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 > > Thanks, > > Patrick >
Re: Cassandra CI Status – 2020-03-13
Thanks for working on this, Mick. I think I'll have some time next week to help out. On Fri, Mar 13, 2020 at 5:38 AM Mick Semb Wever wrote: > > The ASF new Jenkins setup is almost complete. > See https://ci-cassandra.apache.org/view/branches/ > The setup has been tracked in INFRA-19951 > > The next step here is to retire our usage of `builds.apache.org` and move > all existing agents to the new setup. There are also new agents getting > ready to being donated, that will be added to this new setup. > > If anyone has a problem with builds.apache.org going away please SPEAK UP > NOW. > > On Jenkins, the main code's unit tests is close to (a japanese) green, > with only 3 failures on both 2.2 and trunk. It's been noticed that some of > the other unit tests (eg compression) are mixing up their run and/or > reports. This, along with the formatting of reports, still remains a todo. > > Otherwise there's been a huge amount of momentum in fixing and improving > the tests. It's only to take a quick glance at the commit log to see test > fixes coming in from everyone and everywhere! > > Some ideas for subsequent steps are: > - clean up report formats (slack notifications and emails sent), > - put together some oversight on slow, flaky, and ignored tests (McFadin, > were you still keen to do this?), > - look into sending failure emails out on unit failures (if over time > there's no more flaky units), > - look into posting test result summary from each pipeline back to jira > as a comment, > - parallelise dtests (because 12 hours is still wild) > - look into testing building of rpm/deb packages > - look into testing of website building? > - look into pipelines only kicking off stages that are relevant to what > changed in the commit, > - more comparison between CircleCI and Jenkins, and from any internal > testing systems if folk can say, > - look into tying in the Driver smoke tests. > > If any contributors are keen on any of these things, do reach out. > Anything to help C* be rock-solid. > > regards, > Mick > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
Sidecar meeting notes from 2020-03-10
Hi everyone, This week, a small group of us met on Zoom on how to contribute best to the sidecar project (CEP-1). DataStax is open sourcing several components, one of which includes a management sidecar. This was open conversation about what's being released and how best to participate in CEP-1 in the future. Thanks to Vinay Chella for organizing such a diverse group! As a matter of tracking any discussions, notes were added to CEP-1 in the Apache cwiki. https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-1+Online+meeting+2020-03-10 Thanks, Patrick
Cassandra CI Status – 2020-03-13
The ASF new Jenkins setup is almost complete. See https://ci-cassandra.apache.org/view/branches/ The setup has been tracked in INFRA-19951 The next step here is to retire our usage of `builds.apache.org` and move all existing agents to the new setup. There are also new agents getting ready to being donated, that will be added to this new setup. If anyone has a problem with builds.apache.org going away please SPEAK UP NOW. On Jenkins, the main code's unit tests is close to (a japanese) green, with only 3 failures on both 2.2 and trunk. It's been noticed that some of the other unit tests (eg compression) are mixing up their run and/or reports. This, along with the formatting of reports, still remains a todo. Otherwise there's been a huge amount of momentum in fixing and improving the tests. It's only to take a quick glance at the commit log to see test fixes coming in from everyone and everywhere! Some ideas for subsequent steps are: - clean up report formats (slack notifications and emails sent), - put together some oversight on slow, flaky, and ignored tests (McFadin, were you still keen to do this?), - look into sending failure emails out on unit failures (if over time there's no more flaky units), - look into posting test result summary from each pipeline back to jira as a comment, - parallelise dtests (because 12 hours is still wild) - look into testing building of rpm/deb packages - look into testing of website building? - look into pipelines only kicking off stages that are relevant to what changed in the commit, - more comparison between CircleCI and Jenkins, and from any internal testing systems if folk can say, - look into tying in the Driver smoke tests. If any contributors are keen on any of these things, do reach out. Anything to help C* be rock-solid. regards, Mick - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
