Re: [VOTE] Argus as a new incubator project
BTW, my prior offer on doing this stands. We just need interest in both ends. On Tue, Jul 22, 2014 at 10:33 AM, Andrew Purtell apurt...@apache.org wrote: +1 (binding) Diversity and 'nonpartisan' governance will be critical for graduating a security project, in my opinion, so it will be important to monitor the attention and openness in community development during incubation. Although the folks behind Argus do not wish to join Apache Sentry (incubating) or take up any of its artifacts, I encourage both communities to find common ground and take some sort of productive common steps. In my opinion, evidence of that would go a long way toward addressing concerns like the above when and if it is time to consider graduation - of either project. On Mon, Jul 21, 2014 at 9:03 AM, Owen O'Malley omal...@apache.org wrote: Following the discussion earlier, I'm calling a vote to accept Argus as a new Incubator project. The proposal draft is available at: https://wiki.apache.org/incubator/ArgusProposal, and is also included below. Vote is open for 72h and closes at 24 July 2014 at 10am PST. [ ] +1 accept Argus in the Incubator [ ] +/-0 [ ] -1 because... I'm +1. .. Owen -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) -- Alejandro
Re: [PROPOSAL] Apache Argus Proposal
There is some overlap between the goals of Argus and Apache Sentry. Apache encourages disjoint teams to form independent projects, even when those projects overlap in scope. Additionally, we feel that the distinct code bases, development teams, and different approaches to the problem should be represented by different projects. This will provide better choices for users to choose from. Approaches may be different, though I wouldn't think they are irreconcilable and we could assume that the end result would be the best of both, thus being a better choice. Have you considered reaching out to the Sentry community to see if they would be interested in bringing Argus existing code base into Sentry? If you are interested, I'd be happy to spend some cycles to see if this would be possible. Cheers. On Wed, Jul 16, 2014 at 11:53 AM, Henry Saputra henry.sapu...@gmail.com wrote: Definitely +1, active members, with lack diversity, are more useful. My original comment was to suggest having mentors come from different organizations so hopefully could help provide different perspectives and inputs to the podling. Never my intention to suggest false diversity to start an Apache incubator project. - Henry On Wed, Jul 16, 2014 at 9:15 AM, Ted Dunning ted.dunn...@gmail.com wrote: On Wed, Jul 16, 2014 at 1:20 AM, Chris Douglas cdoug...@apache.org wrote: So, I am fond of Henry's hope that the project will solicit a more diversified set of mentors and initial committers. The committer and PPMC list should be honest. If there is no diversity, that fact must be visible for it to be tracked. Initial committers are a dodge that demonstrates nothing about the project's willingness to not only accept, but attract new ideas. The viability of an OSS project is not inaccurately *defined* as its ability to compete for that attention. Demanding pro forma adherence to heuristics is a harmful lesson to podlings, unless the goal is to teach them to evade accountability. -C +1 to this. Sham committers are more of a pain than lack of diversity, as much as I dislike sock-puppet projects. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro
Re: Change of IPMC Chair
Neat, Congrats!! On Mon, Feb 3, 2014 at 6:43 PM, Jarek Jarcec Cecho jar...@apache.orgwrote: Congratulations Roman! Jarcec On Mon, Feb 03, 2014 at 06:11:42PM -0800, Henry Saputra wrote: Congrats Roman! On Monday, February 3, 2014, Marvin Humphrey mar...@rectangular.com wrote: Greetings, Congratulations to Roman Shaposhnik! The Incubator PMC has voted to recommend Roman as our next Chair in a resolution to the Board next week. My wholehearted thanks go out to everyone who has contributed to a podling or otherwise worked to advance the Incubator during my tenure as Chair. I look forward to supporting Roman and to continued collaboration with you all, both here in the Incubator and elsewhere. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org javascript:; For additional commands, e-mail: general-h...@incubator.apache.org javascript:; -- Alejandro
Re: Hoya Proposal
Mmmh, if i recall correctly this has come up in the past with other projects and it was decided against it. Could you please check with the hadoop folks about it? Thx On Jan 9, 2014, at 1:19 AM, Steve Loughran ste...@hortonworks.com wrote: no its wrong, it should all be under org.apache.hoya. I had the hadoop prefix so that I could perhaps put it straight into the hadoop code as another tools module -no need for incubation. But as the actual providers and all tests are related to the deployment of hbase and accumulo, it really comes downstream of those. so a rename is needed. but yes, ASF headers everywhere On 8 January 2014 22:48, Henry Saputra henry.sapu...@gmail.com wrote: I like how the initial code already put under org.apache.hadoop.hoya with correct ASF header =) - Henry On Wed, Jan 8, 2014 at 7:08 AM, Steve Loughran ste...@hortonworks.com wrote: I'm starting to put together the incubation proposal for Hoya: a tool to dynamically deploy applications such as HBase or Accumulo on YARN https://wiki.apache.org/incubator/HoyaProposal It does already work to the extent that it can bring up either application, run different clusters of different versions, and remember where containers were allocated so that on application restart it can ask for them back. That increases data locality and makes a big difference with HBase. It also needs a lot more work -YARN-896 is adding YARN features that help, but there's lots of fun to be had in Hoya including -leading edge work in failure handling, modelling cluster unreliability and reacting to it. Can we move beyond simple blacklisting to greylisting, accepting unreliable boxes if we have no altenatives Then there's adding more providers, to support different application installations -I'm starting to write a functional test framework which need provider-specific workload generations Other features: AM should have a web ui that redirects to the live endpoints to all the app-specific UIs (e.g. HBase Master GUI), as well as displaying cluster state itself, for people and for management tools To summarise: lots of fun to be had -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Hoya Proposal
I may have not been clear enough, I was referring to using 'org.apache.hadoop' as package prefix for a project other than hadoop. Thanks On Thu, Jan 9, 2014 at 8:36 AM, Benson Margulies bimargul...@gmail.comwrote: If you can work out a plan to do this directly in Hadoop, there's no need for the incubator. You just build and and contribute it in cahoots with them, and earn commit over there as you go. On Thu, Jan 9, 2014 at 11:14 AM, Alejandro Abdelnur t...@cloudera.com wrote: Mmmh, if i recall correctly this has come up in the past with other projects and it was decided against it. Could you please check with the hadoop folks about it? Thx On Jan 9, 2014, at 1:19 AM, Steve Loughran ste...@hortonworks.com wrote: no its wrong, it should all be under org.apache.hoya. I had the hadoop prefix so that I could perhaps put it straight into the hadoop code as another tools module -no need for incubation. But as the actual providers and all tests are related to the deployment of hbase and accumulo, it really comes downstream of those. so a rename is needed. but yes, ASF headers everywhere On 8 January 2014 22:48, Henry Saputra henry.sapu...@gmail.com wrote: I like how the initial code already put under org.apache.hadoop.hoya with correct ASF header =) - Henry On Wed, Jan 8, 2014 at 7:08 AM, Steve Loughran ste...@hortonworks.com wrote: I'm starting to put together the incubation proposal for Hoya: a tool to dynamically deploy applications such as HBase or Accumulo on YARN https://wiki.apache.org/incubator/HoyaProposal It does already work to the extent that it can bring up either application, run different clusters of different versions, and remember where containers were allocated so that on application restart it can ask for them back. That increases data locality and makes a big difference with HBase. It also needs a lot more work -YARN-896 is adding YARN features that help, but there's lots of fun to be had in Hoya including -leading edge work in failure handling, modelling cluster unreliability and reacting to it. Can we move beyond simple blacklisting to greylisting, accepting unreliable boxes if we have no altenatives Then there's adding more providers, to support different application installations -I'm starting to write a functional test framework which need provider-specific workload generations Other features: AM should have a web ui that redirects to the live endpoints to all the app-specific UIs (e.g. HBase Master GUI), as well as displaying cluster state itself, for people and for management tools To summarise: lots of fun to be had -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro
Re: Hoya Proposal
argh, gmail trying to be extra smart collapsed his comment on that and i missed. sorry thx Alejandro (phone typing) On Jan 9, 2014, at 9:23, larry mccay lmc...@apache.org wrote: Hi Alejandro - I believe that Steve has already acknowledged that a package rename is required and that the project is likely not appropriate for Hadoop proper. thanks, --larry On Thu, Jan 9, 2014 at 11:46 AM, Alejandro Abdelnur t...@cloudera.comwrote: I may have not been clear enough, I was referring to using 'org.apache.hadoop' as package prefix for a project other than hadoop. Thanks On Thu, Jan 9, 2014 at 8:36 AM, Benson Margulies bimargul...@gmail.com wrote: If you can work out a plan to do this directly in Hadoop, there's no need for the incubator. You just build and and contribute it in cahoots with them, and earn commit over there as you go. On Thu, Jan 9, 2014 at 11:14 AM, Alejandro Abdelnur t...@cloudera.com wrote: Mmmh, if i recall correctly this has come up in the past with other projects and it was decided against it. Could you please check with the hadoop folks about it? Thx On Jan 9, 2014, at 1:19 AM, Steve Loughran ste...@hortonworks.com wrote: no its wrong, it should all be under org.apache.hoya. I had the hadoop prefix so that I could perhaps put it straight into the hadoop code as another tools module -no need for incubation. But as the actual providers and all tests are related to the deployment of hbase and accumulo, it really comes downstream of those. so a rename is needed. but yes, ASF headers everywhere On 8 January 2014 22:48, Henry Saputra henry.sapu...@gmail.com wrote: I like how the initial code already put under org.apache.hadoop.hoya with correct ASF header =) - Henry On Wed, Jan 8, 2014 at 7:08 AM, Steve Loughran ste...@hortonworks.com wrote: I'm starting to put together the incubation proposal for Hoya: a tool to dynamically deploy applications such as HBase or Accumulo on YARN https://wiki.apache.org/incubator/HoyaProposal It does already work to the extent that it can bring up either application, run different clusters of different versions, and remember where containers were allocated so that on application restart it can ask for them back. That increases data locality and makes a big difference with HBase. It also needs a lot more work -YARN-896 is adding YARN features that help, but there's lots of fun to be had in Hoya including -leading edge work in failure handling, modelling cluster unreliability and reacting to it. Can we move beyond simple blacklisting to greylisting, accepting unreliable boxes if we have no altenatives Then there's adding more providers, to support different application installations -I'm starting to write a functional test framework which need provider-specific workload generations Other features: AM should have a web ui that redirects to the live endpoints to all the app-specific UIs (e.g. HBase Master GUI), as well as displaying cluster state itself, for people and for management tools To summarise: lots of fun to be had -steve -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro
Re: [VOTE] Accept Twill for Incubation
+1 On Thu, Nov 7, 2013 at 2:19 PM, Roman Shaposhnik r...@apache.org wrote: On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote: The discussion about the Weave proposal has calmed. As the outcome of the discussion, we have chosen a new name for the project, Twill. I would like to call a vote for Twill to become an incubated project. The proposal is pasted below, and also available at: https://wiki.apache.org/incubator/TwillProposal Let's keep this vote open for three business days, closing the voting on Tuesday 11/12. [ ] +1 Accept Twill into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Twill because... +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro
Re: [VOTE] Accept Tez into Incubator
+1 (non-binding), glad to see that finally the idea of having a DAG AM is getting traction. Arun, would you please clarify how Tez is (conceptually) different from the Workflow AM proposed in MAPREDUCE-4495/OOZIE-1178? On Wed, Feb 20, 2013 at 6:50 AM, Hitesh Shah hit...@hortonworks.com wrote: +1 ( non-binding ) -- Hitesh On Feb 19, 2013, at 8:26 PM, Arun C Murthy wrote: Hi Folks, Thanks for participating in the discussion. I'd like to call a VOTE for acceptance of Apache Tez into the Incubator. I'll let the vote run till into this weekend (Sun 2/24 6pm PST). [ ] +1 Accept Apache Tez into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Tez into the Incubator because... Full proposal is pasted at the bottom of this email, and the corresponding wiki is http://wiki.apache.org/incubator/TezProposal. Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Here's my +1 (binding). thanks, Arun PS: From the initial discussion, the only changes are that I've added one new mentor and 2 new committers. All the new additions come from the non-major employer while we continue to strive to further diversify during the incubation. Thanks. = Tez = == Abstract == Tez is an effort to develop a generic application framework which can be used to process arbitrarily complex data-processing tasks and also a re-usable set of data-processing primitives which can be used by other projects. == Proposal == Tez is a proposal to develop a generic application which can be used to process complex data-processing task DAGs and runs natively on Apache Hadoop YARN. YARN is a generic resource-management system on which currently applications like MapReduce already exist. MapReduce is a specific, and constrained, DAG - which is not optimal for several frameworks like Apache Hive and Apache Pig. Furthermore, we propose to develop a re-usable set of libraries of data-processing primitives such as sorting, merging, data-shuffling, intermediate data management etc. which are necessary for Tez which we envision can be used directly by other projects. == Background == Apache Hadoop MapReduce has emerged as the assembly-language on which other frameworks like Apache Pig and Apache Hive have been built. However, it has been well accepted that MapReduce produces very constrained task DAGs for each job which results in Apache Pig and Apache Hive requiring multiple MapReduce jobs for several queries. By providing a more expressive DAG of tasks for a job, Tez attempts to provide significantly enhanced data-processing capabilities for projects like Apache Pig, Apache Hive, Cascading etc. == Rationale == There is an important gap that Tez fulfills in the Apache Hadoop ecosystem of allowing for more expressive task DAGs for data-processing applications such as Apache Pig, Apache Hive, Cascading etc. With emergence of Apache Hadoop YARN, there is a strong need for a common DAG application which can then be shared by Apache Pig, Apache Hive, Cascading etc. == Initial Goals == The initial goals for this project are to specify the detailed requirements and architecture, and then develop the initial implementation including the DAG ApplicationMaster to run natively inside Apache Hadoop YARN. == Current Status == Significant work has been completed to identify the initial requirements and define the overall system architecture. There is a patch available in the internal Hortonworks git repository which can act as the initial seed. === Meritocracy === We plan to invest in supporting a meritocracy. We will discuss the requirements in an open forum. Several companies have already expressed interest in this project, and we intend to invite additional developers to participate. We will encourage and monitor community participation so that privileges can be extended to those that contribute. === Community === The need for a generic DAG application for data processing in the open source is tremendous, so there is a potential for a very large community. We believe that Tez's extensible architecture will further encourage community participation. Also, related Apache projects (eg, Pig, Hive) have very large and active communities, and we expect that over time Tez will also attract a large community. === Core Developers === The developers on the initial committers list include people very experienced in the Apache Hadoop ecosystem: * Alan Gates gates at apache dot org * Arun C Murthy acmurthy at apache dot org * Ashutosh Chauhan hashutosh at apache dot org * Bikas Saha bikas at apache dot org * Chris Douglas cdouglas at apache dot org * Daryn Sharp daryn at apache dot org * Devaraj Das ddas at apache dot org * Gopal Vijayaraghavan gopal at hortonworks dot com * Gunther Hagleitner
Re: [VOTE] Accept Apache Knox Hadoop Gateway Project into the Incubator
+1 non binding Alejandro (phone typing) On Feb 15, 2013, at 5:45 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: +1 binding. Cheers, Chris Sent from my iPad On Feb 15, 2013, at 11:23 AM, Devaraj Das d...@hortonworks.com wrote: Hi Folks, Thanks for participating in the discussion. I'd like to call a VOTE for acceptance of Apache Knox Hadoop Gateway Project into the Incubator. The vote will close on Feb 22 at 6:00 p.m. [ ] +1 Accept Apache Knox Hadoop Gateway Project into the Incubator [ ] +0 Don't care. [ ] -1 Don't accept Apache Knox Hadoop Gateway Project into the Incubator because... Full proposal is pasted at the bottom of this email, and the corresponding wiki is http://wiki.apache.org/incubator/knox. Only VOTEs from Incubator PMC members are binding. Here's my +1 (binding). Thanks, Devaraj. - Knox Gateway Proposal Abstract Knox Gateway is a system that provides a single point of secure access for Apache Hadoop clusters. Proposal The Knox Gateway (“Gateway” or “Knox”) is a system that provides a single point of authentication and access for Apache Hadoop services in a cluster. The goal is to simplify Hadoop security for both users (i.e. who access the cluster data and execute jobs) and operators (i.e. who control access and manage the cluster). The Gateway runs as a server (or cluster of servers) that serve one or more Hadoop clusters. Provide perimeter security to make Hadoop security setup easier Support authentication and token verification security scenarios Deliver users a single cluster end-point that aggregates capabilities for data and jobs Enable integration with enterprise and cloud identity management environments Background An Apache Hadoop cluster is presented to consumers as a loose collection of independent services. This makes it difficult for users to interact with Hadoop since each service maintains it’s own method of access and security. As well, for operators, configuration and administration of a secure Hadoop cluster is a complex and many Hadoop clusters are insecure as a result. The goal of the project is to provide coverage for all existing Hadoop ecosystem projects. In addition, the project will be extensible to allow for new and/or proprietary Hadoop components without requiring changes to the gateway source code. The gateway is expected to run in a DMZ environment where it will provide controlled access to these Hadoop services. In this way Hadoop clusters can be protected by a firewall and only limited access provided through the firewall for the gateway. The authentication components of the gateway will be modular and extensible such that it can be integrated with existing security infrastructure. Rationale Organizations that are struggling with Hadoop cluster security result in a) running Hadoop without security or b) slowing adoption of Hadoop. The Gateway aims to provide perimeter security that integrates more easily into existing organizations’ security infrastructure. Doing so will simplify security for these organizations and benefit all Hadoop stakeholders (i.e. users and operators). Additionally, making a dedicated perimeter security project part of the Apache Hadoop ecosystem will prevent fragmentation in this area and further increase the value of Hadoop as a data platform. Current Status Prototype available, developed by the list of initial committers. Meritocracy We desire to build a diverse developer community around Gateway following the Apache Way. We want to make the project open source and will encourage contributors from multiple organizations following the Apache meritocracy model. Community We hope to extend the user and developer base in the future and build a solid open source community around Gateway. Apache Hadoop has a large ecosystem of open source projects, each with a strong community of contributors. All project communities in this ecosystem have an opportunity to participate in the advancement of the Gateway project because ultimately, Gateway will enable the security capabilities of their project to be more enterprise friendly. Core Developers Gateway is currently being developed by several engineers from Hortonworks - Kevin Minder, Larry McCay, John Speidel, Tom Beerbower and Sumit Mohanty. All the engineers have deep expertise in middleware, security identity systems and are quite familiar with the Hadoop ecosystem. Alignment The ASF is a natural host for Gateway given that it is already the home of Hadoop, Hive, Pig, HBase, Oozie and other emerging big data software projects. Gateway is designed to solve the security challenges familiar to the Hadoop ecosystem family of projects. Known Risks Orphaned products Reliance on Salaried Developers The core developers plan to work full time on the project. We believe that this project will be of
Re: [PROPOSAL] Knox Hadoop Gateway Project
Hi Kevin, I'd like to offer joining the project if accepted for incubation. I'm actively working in Hadoop (PMC member) and Oozie (PMC member), helped driving Oozie through incubation and graduation. I'm also the initial developer of hadoop-auth and httpfs (standalone WebHDFS gateway). In, Oozie provides REST APIs for jobs submission (workflows, coordinators, bundles, mapreduce, streaming, pig). In addition I've been involved in efforts for providing HTTP access to Hadoop stack. Thanks. On Mon, Feb 11, 2013 at 11:54 AM, Kevin Minder kevin.min...@hortonworks.com wrote: The proposal is now hosted on the wiki. http://wiki.apache.org/**incubator/knoxhttp://wiki.apache.org/incubator/knox Currently just the initial proposal. I'll be incorporating feedback/clarifications shortly. On 2/11/13 11:35 AM, Bertrand Delacretaz wrote: Hi, On Mon, Feb 11, 2013 at 5:07 PM, Kevin Minder kevin.min...@hortonworks.com wrote: ...Currently all of the mentors are affiliated with Hortonworks as well. We can reach out to a number of other people and organizations that are interested in the project to diversify if this is an important consideration at this stage I think that would be good - just ask for more mentors on this list. Without such diversity this is basically an all-hortonworks podling, which is not good IMO. I don't seem to have privs to create http://wiki.apache.org/** incubator/knox http://wiki.apache.org/incubator/knox. Would that be the correct place to evolve the proposal? If so, how do I go about creating in?... Yes, http://wiki.apache.org/**incubator/ishttp://wiki.apache.org/incubator/isthe right place - just ask for write access on this list, a [wiki] marker in the subject line will probably help. I don't think I have the rights to grant that access myself. -Bertrand --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- Alejandro
[RESULT][VOTE] Graduate Oozie podling from Apache Incubator
The VOTE by Apache Incubator to graduate Oozie podling has passed. Tally of binding votes is as follows: 5 +1 votes Chris Mattmann Arvind Prabhakar Chris Douglas Alan Gates Bertrand Delacretaz 0 +0 votes 0 -1 votes The VOTE threads for this can be found at [1]. I will proceed by sending the proposal to the board. [1] http://s.apache.org/Gs0 http://s.apache.org/UJp Thanks and regards, Alejandro Abdelnur - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduate Oozie podling from Apache Incubator
This is the second call for vote to graduate Oozie podling from Apache Incubator, comments and suggestions received during the first call have been addressed. Oozie entered the Incubator in July of 2011. Since then it has added two new committers and made two significant releases following the ASF policies and guidelines. The community of Oozie is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Oozie community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Oozie podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Oozie podling [ ] -1 Reject graduation of Oozie podling from Apache Incubator This vote will be open for at least 72 hours. Please find the proposed board resolution below. [1] http://s.apache.org/WDb [2] http://s.apache.org/AB2 Regards, Alejandro Abdelnur - X. Establish the Apache Oozie Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a system for managing and scheduling workflows that run different types of Hadoop jobs (such as MapReduce, Pig, Hive and Sqoop) as well as system specific jobs (such as Java programs and shell scripts) for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oozie Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oozie Project be and hereby is responsible for the creation and maintenance of software related to a system for managing and scheduling workflows that run different types of Hadoop jobs (such as MapReduce, Pig, Hive and Sqoop) as well as system specific jobs (such as Java programs and shell scripts); and be it further RESOLVED, that the office of Vice President, Apache Oozie be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oozie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oozie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oozie Project: * Alan Gatesga...@apache.org * Alejandro Abdelnurt...@apache.org * Andreas Neumann a...@apache.org * Angelo Huang ange...@apache.org * Chao Wang broo...@apache.org * Chris Douglas cdoug...@apache.org * Devaraj Das d...@apache.org * Harsh Chouraria ha...@apache.org * Mayank Bansal may...@apache.org * Mohammad Islamkam...@apache.org * Virag Kothari vi...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alejandro Abdelnur be appointed to the office of Vice President, Apache Oozie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Oozie PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Oozie Project; and be it further RESOLVED, that the Apache Oozie Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oozie podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oozie podling encumbered upon the Apache Incubator Project are hereafter discharged.
[VOTE] Graduate Oozie podling from Apache Incubator
[resending, starting as a new email to force a new thread] This is the second call for vote to graduate Oozie podling from Apache Incubator, comments and suggestions received during the first call have been addressed. Oozie entered the Incubator in July of 2011. Since then it has added two new committers and made two significant releases following the ASF policies and guidelines. The community of Oozie is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Oozie community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Oozie podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Oozie podling [ ] -1 Reject graduation of Oozie podling from Apache Incubator This vote will be open for at least 72 hours. Please find the proposed board resolution below. [1] http://s.apache.org/WDb [2] http://s.apache.org/AB2 Regards, Alejandro Abdelnur - X. Establish the Apache Oozie Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a system for managing and scheduling workflows that run different types of Hadoop jobs (such as MapReduce, Pig, Hive and Sqoop) as well as system specific jobs (such as Java programs and shell scripts) for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oozie Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oozie Project be and hereby is responsible for the creation and maintenance of software related to a system for managing and scheduling workflows that run different types of Hadoop jobs (such as MapReduce, Pig, Hive and Sqoop) as well as system specific jobs (such as Java programs and shell scripts); and be it further RESOLVED, that the office of Vice President, Apache Oozie be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oozie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oozie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oozie Project: * Alan Gatesga...@apache.org * Alejandro Abdelnurt...@apache.org * Andreas Neumann a...@apache.org * Angelo Huang ange...@apache.org * Chao Wang broo...@apache.org * Chris Douglas cdoug...@apache.org * Devaraj Das d...@apache.org * Harsh Chouraria ha...@apache.org * Mayank Bansal may...@apache.org * Mohammad Islamkam...@apache.org * Virag Kothari vi...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alejandro Abdelnur be appointed to the office of Vice President, Apache Oozie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Oozie PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Oozie Project; and be it further RESOLVED, that the Apache Oozie Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oozie podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oozie podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Oozie podling from Apache Incubator
Thanks Jukka, Currently Oozie focuses on coordinating workflows which mainly consists of Hadoop jobs. If that would change in the future, then we would follow the necessary steps to update its charter. Does this make sense? Regards. On Tue, Aug 14, 2012 at 5:55 AM, Jukka Zitting jukka.zitt...@gmail.com wrote: Hi, On Saturday, August 11, 2012, Alejandro Abdelnur wrote: This is a call for vote to graduate Oozie podling from Apache Incubator. [x] +1 Graduate Oozie podling from Apache Incubator open-source software related to a system for managing and scheduling workflows that run Apache Hadoop Map Reduce jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop jobs for distribution at no charge to the public. The explicit list seems too specific here; what if you want to add support for new kinds of jobs? How about something a bit more general, like a system for managing and scheduling workflows of distributed jobs? BR, Jukka Zitting -- Alejandro - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Oozie podling from Apache Incubator
Hi Bertrand, The Oozie pages have been updated: http://incubator.apache.org/projects/oozie.html http://incubator.apache.org/oozie/Credits.html (I believe this is the one where you saw the incorrect user ID). Would you consider changing you -1 vote now that the reason for it has been addressed? Thanks and best regards. Alejandro On Mon, Aug 13, 2012 at 2:41 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Sat, Aug 11, 2012 at 1:12 AM, Alejandro Abdelnur t...@cloudera.com wrote: ... RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oozie Project: ... * Harsh Chouraria qwertyman...@apache.org ... I don't see that user at http://people.apache.org/committer-index.html, and id qwertymaniac on people.a.o doesn't find it either. -1 for graduation until this is fixed, please check with infra. Also, the proposed PPMC doesn't include an ASF member. While not a requirement, I think it's good to have one on board, if only to help others become members over time. Would one of your mentors who's an ASF member agree to stay on the new PMC? -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[CALLING OFF THE VOTE] [VOTE] Graduate Oozie podling from Apache Incubator
I'm calling off the vote as due to the omission of mentors from the proposed PMC. We'll discuss this in the Oozie community and come up with a new proposal. Thanks and regards. Alejandro On Wed, Aug 15, 2012 at 11:26 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Tue, Aug 14, 2012 at 4:55 AM, Alejandro Abdelnur t...@cloudera.com wrote: ...Sebb, Bertrand, does the updated status page address your concerns?... My concern is about the list of people included in the resolution, which had a mistake. IMO you can just post the corrected resolution in this thread (it's more a formal thing and doesn't really impact what the project is), and leave at least 24 hours for people to complain if they want, but no need to restart this vote. The revised list can also include Alan and/or Devaraj if they accept to stay as PMC members. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Oozie podling from Apache Incubator
Sebb, Beltrand, Thanks for pointing out missing/incorrect information in the status page, We've also noticed that we never added Devaraj Das as mentor. Corrections to Oozie status page: -- * Add Devaraj Das as mentor. * Change Hash's 'qwertymaniac' ID to 'harsh' (by mistake I've added him with his JIRA ID instead his Apache/SVN ID) * Missing milestone dates: 1* Migrate the project to our infrastructure. 2* Subscribe all Mentors on the pmc and general lists. 3* Give all Mentors access to the incubator SVN repository. 4* Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. 5* Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. FEB/22/2012 6* Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. For #1: OCT/05/2011 (OOZIE-1) For #2: OCT/05/2011 (Don't have effective date, by this date there were threads in the alias involving the mentors) For #3: OCT/05/2011 (Don't have effective date of this) For #4: FEB/22/2012 (First Oozie Incubator release, RAT report) For #5: FEB/22/2012 (First Oozie Incubator release, Oozie does not include 3rd party source code) For #6: JUN/06/2012 (Second Oozie Incubator release, all contributed code as been explicitly granted license to ASF for inclusion) -- I believe this will address your concerns. If so, please let us know and we'll update Oozie status page accordingly. Also, let us know if we can resume this vote, or if you prefer us to start a new vote. Thanks and regards. Alejandro On Mon, Aug 13, 2012 at 2:48 AM, sebb seb...@gmail.com wrote: On 11 August 2012 00:12, Alejandro Abdelnur t...@cloudera.com wrote: This is a call for vote to graduate Oozie podling from Apache Incubator. Oozie entered the Incubator in July of 2011. Since then it has added two new committers and made two significant releases following the ASF policies and guidelines. The community of Oozie is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Oozie community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Oozie podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Oozie podling [ ] -1 Reject graduation of Oozie podling from Apache Incubator As I already wrote, there are several items in the status page [1] that appear to be incomplete. Have these been addressed? If so, please update the status page. If not, please fix them before proceeding with the graduation vote. [1] http://incubator.apache.org/projects/oozie.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Oozie podling from Apache Incubator
Alan, thanks for updating Oozie status page. Sebb, Bertrand, does the updated status page address your concerns? Regarding Bertrand suggestion about leaving an Apache member on the PMC, We was not aware of that possibility. I'll bring it up in the Oozie community. Alan, thanks for your offer, I'm sure you'd be a valuable contributor to Oozie PMC. However, if there is not reason for calling off the current VOTE, I'd prefer to continue with it (we already have 7 +1s) and then discuss the inclusion of an Apache member to the PMC as one of the first topics of the Oozie community as a Top Level Project. Thoughts? Thanks. Alejandro On Mon, Aug 13, 2012 at 3:19 PM, Alan Gates ga...@hortonworks.com wrote: I've updated the status page with the info provided by Alejandro. Alejandro, of the concerns brought up by Bertrand you didn't address the one about leaving an Apache member on the PMC. You should probably discuss that with the rest of the Oozie community to see what they want to do. I'm happy to stay on the PMC if the community is interested. I'll let ones wiser than I in the ways of the incubator answer whether you need a new vote, except that if you add a new PMC member from amongst the mentors it definitely seems you'll need to restart the vote. Alan. On Aug 13, 2012, at 8:38 AM, Alejandro Abdelnur wrote: Sebb, Beltrand, Thanks for pointing out missing/incorrect information in the status page, We've also noticed that we never added Devaraj Das as mentor. Corrections to Oozie status page: -- * Add Devaraj Das as mentor. * Change Hash's 'qwertymaniac' ID to 'harsh' (by mistake I've added him with his JIRA ID instead his Apache/SVN ID) * Missing milestone dates: 1* Migrate the project to our infrastructure. 2* Subscribe all Mentors on the pmc and general lists. 3* Give all Mentors access to the incubator SVN repository. 4* Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. 5* Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute. FEB/22/2012 6* Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms. For #1: OCT/05/2011 (OOZIE-1) For #2: OCT/05/2011 (Don't have effective date, by this date there were threads in the alias involving the mentors) For #3: OCT/05/2011 (Don't have effective date of this) For #4: FEB/22/2012 (First Oozie Incubator release, RAT report) For #5: FEB/22/2012 (First Oozie Incubator release, Oozie does not include 3rd party source code) For #6: JUN/06/2012 (Second Oozie Incubator release, all contributed code as been explicitly granted license to ASF for inclusion) -- I believe this will address your concerns. If so, please let us know and we'll update Oozie status page accordingly. Also, let us know if we can resume this vote, or if you prefer us to start a new vote. Thanks and regards. Alejandro On Mon, Aug 13, 2012 at 2:48 AM, sebb seb...@gmail.com wrote: On 11 August 2012 00:12, Alejandro Abdelnur t...@cloudera.com wrote: This is a call for vote to graduate Oozie podling from Apache Incubator. Oozie entered the Incubator in July of 2011. Since then it has added two new committers and made two significant releases following the ASF policies and guidelines. The community of Oozie is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Oozie community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Oozie podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Oozie podling [ ] -1 Reject graduation of Oozie podling from Apache Incubator As I already wrote, there are several items in the status page [1] that appear to be incomplete. Have these been addressed? If so, please update the status page. If not, please fix them before proceeding with the graduation vote. [1] http://incubator.apache.org/projects/oozie.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro
[VOTE] Graduate Oozie podling from Apache Incubator
This is a call for vote to graduate Oozie podling from Apache Incubator. Oozie entered the Incubator in July of 2011. Since then it has added two new committers and made two significant releases following the ASF policies and guidelines. The community of Oozie is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Oozie community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Oozie podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Oozie podling [ ] -1 Reject graduation of Oozie podling from Apache Incubator This vote will be open for at least 72 hours. Please find the proposed board resolution below. [1] http://s.apache.org/WDb [2] http://s.apache.org/AB2 Regards, Alejandro Abdelnur X. Establish the Apache Oozie Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to a system for managing and scheduling workflows that run Apache Hadoop Map Reduce jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop jobs for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Oozie Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Oozie Project be and hereby is responsible for the creation and maintenance of software related to a system for managing and scheduling workflows that run Apache Hadoop Map Reduce jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop jobs; and be it further RESOLVED, that the office of Vice President, Apache Oozie be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Oozie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Oozie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Oozie Project: * Alejandro Abdelnurt...@apache.org * Andreas Neumann a...@apache.org * Angelo Huang ange...@apache.org * Chao Wang broo...@apache.org * Harsh Chouraria qwertyman...@apache.org * Mayank Bansal may...@apache.org * Mohammad Islamkam...@apache.org * Virag Kothari vi...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alejandro Abdelnur be appointed to the office of Vice President, Apache Oozie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Oozie PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Oozie Project; and be it further RESOLVED, that the Apache Oozie Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Oozie podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Oozie podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT] [VOTE] Release Oozie 3.2.0-incubating (candidate 1)
Based on the following votes (3 from IPMCs) the release Oozie 3.2.0-incubating has been approved. +1 Harsh J +1 Alan Gates (binding) +1 Alejandro Abdelnur +1 Mona Chitnis +1 Virag Kothari +1 Angelo Huang +1 Jeremy Hanna +1 Roman Shaposhnik +1 Patrick Hunt (binding) +1 Tom White (binding) +1 Mayank Bansal Following I'll complete the release process (tags, documentation, etc). Thanks to all. Alejandro On Tue, Jun 5, 2012 at 7:46 PM, Tom White tom.e.wh...@gmail.com wrote: +1 I checked the signature and checksums, inspected the source tag, ran a RAT report, checked the disclaimer, notice and license files. Tom On Fri, Jun 1, 2012 at 6:35 PM, Alejandro Abdelnur t...@cloudera.com wrote: Dear Incubator PMCs, Oozie Incubator community has voted on the Oozie 3.2.0-incubating release. The tally of the votes is: Results: 8 +1 votes, 0 -1 votes developers/users: 3 +1 (mona, jeremy, roman) committers: 4 +1 (harsh, virag, angelo, tucu) mentors: 1 +1 (alan) Below you'll find the email sent to the Oozie developer alias with the VOTE request. There you'll find the details of the release and where to download the release artifact. Vote closes on Monday JUN/04 17:00 PST. Thanks Alejandro -- Forwarded message -- From: Alejandro Abdelnur t...@cloudera.com Date: Tue, May 29, 2012 at 3:23 PM Subject: [VOTE] Release Oozie 3.2.0-incubating (candidate 1) To: oozie-...@incubator.apache.org Dear Oozie community, The release candidate 1 for for Oozie 3.2.0-incubating is available. Changes from candidate 0: * removes native files and adds instructions on how to test Pipe * consolidate rat report * minor fix in the demo example Some of the new features are: * Hive action * Sqoop action * Shell action * Tool to create/upgrade database schema * Kerberos SPNEGO authentication * Proxy User capabilities for Oozie users * Job ACLs support * Improved Job information over HTTP REST API * Improved Workflow validation * Sharelib directories per action * EL functions for Workflow and Coordinator applications In addition it includes several improvements for performance and stability and several bug fixes. Keys used to sign the release are available at http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup. Please download, test, and try it out: http://people.apache.org/~tucu/oozie-3.2.0-incubating-candidate-1 The release, md5 signature, gpg signature, and rat report can all be found at the above URL. Vote closes on Friday JUN/01 15:30 PST. Thanks -- Alejandro - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Alejandro
[VOTE] Release Oozie 3.2.0-incubating (candidate 1)
Dear Incubator PMCs, Oozie Incubator community has voted on the Oozie 3.2.0-incubating release. The tally of the votes is: Results: 8 +1 votes, 0 -1 votes developers/users: 3 +1 (mona, jeremy, roman) committers: 4 +1 (harsh, virag, angelo, tucu) mentors: 1 +1 (alan) Below you'll find the email sent to the Oozie developer alias with the VOTE request. There you'll find the details of the release and where to download the release artifact. Vote closes on Monday JUN/04 17:00 PST. Thanks Alejandro -- Forwarded message -- From: Alejandro Abdelnur t...@cloudera.com Date: Tue, May 29, 2012 at 3:23 PM Subject: [VOTE] Release Oozie 3.2.0-incubating (candidate 1) To: oozie-...@incubator.apache.org Dear Oozie community, The release candidate 1 for for Oozie 3.2.0-incubating is available. Changes from candidate 0: * removes native files and adds instructions on how to test Pipe * consolidate rat report * minor fix in the demo example Some of the new features are: * Hive action * Sqoop action * Shell action * Tool to create/upgrade database schema * Kerberos SPNEGO authentication * Proxy User capabilities for Oozie users * Job ACLs support * Improved Job information over HTTP REST API * Improved Workflow validation * Sharelib directories per action * EL functions for Workflow and Coordinator applications In addition it includes several improvements for performance and stability and several bug fixes. Keys used to sign the release are available at http://svn.apache.org/viewvc/incubator/oozie/trunk/KEYS?view=markup. Please download, test, and try it out: http://people.apache.org/~tucu/oozie-3.2.0-incubating-candidate-1 The release, md5 signature, gpg signature, and rat report can all be found at the above URL. Vote closes on Friday JUN/01 15:30 PST. Thanks -- Alejandro
Re: Policy on t-shirts for incubating projects
You mean the project logo within an egg? Cheers. Alejandro On Thu, Jul 21, 2011 at 8:48 AM, Alan D. Cabrera l...@toolazydogs.comwrote: On Jul 21, 2011, at 8:44 AM, Bertrand Delacretaz wrote: On Thu, Jul 21, 2011 at 5:15 PM, Alan D. Cabrera l...@toolazydogs.com wrote: What's the policy on making t-shirts for an incubating project? I'd say the t-shirt should make it clear that the project is incubating. My thoughts as well. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Oozie to join the Incubator
operations, Java programs and shell scripts. Because of this, developers find themselves writing ad-hoc glue programs to combine these Hadoop jobs. These ad-hoc programs are difficult to schedule, manage, monitor and recover. Workflow management and scheduling is an essential feature for large-scale data processing applications. Such applications could write the customized solution that would require separate development, operational, and maintenance overhead. Since it is a prevalent use-case for data processing, the application developer would surely prefer a generalized solution with little or no such overhead. Oozie addresses the challenge by providing an execution framework to flexibly specify the job dependency, data dependency, and time dependency. In addition, Oozie provides a multi-tenant-based centralized service and the opportunity to optimize load and utilization while respecting SLAs. Oozie is built on Apache HadoopTM to schedule jobs related to various Apache projects such as Hadoop, Pig, and Hive. As an Apache Open source project, Oozie is expected to attract the larger and more diversified community that currently uses such Apache sponsored projects. Additionally, users of the Hadoop ecosystem can influence Oozie’s roadmap, and contribute to it. Likewise, Oozie, as part of the Apache Hadoop TMecosystem, will be a great benefit to the current Hadoop/Pig/Hive/HBase/HCatalog community. Current Status Meritocracy Oozie currently is a github-based open sourced project where developers from multiple companies are contributing to the project. Our intent with this incubator proposal is to further extend this diverse developer community around Oozie following the Apache meritocracy model. We plan to continue to provide adequate support to new developers and to quickly recruit those who make solid contributions to committer status. In addition, Oozie will expect, accept, and work to attract contributions from amateurs as well. Community While an efficient workflow management and scheduling system is critical for large companies with huge data processing in multi-tenant clusters, it is equally necessary for any non-trivial deployment. Different companies are currently using Oozie as a workflow scheduler for Hadoop-based data processing. At Yahoo! it is being used extensively in production clusters to process thousand of jobs. Like the Oozie user community, the Oozie developer community is also very strong. Developers from Yahoo! provided the initial code base, and they are still the most active contributors. In late 2010, developers from Cloudera also started contributing, and currently other companies (e.g., IBM) are beginning to participate. We currently use JIRA for issue tracking, github for code hosting and Yahoo! Groups for developer and user communications. Core Developers Oozie is currently being designed and developed by four engineers from Yahoo! – Mohammad Islam, Angelo Huang, Mayank Bansal, and Andreas Neumann. In addition, many outside contributors are actively contributing in design and development. Among them, Alejandro Abdelnur from Cloudera and Chao Wang from IBM are very important contributors. All of these core developers have deep expertise in Hadoop and the Hadoop Ecosystem in general. Alignment The ASF is a natural host for Oozie given that it is already the home of Hadoop, Pig, Hive, and other emerging cloud software projects. Oozie was designed to support Hadoop from the beginning in order to solve data processing challenges in Hadoop clusters. Oozie complements the existing Apache cloud computing projects by providing a flexible framework for managing complex data processing tasks. Known Risks Orphaned Products The core developers plan to work full time on the project. There is very little risk of Oozie getting orphaned since large companies like Yahoo! are extensively using it on their production Hadoop clusters. For example, there are nearly 400 Yahoo! internal Oozie users and thousands of jobs are processed hourly through Oozie in production. In addition, there are nearly 400 active users (including Yahoo! internal and external) in the email community where nearly 15 emails are exchanged per day. Furthermore, there were more than 1500 downloads of the Oozie binary in the last eight months from the github site and a large number of downloads were conducted by other companies such as Cloudera. Oozie has three major releases and more than 15 patch releases in the last couple of years which further demonstrates Oozie as a very active project. We plan to extend and diversify this community further through Apache. Inexperience with Open Source The core developers are all active
Re: [PROPOSAL] Oozie for the Apache Incubator
the customized solution that would require separate development, operational, and maintenance overhead. Since it is a prevalent use-case for data processing, the application developer would surely prefer a generalized solution with little or no such overhead. Oozie addresses the challenge by providing an execution framework to flexibly specify the job dependency, data dependency, and time dependency. In addition, Oozie provides a multi-tenant-based centralized service and the opportunity to optimize load and utilization while respecting SLAs. Oozie is built on Apache Hadoop to schedule jobs related to various Apache projects such as Hadoop, Pig, and Hive. As an Apache Open source project, Oozie is expected to attract the larger and more diversified community that currently uses such Apache sponsored projects. Additionally, users of the Hadoop ecosystem can influence Oozie’s roadmap, and contribute to it. Likewise, Oozie, as part of the Apache Hadoop ecosystem, will be a great benefit to the current Hadoop/Pig/Hive/HBase/HCatalog community. Current Status Meritocracy Oozie currently is a github-based open sourced project where developers from multiple companies are contributing to the project. Our intent with this incubator proposal is to further extend this diverse developer community around Oozie following the Apache meritocracy model. We plan to continue to provide adequate support to new developers and to quickly recruit those who make solid contributions to committer status. In addition, Oozie will expect, accept, and work to attract contributions from amateurs as well. Community While an efficient workflow management and scheduling system is critical for large companies with huge data processing in multi-tenant clusters, it is equally necessary for any non-trivial deployment. Different companies are currently using Oozie as a workflow scheduler for Hadoop-based data processing. At Yahoo! it is being used extensively in production clusters to process thousand of jobs. Like the Oozie user community, the Oozie developer community is also very strong. Developers from Yahoo! provided the initial code base, and they are still the most active contributors. In late 2010, developers from Cloudera also started contributing, and currently other companies (e.g., IBM) are beginning to participate. We currently use JIRA for issue tracking, github for code hosting and Yahoo! Groups for developer and user communications. Core Developers Oozie is currently being designed and developed by four engineers from Yahoo! – Mohammad Islam, Angelo Huang, Mayank Bansal, and Andreas Neumann. In addition, many outside contributors are actively contributing in design and development. Among them, Alejandro Abdelnur from Cloudera and Chao Wang from IBM are very important contributors. All of these core developers have deep expertise in Hadoop and the Hadoop Ecosystem in general. Alignment The ASF is a natural host for Oozie given that it is already the home of Hadoop, Pig, Hive, and other emerging cloud software projects. Oozie was designed to support Hadoop from the beginning in order to solve data processing challenges in Hadoop clusters. Oozie complements the existing Apache cloud computing projects by providing a flexible framework for managing complex data processing tasks. Known Risks Orphaned Products The core developers plan to work full time on the project. There is very little risk of Oozie getting orphaned since large companies like Yahoo! are extensively using it on their production Hadoop clusters. For example, there are nearly 400 Yahoo! internal Oozie users and thousands of jobs are processed hourly through Oozie in production. In addition, there are nearly 400 active users (including Yahoo! internal and external) in the email community where nearly 15 emails are exchanged per day. Furthermore, there were more than 1500 downloads of the Oozie binary in the last eight months from the github site and a large number of downloads were conducted by other companies such as Cloudera. Oozie has three major releases and more than 15 patch releases in the last couple of years which further demonstrates Oozie as a very active project. We plan to extend and diversify this community further through Apache. Inexperience with Open Source The core developers are all active users and followers of open source. They are already committers and contributors to the Oozie Github project. In addition, they are very familiar with Apache principals and philosophy for community driven software development. Homogeneous Developers The core developers are from Yahoo! as well as from several other corporations, including Cloudera and IBM. Reliance on Salaried Developers Currently, the developers are paid to do work on Oozie. Companies like Yahoo! and Cloudera are invested
