[RESULT][VOTE] Kalumet to join Incubator
Hello, The vote has passed with the following result : + 1 (binding) : Jean-Baptiste Onofré, Alan D. Cabrera, Marcel Offermans, Brett Porter, Mohammad Nour El-Din, Olivier Lamy + 1 (non binding) : Simone Tripodi, Joey Echeverria, David Blevins, Henri Gomez, Ashish Paliwal, Jamie Mark Goodyear, foxmask (no real name sorry :-), Terri-Lynn Rimmer, It looks the vote is fine : now time to hack :-). I will proceed with all the various tasks (ml creation, jira etc...) later this week. Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Kalumet to join Incubator
Hi, thanks all for your votes. I gonna work with Olivier to create and import the resources. Regards JB On 09/20/2011 09:56 AM, Olivier Lamy wrote: Hello, The vote has passed with the following result : + 1 (binding) : Jean-Baptiste Onofré, Alan D. Cabrera, Marcel Offermans, Brett Porter, Mohammad Nour El-Din, Olivier Lamy + 1 (non binding) : Simone Tripodi, Joey Echeverria, David Blevins, Henri Gomez, Ashish Paliwal, Jamie Mark Goodyear, foxmask (no real name sorry :-), Terri-Lynn Rimmer, It looks the vote is fine : now time to hack :-). I will proceed with all the various tasks (ml creation, jira etc...) later this week. Thanks, -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
+1 (binding) On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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
Re: [VOTE] Kalumet to join Incubator
hmm looks like I'm late :) good luck any way On Tue, Sep 20, 2011 at 10:53 AM, Julien Vermillard jvermill...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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
Re: [VOTE] Kalumet to join Incubator
+1 (binding) Tommaso 2011/9/20 Julien Vermillard jvermill...@gmail.com +1 (binding) On Mon, Sep 19, 2011 at 9:51 PM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: +1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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
Re: [VOTE] Kalumet to join Incubator
+1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
+1 (binding) On Mon, Sep 19, 2011 at 4:23 PM, trimmer one.pro.gram...@gmail.com wrote: +1 (non-binding) Cheers, Terri-Lynn Rimmer -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32495487.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
+1 (binding) On 13/09/2011, at 5:18 PM, Olivier Lamy wrote: Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
+1 (non-binding) Cheers, Jamie - Jamie Goodyear Blog: http://icodebythesea.blogspot.com/ Open Source SOA http://fusesource.com -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32463104.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
Hi, +1 (non-binding) Cheers. -- View this message in context: http://old.nabble.com/-VOTE--Kalumet-to-join-Incubator-tp32453584p32463185.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Kalumet to join Incubator
Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) == Core Developers == The core developers for AutoDeploy/Apache Kalumet project are : * Jean-Baptiste Onofré (founder in 2004). * Mike Duffy, WebSphere Consultant, contributes since 2005. == Open Source == Since the beginning, AutoDeploy was a Open Source project using GPL license. It switched to Apache 2.0 license in 2009, approved by all AutoDeploy developers (IP Clearance). As all AutoDeploy contributors has approved, Apache Kalumet uses the
Re: [VOTE] Kalumet to join Incubator
non-binding +1, look *really* interesting!!! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Tue, Sep 13, 2011 at 9:18 AM, Olivier Lamy ol...@apache.org wrote: Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) == Core Developers == The core developers for AutoDeploy/Apache Kalumet project are : * Jean-Baptiste Onofré (founder in 2004). * Mike Duffy, WebSphere Consultant,
Re: [VOTE] Kalumet to join Incubator
+1 (non-binding) On Sep 13, 2011, at 3:18, Olivier Lamy ol...@apache.org wrote: Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) == Core Developers == The core developers for AutoDeploy/Apache Kalumet project are : * Jean-Baptiste Onofré (founder in 2004). * Mike Duffy, WebSphere Consultant, contributes since 2005. == Open Source == Since the beginning,
Re: [VOTE] Kalumet to join Incubator
+1 (binding) -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: Olivier Lamy ol...@apache.org To: general@incubator.apache.org Subject: [VOTE] Kalumet to join Incubator Date: Tue, Sep 13, 2011 9:18 am Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) == Core Developers == The core developers for AutoDeploy/Apache Kalumet project are : * Jean-Baptiste Onofré (founder in 2004). * Mike Duffy, WebSphere Consultant
Re: [VOTE] Kalumet to join Incubator
+1 binding Regards, Alan On Sep 13, 2011, at 12:18 AM, Olivier Lamy wrote: The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason:
Re: [VOTE] Kalumet to join Incubator
+1 (wondering if it's binding or not) 2011/9/13 j...@nanthrax.net j...@nanthrax.net: +1 (binding) -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: Olivier Lamy ol...@apache.org To: general@incubator.apache.org Subject: [VOTE] Kalumet to join Incubator Date: Tue, Sep 13, 2011 9:18 am Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http
Re: [VOTE] Kalumet to join Incubator
+1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Kalumet to join Incubator
Looks very interesting! +1 (non-binding) -David On Sep 13, 2011, at 12:18 AM, Olivier Lamy wrote: Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) == Core Developers == The core developers for AutoDeploy/Apache Kalumet project are : * Jean-Baptiste Onofré (founder in 2004). * Mike Duffy, WebSphere Consultant, contributes since 2005. == Open Source ==
Re: [VOTE] Kalumet to join Incubator
+1 On Tue, Sep 13, 2011 at 12:48 PM, Olivier Lamy ol...@apache.org wrote: Hello Folks, Please vote on the acceptance of Kalumet into the Apache incubator. The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal (for your convenience, a snapshot is also copied below) The vote options (please cast your vote) : [ ] +1 Accept Kalumet for incubation [ ] +0 Don't care [ ] -1 Reject for the following reason: The vote is open for 72 hours. Here my (binding) +1 . Thanks, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy = Kalumet - Complete Environment Deployer Toolbox = == Abstract == Kalumet a complete environment manager and deployer including J2EE environments (application servers, applications, etc), softwares, and resources. It's a perfect complement to continuous integration (managed by maven and continuum or jenkins for instance) by adding continuous deployment. The whole factory chain is cover and the software administrator managed all environments in secure and safe way, whatever the underlying application servers (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares (printout system, Apache HTTPd, operating systems, etc) are. Kalumet provides two kind of components : * Apache Kalumet agent are installed locally on the target server box. * Apache Kalumet console controls and manages the agents, allowing the software administrator to update all environments from a central multi-user web tool. == Background == Currently, Apache Kalumet is named BuildProcess AutoDeploy (http://buildprocess.sourceforge.net). The development has begun 4 years ago and several release have already been provided. == Rationale == The software environments administration is heavy cost task with a high level of human actions, especially when mixing J2EE environments, different operating systems, softwares, etc It suffers : * a different set of scripts or actions/procedures depending of the application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere, ...) or other middlewares (portals or ESB like ServiceMix, HTTP servers like Apache HTTPd, etc); * a high level of risk due to human actions (for example, an administrator can forget to deploy a JDBC DataSource, or forget to change an application configuration file); * migrate an application from an environment to another one request boring actions (for example, migration applications and all linked resources from a testing environment to a production one, this action is named promote); * the upgrade process can be long (depending of the number of applications and complexity); * most of resources are stored on the application server box, not in a central repository. Apache Kalumet secures the environment deployment and covers the whole environment scope including J2EE parts (EAR/WAR archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and resources (operating systems, softwares, etc) in a unique way. It's heavily expendable, that means that you can create new plugins for dedicated resources. == Initial Goals == When we have begun AutoDeploy, the first goal was to provide several J2EE application servers JMX plugins. But quickly, we have seen that multi-application servers support was only a part of the software administration needs. That's why we have extended AutoDeploy to provide agents and a central console hosting all environments knowledges (artifact versions, resources, etc). Using the console, several administrators can use a central tool to manage all environments in a collaborative, unique and secure way. The target is now to provide a complete tool to fully administrate a data center servers, softwares and middlewares. = Current Status = Currently, BuildProcess AutoDeploy provides two branches : * the 0.5 branch (with the 0.5.6 latest release) is the current stable branch. This branch is built every night using Apache Continuum (http://continuum.nanthrax.net). * the 0.6 branch is in progress and it's the target one to become Apache Kalumet == Community == Currently, AutoDeploy community contains two comitters, 5 contributors and around 50 users. BuildProcess AutoDeploy is used in production and test in several companies : * Fimasys France (http://www.fimasys.com) * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au) * Vodacom South Africa (http://www.vodacom.com) * Mayo Clinic USA (http://www.mayoclinic.com) * NSW Attorney General Australia (http://www.lawlink.nsw.gov.au) == Core Developers == The core developers for AutoDeploy/Apache Kalumet project are : * Jean-Baptiste Onofré (founder in 2004). * Mike Duffy, WebSphere Consultant, contributes since 2005. == Open Source == Since the beginning, AutoDeploy was a Open Source project using GPL
