incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From " Jean-Baptiste Onofré" ...@nanthrax.net>
Subject Re: [PROPOSAL] Apache Scrum
Date Thu, 18 Dec 2008 10:22:57 GMT
Hi Andrus,

You can browse the subversion code repository and recommand to take a look on the
0.5.4 branch.

Currently, there is not a lot of documentation (I need to produce one) but,
anyway, quickly :), the deployment flow is :
Step 0 : init VFS file manipulator
Step 1 : check if an update is already in progress or add the new one in the
update queue
Step 2 : parse the AutoDeploy XML description file (can be local or remote
delivered by WebAutoDeploy)
Step 3 : create a update journal log
Step 4 : send notification and wait a countdown
Step 5 : update JEE application servers
  5.1 : update JDBC connection pools
  5.2 : update JDBC datasources
  5.3 : update JMS connection factories
  5.4 : update JMS servers (including queues and topics)
  5.5 : update JNDI name space bindings
  5.6 : update shared libraries
  5.7 : update JEE applications
    5.7.1 : update application configuration file (in the classpath) with
applying regexp
    5.7.2 : update application database (launch SQL script on the database)
    5.7.3 : update application content manager (with content manager plugin)
    5.7.4 : update application archive (EAR or WAR)
  5.8 : stop/start of application server and cache cleaning
Step 6 : udpate external software
Step 7 : send update log (by e-mail)

All this step can be bypassed or not.

For a live demo, you can try :
http://autodeploy.j2ee.fimasys.fr

using 
user : demo
pass : demo

It's not really a demo : you have a read only access to a small part of an
AutoDeploy production environment (that manages around 130 JEE environments using
JBoss, Weblogic, Websphere).

Regards
JB
--
Jean-Baptiste Onofré
jb@nanthrax.net
BuildProcess/AutoDeploy Project Leader
http://buildprocess.sourceforge.net

On Thu 18/12/08 10:58, Andrus Adamchik andrus@objectstyle.org wrote:
> Hi JB,
> 
> A very interesting problem you are addressing with AutoDeploy. JEE  
> deployment tools that I've seen to date don't scale too well, so this 
> 
area can use lots of improvement. I've developed a similar system for 
> 
a big site of one of our customers, with the main goal to manage a mid-
> 
size cluster (10-100 app server nodes) running Jetty. The main idea is 
> 
the same - write an XML descriptor to describe the cluster layout and 
> 
app destinations, and then write the tools around that descriptor  
> (deployment, monitoring and what not). But of course the tools is  
> where YMMV, and I am happy to see someone else building such tools :-)
> 
> I downloaded AutoDeploy-0.5.3 (BTW, noticed that the jar files are all 
> 
duplicated under lib/ and target/ increasing the size of the download 
> 
to 140MB. Poking around the code now. In the meantime a few questions 
> 
- do you have a demo system somewhere that would allow to play with  
> the UI without deploying the app? Also are there any diagrams on the  
> deployment flow implemented in AutoDeploy?
> 
> 
> Thanks,
> Andrus
> 
> 
> On Dec 17, 2008, at 11:01 PM, Jean-Baptiste Onofré wrote:
> > Hi,
> >
> > I would like to introduce my Apache Scrum
> proposal.
>
> > Abstract
> >   Apache Scrum is a complete environment manager and
> deployer  
> including JEE applications
> >   and resources.
> >   It's a perfect complement to continuous
> integration by adding  
> continuous deployment.
> >   The whole software factory chain is cover and the
> JEE  
> administrator managed all environments
> >   is a secure and safe way, whatever the underlying
> application  
> server is.
> >
> > Proposal
> >   Apache Scrum provides two components :
> >   - Apache Scrum agent are installed localy on the
> application  
> server server
> >   - Apache Scrum console controls and manages
> agents, allowing the  
> JEE administrator to update
> >     all environments from a central web
> tool.
>
> > Background
> >   Currently, Apache Scrum is named BuildProcess
> AutoDeploy (http://buildprocess.sourceforge.net 
> ).
> >   The development has begun 4 years ago and several
> release have  
> been already provided.
> >   AutoDeploy is used in several companies like
> Fimasys (http://www.fimasys.com 
> ), Vodacom South Africa
> >   (http://www.vodacom.com), Mayo Clinic USA (http://
> 
> www.mayocinic.com),
> etc.
>
> > Rationale
> >   The JEE environments administration is heavy cost
> task with a high  
> level on human action. It suffers :
> >   - a different set of script or actions dependning
> of the  
> application server used (JBoss, Websphere, Weblogic,
> etc)
>   - a high level of risk due to human action (for
> exemple, an  
> administrator can forget to deploy a JDBC
> datasource,
>     or forget to change an application specific
> configuration file)
>   - the upgrade process can be long (depending of
> the applications  
> complexity)
> >   - most of resources are stored localy to the
> application server,  
> not in a central repository
> >   Apache Scrum securise the environment deployment
> and cover the  
> whole JEE scope (EAR/WAR archives, JDBC
> datasources,
>   JMS queues, JMS topics, classloader policy, etc)
> in a uniq way  
> whatever the underlying application server (it
> heavely
>   uses JMX to interact with compatible
> middlewares).
>
> > Initial Goals
> >   When I have begun AutoDeploy, my first goal was to
> provide several  
> application server JMX plugins. But quickly, I
> have
>   seen that multi-application servers support was
> only a small part  
> of the JEE administration need.
> >   That's why I have extended AutoDeploy to provide
> agents and a  
> central console. Using the console, several JEE
> administrators
>   can use a central tools to manage all environments
> in a  
> collaborative and secure way.
> >
> > Current Status
> >   Currently, AutoDeploy provides two branches
> :
>   - the 0.5.x branch (with the 0.5.4 lastest
> release) is the current  
> stable branche
> >   - the 0.6.x branch is target to become Apache
> Scrum
>
> > Community
> >   Currently the project contains two contributors
> and around 50 users.
>   Thanks to the popularity of ASF, the purpose is
> increase the  
> number of contributors to improve the functionnality
> cover
>   of Apache Scrum.
> >
> > Core Developers
> >   AutoDeploy/Apache Scrum was founded by
> Jean-Baptiste Onofré in  
> 2004. Mike Duffy, Vodacom JEE architect, contributes
> since
>   2005. Several contributors have provided patches
> on the project.
>
> > Open Source
> >   Since the beginning, AutoDeploy was a Open Source
> project using  
> GPL license.
> >   Apache Scrum will use the Apache 2
> license.
>
> > Relationships with Other Apache Products
> >   AutoDeploy/Apache Scrum heavely uses Apache
> products such as :
>   - lot of jakarta commons (espcailly
> VFS)
>   - maven/continuum for build/continuous
> integration
>   - xerces/xalan for XML manipulation
> >   - etc ...
> >
> > I hope that Apache Scrum provide a kind of interest
> to you :) and  
> really hope that the ASF approve this
> project.
> I think that the core product is efficient due to
> the number of  
> users on the current stable version. Joining ASF
> will increase
> the visibility of Scrum and increase the number of
> contributors, for  
> sure.
> >
> > If you have need more informations, or if you have
> some questions,  
> don't hesitate to contact me.
> >
> > Thanks in advance :)
> > Regards
> > JB
> >
> > [1] BuildProcess AutoDeploy (Apache Scrum)
> :
>   http://buildprocess.sourceforge.net
>> -- 
> > Jean-Baptiste Onofré (Nanthrax)
> > BuildProcess/AutoDeploy Project Leader
> > http://buildprocess.sourceforge.net
>> jb@nanthrax.n
> et
> PGP : 17D4F086
> >
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
> 
> 
> 



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


Mime
View raw message