Re: [PROPOSAL] Provisionr join the Apache Incubator
On Fri, Mar 8, 2013 at 2:20 AM, Andrew Bayer andrew.ba...@gmail.com wrote: A little belated, but I'd be interested in helping out as well. You are welcome! :) -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
A little belated, but I'd be interested in helping out as well. A. On Sat, Mar 2, 2013 at 3:21 PM, Andrei Savu savu.and...@gmail.com wrote: I think the proposal is now ready for voting. I will go ahead and start a new thread. http://wiki.apache.org/incubator/ProvisionrProposal Thank you all! -- Andrei Savu On Fri, Mar 1, 2013 at 6:57 PM, Andrei Savu savu.and...@gmail.com wrote: On Fri, Mar 1, 2013 at 10:45 AM, Eric Sammer esam...@cloudera.com wrote: I'd love to be involved if you're actively looking for initial committers. I'm very familiar with OSGi, puppet, and the Hadoop ecosystem side of things. I'm (non-binding) +1 on accepting the project to the incubator. Thanks Eric and welcome to the team. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
The VOTE just closed so we can't modify the proposal, but I think we can grant karma once the project is up. On Thu, Mar 7, 2013 at 4:20 PM, Andrew Bayer andrew.ba...@gmail.com wrote: A little belated, but I'd be interested in helping out as well. A. On Sat, Mar 2, 2013 at 3:21 PM, Andrei Savu savu.and...@gmail.com wrote: I think the proposal is now ready for voting. I will go ahead and start a new thread. http://wiki.apache.org/incubator/ProvisionrProposal Thank you all! -- Andrei Savu On Fri, Mar 1, 2013 at 6:57 PM, Andrei Savu savu.and...@gmail.com wrote: On Fri, Mar 1, 2013 at 10:45 AM, Eric Sammer esam...@cloudera.com wrote: I'd love to be involved if you're actively looking for initial committers. I'm very familiar with OSGi, puppet, and the Hadoop ecosystem side of things. I'm (non-binding) +1 on accepting the project to the incubator. Thanks Eric and welcome to the team. -- Andrei Savu -- Eric Sammer twitter: esammer data: www.cloudera.com
Re: [PROPOSAL] Provisionr join the Apache Incubator
I think the proposal is now ready for voting. I will go ahead and start a new thread. http://wiki.apache.org/incubator/ProvisionrProposal Thank you all! -- Andrei Savu On Fri, Mar 1, 2013 at 6:57 PM, Andrei Savu savu.and...@gmail.com wrote: On Fri, Mar 1, 2013 at 10:45 AM, Eric Sammer esam...@cloudera.com wrote: I'd love to be involved if you're actively looking for initial committers. I'm very familiar with OSGi, puppet, and the Hadoop ecosystem side of things. I'm (non-binding) +1 on accepting the project to the incubator. Thanks Eric and welcome to the team. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi I would like to help and hence added myself as a mentor. Thanks for bringing the project to Apache. On Fri, Mar 1, 2013 at 7:02 AM, Andrei Savu savu.and...@gmail.com wrote: Hi David - On Thu, Feb 28, 2013 at 11:19 AM, David Nalley da...@gnsa.us wrote: I am interested in this. I know one or two things about puppet and cloud APIs. Not sure how many cycles I can expend. It would be great to have you part of the team. Feel free to edit the wiki. CloudStack support is very important for me and I'm going to spend a fair amount of time on that over the next cloud of weeks / months. -- Andrei Savu -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein
Re: [PROPOSAL] Provisionr join the Apache Incubator
On 27 February 2013 18:53, Andrei Savu savu.and...@gmail.com wrote: Hi Benson - Thanks for your feedback! It's too early to decide if there is an overlap between communities. Provisionr solves a different problem being focused on semi-automated workflows (e.g. with Rundeck) and cloud portability while Whirr is more focused on deploying services from the Hadoop stack. I had this conversation before with Tom. -- Andrei Savu I do support this, though lack time to commit to active participation. It is very different from whirr, but is built very much on other bits of the ASF codebase, especially Karaf. One thing I would recommend for the curious is to get a demo of it from Andrei; I saw one over G+ and it looked very nice. -Steve
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Fri, Mar 1, 2013 at 12:59 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: I would like to help and hence added myself as a mentor. Thanks for bringing the project to Apache. Thanks for joining! Your help is highly appreciated. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Thanks Steve! On Fri, Mar 1, 2013 at 3:43 AM, Steve Loughran steve.lough...@gmail.comwrote: One thing I would recommend for the curious is to get a demo of it from Andrei; I saw one over G+ and it looked very nice. Anyone should feel free to email me if they want a live demo. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Fri, Mar 1, 2013 at 10:45 AM, Eric Sammer esam...@cloudera.com wrote: I'd love to be involved if you're actively looking for initial committers. I'm very familiar with OSGi, puppet, and the Hadoop ecosystem side of things. I'm (non-binding) +1 on accepting the project to the incubator. Thanks Eric and welcome to the team. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Anyone else interested to join? We are still looking for mentors / initial contributor. If you are working with OSGi, Karaf, Activiti, Cloud APIs or Puppet it would be great to have you on-board as a mentor or contributor. I am at ApacheCon in Portland - feel free to get in touch if you want to know more. -- Andrei Savu On Wed, Feb 27, 2013 at 10:56 AM, Andrei Savu savu.and...@gmail.com wrote: I think the following presentation does a better job at explaining the scope of Provisionr: http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013 Regards, -- Andrei Savu On Wed, Feb 27, 2013 at 7:53 AM, Benson Margulies bimargul...@gmail.comwrote: On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi, Disclaimer: I am one of the developers. +1 This is a great project for the incubator. I'm also in Portland during ApacheCon, available for demos/questions . Cheers, -- Ioan Eugen Stan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Thu, Feb 28, 2013 at 1:52 PM, Andrei Savu savu.and...@gmail.com wrote: Anyone else interested to join? We are still looking for mentors / initial contributor. If you are working with OSGi, Karaf, Activiti, Cloud APIs or Puppet it would be great to have you on-board as a mentor or contributor. I am at ApacheCon in Portland - feel free to get in touch if you want to know more. I am interested in this. I know one or two things about puppet and cloud APIs. Not sure how many cycles I can expend. --David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi David - On Thu, Feb 28, 2013 at 11:19 AM, David Nalley da...@gnsa.us wrote: I am interested in this. I know one or two things about puppet and cloud APIs. Not sure how many cycles I can expend. It would be great to have you part of the team. Feel free to edit the wiki. CloudStack support is very important for me and I'm going to spend a fair amount of time on that over the next cloud of weeks / months. -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Provisionr shares no code with Whirr, but it would be natural for Whirr to use Provisionr for reliable cloud provisioning. Indeed, as the proposal states, This project started as a re-write of the core of Apache Whirr, so Provisionr is a sort of Next Generation Whirr. More importantly, in terms of community, Andrei is on the Whirr PMC and I think that the communities would have considerable overlap. It's worth deciding now, since there is an ongoing discussion about whether existing projects are suitable homes for newly graduated projects [1]. BTW Andrei, please put the proposal on the Incubator wiki so others can edit it, and so it's easy to find in the future. Thanks, Tom [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201302.mbox/%3ccabd8fluoxt71foldya60faebd4ys1-ovxapkkrufjn9hndd...@mail.gmail.com%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
Thanks Tom! On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: BTW Andrei, please put the proposal on the Incubator wiki so others can edit it, and so it's easy to find in the future. I have updated the proposal and posted it on the Incubator wiki: http://wiki.apache.org/incubator/ProvisionrProposal -- Andrei Savu
Re: [PROPOSAL] Provisionr join the Apache Incubator
Hi Benson - Thanks for your feedback! It's too early to decide if there is an overlap between communities. Provisionr solves a different problem being focused on semi-automated workflows (e.g. with Rundeck) and cloud portability while Whirr is more focused on deploying services from the Hadoop stack. I had this conversation before with Tom. -- Andrei Savu On Wed, Feb 27, 2013 at 7:53 AM, Benson Margulies bimargul...@gmail.comwrote: On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
I think the following presentation does a better job at explaining the scope of Provisionr: http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013 Regards, -- Andrei Savu On Wed, Feb 27, 2013 at 7:53 AM, Benson Margulies bimargul...@gmail.comwrote: On Wed, Feb 27, 2013 at 2:28 AM, Tom White tom.e.wh...@gmail.com wrote: On Tue, Feb 26, 2013 at 6:34 AM, Andrei Savu savu.and...@gmail.com wrote: Tom do you want to be a champion for this proposal? Yes, I'd be happy to. One thing I think is worth discussing more here is whether Provisionr should be a TLP on graduation, or whether it should be a module in Whirr. Well, that puts this proposal into a gray area. In case you haven't been reading all the traffic on this list, I'll give a quick summary here. Historically, the Foundation had 'subprojects', and the the incubator hosted podlings intended, eventually, to become subprojects of existing TLPs. We don't do that anymore. If Provisionr becomes part of Whir, it just becomes, well, part of Whir. That raises the question of what you need the incubator for if this is your goal. There's a pretty simple alternative. The existing Provisionr team works with Whir to do an IP grant of the code to the Foundation. The existing team submits ICLAs. Whir makes a branch or other distinctive tree in source control and grants the Provisionr team commit access _to that tree_. Over time, the Provisionr people earn full committer status by merit, and appropriate adjustments are made to the tree structure. Given the state of the conversation about policy on this subject, I think it would be reasonable to ask you all to talk to the Whir people about this, and see if you an all come to an agreement for something like this in parallel with a discussion here. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] Provisionr join the Apache Incubator
Hi guys - I would like to propose Provisionr to the Apache Incubator: https://github.com/axemblr/axemblr-provisionr/wiki/Provisionr-Proposal Provisionr is a service that wants to solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. I am looking forward to your feedback and suggestions. Thanks, -- Andrei Savu ## Abstract Provisionr is an effort to develop a service that can be used to create and manage pools of virtual machines on multiple clouds in an automatic or semi-automatic fashion. ## Proposal Provisionr solves the problem of cloud portability by hiding completely the APIs and only focusing on building a cluster that matches the same set of assumptions on all clouds, assumptions like: running a specific operating system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed packages and binaries, sane dns settings (forward reverse ip resolution - as needed for Hadoop), ntp settings, networking settings, firewall, ssh admin access, vpn access etc. As a secondary goal Provisionr should also provide primitives for building automatic or semi-automatic workflows for configuring services, workflows that assume that all the machines share a common set of characteristics as described above. ## Background Creating clusters on cloud infrastructure is non-trivial because careful orchestration is required. To make it easy to deploy services we need to start from a foundation that matches a common set of assumptions on multiple providers. ## Rationale This project started as a re-write of the core of Apache Whirr but has a different target being more focused on semi-automated workflows and cloud portability. ## Initial Goals * Build a community * Provide an excellent user experience for semi-automatic workflows (e.g. using Rundeck) * Implement a REST service and a Web Console * Add support for more providers ## Current Status Provisionr had four releases on GitHub and it's used to deploy Hadoop clusters on-demand at Axemblr and infrastructure for testing / QA. ### 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 community interested in cloud service infrastructure is currently spread across many smaller projects, and one of the main goals of this project is to build a vibrant community to share best practices and build common infrastructure. ### Core developers Core developers are very experienced in the Apache ecosystem. To achieve more diversity of developers, we will be eager to recruit developers from diverse companies. * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) * Alex Ciminian (not a committer) ### Alignment Provisionr complements Apache Whirr and later on it should provide a robust foundation for more advanced functionalities. ## Known Risks ### Orphaned products The contributors have significant open source experience and the project is being used as part of a commercial product, so the risk of being orphaned is relatively low. We plan to mitigate this risk by recruiting additional committers. ### Inexperience with Open Source Most of the initial committers have experience working on open source projects. Andrei Savu and Ioan Eugen Stan have experience as committers and PMC members on other Apache projects. ### Homogenous Developers We are committed to recruiting additional committers from other companies based on their contributions to the project. ### Reliance on Salaried Developers It is expected that Provisionr development will occur on both salaried time and on volunteer time, after hours. The majority of initial committers are paid by their employer to contribute to this project. However, they are all passionate about the project, and we are confident that the project will continue even if no salaried developers contribute to the project. We are committed to recruiting additional committers including non-salaried developers. ### Relationships with Other Apache Products Provisionr is closely integrated with Karaf, CXF in a numerous ways. We look forward to collaborating with those communities, as well as other Apache communities. ### A Excessive Fascination with the Apache Brand We
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Mon, Feb 25, 2013 at 2:53 PM, Andrei Savu as...@apache.org wrote: ... ### Mailing lists * provisionr-private * provisionr-dev * provisionr-user A user list is not recommended for a new community. That only serves to divide a limited number of people. Your users should be involved on the dev@ list until the user influx becomes distracting. It may be advisable to have a -commits list, but sending all commits to the -dev list is also workable. ... ## Sponsors ### Champion Andrei Savu - asavu at apache dot org Champions must be an Officer or a Member of the Foundation. Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Provisionr join the Apache Incubator
On Tue, Feb 26, 2013 at 5:26 AM, Greg Stein gst...@gmail.com wrote: A user list is not recommended for a new community. That only serves to divide a limited number of people. Your users should be involved on the dev@ list until the user influx becomes distracting. Good point. Thanks! It may be advisable to have a -commits list, but sending all commits to the -dev list is also workable. I would prefer to do only send JIRA updates on the dev- list with a Review-Then-Commit development process. Champions must be an Officer or a Member of the Foundation. Tom do you want to be a champion for this proposal? -- Andrei Savu
