incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "KalumetProposal" by OlivierLamy
Date Fri, 26 Aug 2011 17:23:01 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "KalumetProposal" page has been changed by OlivierLamy:
http://wiki.apache.org/incubator/KalumetProposal?action=diff&rev1=21&rev2=22

- = PROJECT PROPOSAL =
+ = Kalumet - Complete Environment Deployer Toolbox =
  
- Kalumet - Complete Environment Deployer Toolbox
+ == Abstract ==
  
- We are proposing a complete environment manager and deployer including JEE applications
and resources.
+ Kalumet a complete environment manager and deployer including JEE applications and resources.
+ It's a perfect complement to continuous integration (managed by maven and continuum or jenkins
for instance) by adding continuous deployment. 
- 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 JEE
administrator managed all environments in secure and safe way, whatever the underlying application
server (Apache Geronimo, Apache Tomcat, Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM
Websphere) is.
+ The whole factory chain is cover and the JEE administrator managed all environments in secure
and safe way, whatever the underlying application server (Apache Geronimo, Apache Tomcat,
Apache TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) is.
  
  Kalumet provides two kind of components :
  
@@ -13, +14 @@

  
  * Apache Kalumet console controls and manages the agents, allowing the JEE administrator
to update all environments from a central multi-user web tool.
  
- = BACKGROUND =
+ == 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 ==
- 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)
- 
- * ...
- 
- = RATIONALE =
  
  The JEE environments administration is heavy cost task with a high level of human actions.
It suffers :
  
@@ -47, +34 @@

  
  Apache Kalumet secures the environment deployment and covers the whole JEE scope (EAR/WAR
archives with classloader policy, JDBC DataSources, JMS Connection Factories, JMS Queues/Topics,
etc) in a unique way whatever the underlying application server is (it heavily uses JMX to
interact with compatible middlwares).
  
- = INITIAL GOALS =
+ == Initial Goals ==
  
  When we have begun AutoDeploy, the first goal was to provide several application servers
JMX plugins. But quickly, we have seen that multi-application servers support was only a part
of the JEE 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 JEE
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, softwares
and middlewares.
+ The target is now to provide a complete tool to fully administrate a data center servers,
softwares and middlewares.
  
- = CURRENT STATUS =
+ = Current Status =
  
  Currently, BuildProcess AutoDeploy provides two branches :
  
@@ -63, +50 @@

  
  * the 0.6 branch is in progress and it's the target one choosed to become Apache Kalumet
  
- = COMMUNITY =
+ == Community ==
  
  Currently, AutoDeploy community contains two developers and around 50 users.
- Thanks to the popularity of ASF, the purpose is to increase the number of contributors to
improve the functionality cover of Apache Kalumet.
+ BuildProcess AutoDeploy is used in production and test in several companies :
  
- = CORE DEVELOPERS =
+ * Fimasys France (http://www.fimasys.com)
  
- AutoDeploy/Apache Kalumet was founded by Jean-Baptiste Onofré in 2004. Mike Duffy, WebSphere
Consultant, contributes since 2005.
+ * AMP-AXA Australia (https://www.amp.com.au/wps/portal/au)
  
- = OPEN SOURCE =
+ * 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 license in 2009, approved by all AutoDeploy developers.
  
  As all AutoDeploy contributors has approved, Apache Kalumet uses the Apache 2 license.
  
  AutoDeploy Console currently use NextApp Echo2 framework, released under Mozilla Public
License, which is a Category B license.
- The Apache incubation phase will use Echo2, acting that we have to switch to an Apache compliant
framework (Pax Wicket and Vaadin could be used).
+ The Apache incubation phase will use Echo2, acting that we have to switch to an Apache compliant
framework (Pax Wicket and Vaadin could be used) before any TLP graduation.
  
- = RELATIONSHIP WITH OTHER APACHE PRODUCTS =
+ = Known Risks =
  
- AutoDeploy/Apache Kalumet heavily uses Apache resources such as :
+ == Orphaned Products ==
  
- * a lot of jakarta commons (especially VFS)
+ AutoDeploy is already deployed in production at multiple companies. (see Community Section)

+ AutoDeploy is getting traction with developers and thus the risks of it being orphaned are
minimal.
  
- * maven/continuum for build/continuous integration
+ == Inexperience with Open Source ==
  
- * xerces/xalan for XML manipulation
+ All code developed for AutoDeploy has been open source from the start (see Open Source section).
+ And mostly by an ASF member Jean-Baptiste Onofre who is intimately familiar with the Apache
model for open-source development and is experienced with working with new contributors. 
+ Jean-Baptiste Onofre, the creator of the project and one of the committers is also a committer
on Apache Karaf, Apache ServiceMix, Apache Camel and Apache Ace.
  
- * etc ...
+ == Homogeneous Developers ==
  
- = ASF RESOURCES =
+ The initial set of committers is from a small set of organizations. However, we expect that
once approved for incubation, the project will attract new contributors from diverse organizations
and will thus grow organically. The participation of developers from several different organizations
in the mailing list is a strong indication for this assertion.
  
+ == Reliance on Salaried Developers ==
+ 
+ It is expected that Kalumet will be developed on salaried and volunteer time, although all
of the initial developers will work on it mainly on salaried time.
+ 
+ == Relationships with Other Apache Products ==
+ 
+ AutoDeploy/Apache Kalumet depends upon other Apache Projects: Xerces, Xalan and multiple
Apache cCommons components and build systems like Maven.
+ 
+ == A Fascination with the Apache Brand ==
+ 
+ The reason for joining Apache is to foster a healthy community of contributors and consumers
around the project. This is facilitated by ASF and that is the primary reason we would like
Kalumet to become an Apache project.
+ 
+ = Documentation =
+ 
+ AutoDeploy docs: http://buildprocess.sourceforge.net/autodeploy.html
+ 
+ == Initial Source ==
+ 
+ https://buildprocess.svn.sourceforge.net/svnroot/buildprocess/AutoDeploy/
+ 
+ == Source and Intellectual Property Submission Plan ==
+ 
+ The initial source is already Apache 2.0 licensed.
+ 
+ == External Dependencies ==
+ 
+ The required external dependencies are all Apache License or compatible licenses. Following
components with non-Apache licenses are enumerated:
+ 
+ * Echo Web framework Mozilla Public License, which is a Category B license (see plan to
remove this dependency)
+ 
+ == Cryptography == 
+ 
+ Kalumet does not depend upon any cryptography tools or libraries.
+ 
+ = Required Resources =
+ 
- == Mailing Lists ==
+ == Mailing lists ==
+ 
+ * kalumet-private (with moderated subscriptions)
+ 
+ * kalumet-dev
+ 
+ * kalumet-commits
  
  * kalumet-user
  
- * kalumet-dev
+ == Subversion Directory ==
  
+ https://svn.apache.org/repos/asf/incubator/kalumet
- == SVN Repositories ==
- 
- * kalumet
  
  == Issue Tracking ==
  
- * Need a new Jira project named KALUMET
+ JIRA Kalumet (Kalumet)
  
- = INITIAL DEVELOPERS SET =
+ == Other Resources ==
+ 
+ The existing code already has unit and integration tests so we would like a Jenkins instance
to run them whenever a new patch is submitted. This can be added after project creation.
+ 
+ == Initial Committer ==
  
  * Jean-Baptiste Onofré (jbonofre@apache.org)
  
@@ -123, +171 @@

  
  * Jamie Goodyear (jgoodyear@apache.org)
  
- = MENTORS =
+ == Affiliations ==
+ 
+ * Jean-Baptiste Onofré, Talend
+ 
+ = Sponsors =
+ 
+ == Champion ==
+ 
+ * Olivier Lamy (olamy@apache.org)
+ 
+ == Nominated Mentors ==
  
  * Jim Jagielski (jim@apache.org)
  
- * Olivier Lamy (olamy@apache.org)
- 

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message