Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
Really great to see an incubation proposal for HTrace. If you need another mentor, please consider me. I don't think you need to list HTrace is not the primary focus of any of the current list of contributors as a risk. One can say that about many (perhaps the majority) of contributors to Apache projects. We would hope the incubation process develops a healthy community that sustains a level of contribution that keeps the project moving forward, as we would hope for all incubation candidates. On Fri, Oct 31, 2014 at 4:06 PM, Roman Shaposhnik r...@apache.org wrote: Hi! I would like to propose HTrace to be consider for Apache Incubator. The proposal is attached and is also available on the wiki: https://wiki.apache.org/incubator/HTraceProposal Please let me know what do you guys think and also don't hesitate to massage the proposal on the wiki based on the feedback from this thread. Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two adding a feature or bug fixing. HTrace is currently undergoing a new “spurt” of development with the effort to get HTrace added to Apache HDFS revived and a new standalone viewing facility being added in to HTrace itself. HTrace has been integrated by Apache Phoenix. === Meritocracy === HTrace, up to this, has been run by Apache
Re: [DISCUSS] New Incubator Project for Enterprise Configuration
Anatole, Thirded to the same notes. If you haven't read it already, please look at how to start the proposal (you have mostly the right form, just needs to be on the wiki). http://incubator.apache.org/guides/proposal.html . You should be able to assume that the sponsoring entity is the incubator as well. Your core developers and initial committers don't match. Was this on purpose? Please also list a champion. For all intents and purposes, that should be you Anatole. If you're looking for assistance in mentors you can include me. John On Sun Nov 02 2014 at 12:01:02 AM Roman Shaposhnik ro...@shaposhnik.org wrote: On Fri, Oct 31, 2014 at 1:42 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi Anatole, On Thu, Oct 30, 2014 at 8:58 PM, Anatole Tresch atsti...@gmail.com wrote: ...The current proposal is available on GitHub: https://github.com/java-config/javaconfig-api/blob/ master/src/main/asciidoc/incubator-proposal-tamaya.adoc ... Looks interesting, I would vote +1 to incubate the project once you have recruited 3 mentors - maybe the people listed as sponsors would take this role? You'll need to move the proposal to http://wiki.apache.org/incubator/ before we can vote on it, to get write access to that create an account and let us know your username. This looks interesting to me as well. Both points that Bertrand raised are fully seconded, btw. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Shepherd
Hi all, I am interested in helping out incubator projects as a shepherd, and saw from the wiki the instructions is to simply drop a line here. I wonder what else I need to do to apply? Thanks! Tim - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator
Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop based applications or it can be used in any Java based systems? Thanks Naresh On Mon, Nov 3, 2014 at 1:34 AM, Andrew Purtell apurt...@apache.org wrote: Really great to see an incubation proposal for HTrace. If you need another mentor, please consider me. I don't think you need to list HTrace is not the primary focus of any of the current list of contributors as a risk. One can say that about many (perhaps the majority) of contributors to Apache projects. We would hope the incubation process develops a healthy community that sustains a level of contribution that keeps the project moving forward, as we would hope for all incubation candidates. On Fri, Oct 31, 2014 at 4:06 PM, Roman Shaposhnik r...@apache.org wrote: Hi! I would like to propose HTrace to be consider for Apache Incubator. The proposal is attached and is also available on the wiki: https://wiki.apache.org/incubator/HTraceProposal Please let me know what do you guys think and also don't hesitate to massage the proposal on the wiki based on the feedback from this thread. Thanks, Roman. == Abstract == HTrace is a tracing framework intended for use with distributed systems written in java. == Proposal == HTrace is an aid for understanding system behavior and for reasoning about performance issues in distributed systems. HTrace is primarily a low impedance library that a java distributed system can incorporate to generate ‘breadcrumbs’ or ‘traces’ along the path of execution, even as it crosses processes and machines. HTrace also includes various tools and glue for collecting, processing and ‘visualizing’ captured execution traces for analysis ex post facto of where time was spent and what resources were consumed. == Background == Distributed systems are made up of multiple software components running on multiple computers connected by networks. Debugging or profiling operations run over non-trivial distributed systems -- figuring execution paths and what services, machines, and libraries participated in the processing of a request -- can be involved. == Rationale == Rather than have each distributed system build its own custom ‘tracing’ libraries, ideally all would use a single project that provides necessary primitives and saves each project building its own visualizations and processing tools anew. Google described “...[a] large-scale distributed systems tracing infrastructure” in Dapper, a Large-Scale Distributed Systems Tracing Infrastructure. The paper tells a compelling story of what is possible when disparate systems standardize on a single tracing library and cooperate, ‘passing the baton’, filling out trace context as executions cross systems. HTrace aims to provide a rough equivalent in open source of the described core Dapper tools and library. As it is adopted by more projects, there will be a ‘network effect’ as HTrace will provide a more comprehensive view of activity on the cluster. For example, as HDFS gets HTrace support, we can connect this with the HTrace support in HBase to follow HBase requests as they enter HDFS. Given the success of HTrace depends on its being integrated by many projects, HTrace should be perceived as unhampered, free of any commercial, political, or legal ‘taint’. Being an Apache project would help in this regard. == Initial Goals == HTrace is a small project of narrow scope but with a grand vision: * Move the HTrace source and repository to Apache, a vendor-neutral location. Currently HTrace resides at a Cloudera-hosted repository. * Add past contributors as committers and institute Apache governance. * Evangelize and encourage HTrace diffusion. Initially we will continue a focus on the Hadoop space since that is where most of the initial contributors work and it is where HTrace has been initially deployed. * Building out the standalone visualization tool that ships with HTrace. * Build more community and add more committers == Current Status == Currently HTrace has a viable Java trace library that can be interpolated to create ‘traces’. The work that needs to be done on this library is mostly bug fixes, ease-of-use improvements, and performance tweaks. In the future, we may add libraries for other languages besides Java. HTrace has means of dumping traces to the filesystem, Twitters’ Zipkin (a tracing sink and visualization system developed by Twitter https://github.com/twitter/zipkin), or Apache HBase. Executions can be viewed either in Zipkin or in pygraph (https://code.google.com/p/python-graph/). Since the initial sprint in the summer of 2012 which saw HTrace patches proposed for Apache HDFS and committed to Apache HBase, development has been sporadic; mostly a single developer or two
Re: Incubator PMC/Board report for Nov 2014 ([ppmc])
On Oct 29, 2014, at 9:21 AM, Alan D. Cabrera l...@toolazydogs.com wrote: On Oct 29, 2014, at 9:08 AM, Andy Seaborne a...@apache.org wrote: On 27/10/14 14:15, Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 November 2014, 10:30 am PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Nov 5th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Taverna wasn't in the incubator template so I added a section for it to make sure it didn't get lost. No shepherd assignment. Have I failed to find some place that needs updating so the template includes Taverna? Or was it just timing, because we only started late in October? I think that it’s because you started after I ran the tools. I’ll update the shepherd assignments. Updated. Roman, I’ve assigned you the task of shepherding Taverna this month. :) Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
