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 Nanthrax
Date Sat, 10 Jan 2009 20:09:34 GMT
Dear Wiki user,

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

The following page has been changed by Nanthrax:
http://wiki.apache.org/incubator/KalumetProposal

------------------------------------------------------------------------------
  
  Kalumet - Complete Environment Deployer Toolbox
  
- We are proposing a whole platform to manage update of software environments.
+ We are proposing a complete environment manager and deployer including JEE applications
and resources.
+ It's a perfect complement to continuous integration (managed by maven and continuum for
example) 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, RedHat JBoss, Oracle W
+ Weblogic or IBM Websphere) is.
  
- Kalumet is mainly focus on JEE environments but support other a large number of middlewares.
+ Kalumet provides two kind of components :
  
- It's a perfect complement of a continuous integration chain (based on maven and continuum
for exemple) to deploy artifacts on target application servers, supporting all application
servers resources (JDBC DataSources, JMS Connection Factories, JMS Queues/Topics, etc) and
other feature (static content support in Apache, configuration files with regexp pattern,
etc).E
+ * Apache Kalumet agent are installed localy on the application server box.
+ 
+ * Apache Kalumet console controls and manages the agents, allowing the JEE 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.
+ 
+ BuildProcess AutoDeploy is used in production and test in several companies :
+ 
+ * Fimasys France (http://www.fimasys.com)
+ 
+ * Vodacom South Africa (http://www.vodacom.com)
+ 
+ * Mayo Clinic USA (http://www.mayoclinic.com)
+ 
+ * Attorney General Australia
+ 
+ * ...
  
  = RATIONALE =
  
- In progress ...
+ The JEE environments administration is heavy cost task with a high level of human actions.
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);
+ 
+ * a high level of risk due to human actions (for exemple, 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
exemple, 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 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 =
+ 
+ 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.
+ 
+ = CURRENT STATUS =
+ 
+ Currently, BuildProcess AutoDeploy provides two branches :
+ 
+ * the 0.5 branch (with the 0.5.4 latest release) is the current stable branch
+ 
+ * the 0.6 branch is in progress and it's the target one choosed to become Apache Kalumet
+ 
+ = 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.
+ 
+ = CORE DEVELOPERS =
+ 
+ AutoDeploy/Apache Kalumet was founded by Jean-Baptiste Onofré in 2004. Mike Duffy, Vodacom
JEE architect, contributes since 2005. Core users/testers are in Fimasys company.
+ 
+ = OPEN SOURCE =
+ 
+ Since the beginning, AutoDeploy was a Open Source project using GPL license.
+ 
+ As all AutoDeploy contributors has approved, Apache Kalumet uses the Apache 2 license.
+ 
+ = RELATIONSHIP WITH OTHER APACHE PRODUCTS =
+ 
+ AutoDeploy/Apache Kalumet heavily uses Apache resources such as :
+ 
+ * a lot of jakarta commons (especially VFS)
+ 
+ * maven/continuum for build/continuous integration
+ 
+ * xerces/xalan for XML manipulation
+ 
+ * etc ...
+ 
+ = ASF RESOURCES =
+ 
+ == Mailing Lists ==
+ 
+ * kalumet-user
+ 
+ * kalumet-dev
+ 
+ == SVN Repositories ==
+ 
+ * kalumet
+ 
+ == Issue Tracking ==
+ 
+ * Need a new Jira project named KALUMET
+ 
+ = INITIAL DEVELOPERS SET =
+ 
+ * Jean-Baptiste Onofré (Fimasys, jb@nanthrax.net)
+ 
+ = MENTORS =
+ 
+ * Jim Jagielski (jim@jaguNET.com)
+ 

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


Mime
View raw message