Re: Status on new nodes for builds.apache.org

[Jay Zhuang]

Is there any plan to give the CI permission to non-committers? It would 
be great if we could also use that.


Thanks,
Jay

On 6/2/17 10:24 AM, Stefan Podkowinski wrote:

Just a quick heads up for everyone interested in the jobs history at
builds.apache.org or who wants to run devbranch jobs there. A couple of
Jenkins nodes are not working correctly, which is causing jobs to abort
abnormally during start. You'd either have to rebuild until you hit a
working node, or wait until this issue has been resolved (follow
INFRA-14153 for that).

Btw, thanks for Instclustr for donating much needed resources! Those
nodes will be much appreciated once they are working :)

-
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: Status on new nodes for builds.apache.org

[Jeff Jirsa]

We haven't really talked about it - if we can do it without giving out full 
admin that seems reasonable but resources are sorta limited and the asf 
hardware runs pretty slow.

Have you tried circleci ? Free and requires no privileges - works reasonably 
well. 



-- 
Jeff Jirsa


> On Jun 5, 2017, at 1:21 PM, Jay Zhuang  wrote:
> 
> Is there any plan to give the CI permission to non-committers? It would be 
> great if we could also use that.
> 
> Thanks,
> Jay
> 
>> On 6/2/17 10:24 AM, Stefan Podkowinski wrote:
>> Just a quick heads up for everyone interested in the jobs history at
>> builds.apache.org or who wants to run devbranch jobs there. A couple of
>> Jenkins nodes are not working correctly, which is causing jobs to abort
>> abnormally during start. You'd either have to rebuild until you hit a
>> working node, or wait until this issue has been resolved (follow
>> INFRA-14153 for that).
>> 
>> Btw, thanks for Instclustr for donating much needed resources! Those
>> nodes will be much appreciated once they are working :)
>> 
>> -
>> 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
> 

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

Re: NGCC?

[Eric Stevens]

Trying to coordinate it around the eclipse seems neat on the surface, but
practically it's probably not a great idea as most major cities along the
eclipse line have largely sold out their hotel rooms for that event.

On Fri, Jun 2, 2017 at 3:13 PM Carlos Rolo  wrote:

> I might try to get some internal support for sponsorship if needed.
>
> Would love for a NGCC event to happen.
>
> Regards,
>
> Carlos Juzarte Rolo
> Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
>
> Pythian - Love your data
>
> rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
> *linkedin.com/in/carlosjuzarterolo
> *
> Mobile: +351 918 918 100 <+351%20918%20918%20100>
> www.pythian.com
>
> On Fri, Jun 2, 2017 at 9:28 PM, Ben Bromhead  wrote:
>
> > +1
> >
> > On Fri, 2 Jun 2017 at 13:17 Eric Evans 
> wrote:
> >
> > > On Fri, Jun 2, 2017 at 2:34 PM, Ben Bromhead 
> > wrote:
> > > > We are more than happy to donate some resources (both people and
> > > materials)
> > > > to putting on NGCC.
> > > >
> > > > I would suggest some sort of committee of folks who are willing to do
> > the
> > > > groundwork and who act as the executive so it gets done :)
> > >
> > > Gary Dusbabek and myself are both willing to shoulder the grunt work
> > > of organizing this.
> > >
> > > Since we're both in San Antonio, that's the location that would be
> > > most practical for us.  It's also easy to get to, centrally located,
> > > and the weather should be fantastic that time of year.
> > >
> > > We were thinking we'd put together some options for venue, and propose
> > > some dates, and circle back to the list in search of consensus.
> > >
> > > If this seems reasonable for now, then we'll get back to everyone with
> > > more info in a weeks time.
> > >
> > > --
> > > Eric Evans
> > > john.eric.ev...@gmail.com
> > >
> > --
> > Ben Bromhead
> > CTO | Instaclustr 
> > +1 650 284 9692 <(650)%20284-9692>
> > Managed Cassandra / Spark on AWS, Azure and Softlayer
> >
>
> --
>
>
> --
>
>
>
>

Re: Integrating vendor-specific code and developing plugins

[大平怜]

Thanks a lot, Jeremiah, Stefan,

That is exactly what I was looking for.


Rei Odaira

2017-06-03 3:36 GMT-05:00 Stefan Podkowinski :
> I'd suggest to use the git docs for the new pages, so we can accept pull
> requests for adding other plugins. [1]
>
> We can also link there from the main pages. Maybe the community page
> would be a good place for that.
>
> [1] https://cassandra.apache.org/doc/latest/development/documentation.html
>
> On 06/03/2017 02:28 AM, J. D. Jordan wrote:
>> The site is in svn for the main pages.
>>
>> https://svn.apache.org/repos/asf/cassandra/site/src/
>>
>> And in git for the docs.
>> https://github.com/apache/cassandra/tree/trunk/doc/source
>>
>> For suggested changes make a JIRA with proposed changes.
>>
>> -Jeremiah
>>
>>> On Jun 2, 2017, at 5:36 PM, 大平怜  wrote:
>>>
>>> Hi all,
>>>
>>> As for our CAPI Flash enablement code, we are now working on the
>>> plugin approach.  Once it is ready, we would like to propose changes
>>> in some Web pages of http://cassandra.apache.org for better plugin
>>> support.  I don't find any official process to propose such changes,
>>> but could anyone tell us who we should work with?
>>>
>>>
>>> Thanks,
>>> Rei Odaira
>>>
>>> 2017-05-19 16:56 GMT-05:00 大平怜 :
 Hi all,

 Everybody seems to agree with improving the plugin ecosystem (as well
 as not small amount of effort needed to do that), but about
 vendor-specific code integration, let me summarize the issues raised
 so far.

 1) How to test it?  What if my code breaks the vendor-specific build?
 2) How to maintain it?  Who is to maintain the code?
 3) How does it affect the Cassandra release cycle?
 4) How to remove it?  It might be hard to remove once integrated, from
 both technical and markting perspective.

 I think #3 and #4 are rather general issues for any newly proposed
 changes, while #1 and #2 are the most problematic for niche :-)
 platform specific code.  #1 is technically solvable, for example, as
 Jeff (thanks!) showed with the Jenkins slave at ASF and as we are
 trying to connect a ppc machine with a CAPI device to the CI.

 #2 must be socially solved, as a component/platform maintainer system
 should be introduced like some other Apache projects.  Is there any
 chance to have such a system in Cassandra?


 Thanks,
 Rei Odaira

 2017-05-18 12:36 GMT-05:00 Jeff Jirsa :
>
>
>> On Thu, May 18, 2017 at 10:28 AM, Jeff Jirsa  wrote:
>>
>>
>>
>> On Mon, May 15, 2017 at 5:25 PM, Jeremiah D Jordan
>>  wrote:
>>>
>>>
>>>
>>> To me testable means that we can run the tests at the very least for
>>> every release, but ideally they would be run more often than that.
>>> Especially with the push to not release unless the test board is all
>>> passing, we should not be releasing features that we don’t have a test 
>>> board
>>> for.  Ideally that means we have it in ASF CI.  If there is someone 
>>> that can
>>> commit to posting results of runs from an outside CI somewhere, then I 
>>> think
>>> that could work as well, but that gets pretty cumbersome if we have to 
>>> check
>>> 10 different CI dashboards at different locations before every release.
>>
>>
>>
>> It turns out there's a ppc64le jenkins slave @ asf, so I've setup
>> https://builds.apache.org/view/A-D/view/Cassandra/job/cassandra-devbranch-ppc64le-testall/
>> for testing.
>>
>> Like our other devbranch-testall builds, it takes a repo+branch as
>> parameters, and runs unit tests. While the unit tests aren't passing, 
>> this
>> platform should now be considered testable.
>>
>
> (Platform != device, though, the CAPI device obviously isn't there, so the
> row cache implementation still doesn't have public testing)
>
>
>>>
>>> -
>>> 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
>

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

Re: Status on new nodes for builds.apache.org

[Jay Zhuang]

circleci is pretty good. Thanks for adding that. Would be better to have 
DTest too.


One problem for circleci is it takes much longer than a typical host 
(70 minutes vs. 40 minutes on a macbook pro). With more parallel 
test.runners, local host could run even faster:

https://issues.apache.org/jira/browse/CASSANDRA-13078

I'll add circleci test result to the patches in the future. But seems we 
still need a committer to run the DTest for us.


Thanks,
Jay

On 6/5/17 2:02 PM, Jeff Jirsa wrote:

We haven't really talked about it - if we can do it without giving out full 
admin that seems reasonable but resources are sorta limited and the asf 
hardware runs pretty slow.

Have you tried circleci ? Free and requires no privileges - works reasonably 
well.





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

Re: Status on new nodes for builds.apache.org

[Jeff Jirsa]

Ariel was working on making dtests work reliably in circle - I don't want to 
speak for him, but I think he was pretty close.

In the mean time, email me directly or tag me on jira and I'll queue up dtests 
for you on the asf Jenkins 

-- 
Jeff Jirsa


> On Jun 5, 2017, at 10:15 PM, Jay Zhuang  wrote:
> 
> circleci is pretty good. Thanks for adding that. Would be better to have 
> DTest too.
> 
> One problem for circleci is it takes much longer than a typical host (70 
> minutes vs. 40 minutes on a macbook pro). With more parallel test.runners, 
> local host could run even faster:
> https://issues.apache.org/jira/browse/CASSANDRA-13078
> 
> I'll add circleci test result to the patches in the future. But seems we 
> still need a committer to run the DTest for us.
> 
> Thanks,
> Jay
> 
>> On 6/5/17 2:02 PM, Jeff Jirsa wrote:
>> We haven't really talked about it - if we can do it without giving out full 
>> admin that seems reasonable but resources are sorta limited and the asf 
>> hardware runs pretty slow.
>> 
>> Have you tried circleci ? Free and requires no privileges - works reasonably 
>> well.
>> 
>> 
>> 


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