Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: <EBA576AE-64C7-4D3B-9261-DD51D31CA094@objectstyle.org>
From: Andrus Adamchik <andrus@objectstyle.org>
To: general@incubator.apache.org
In-Reply-To: <20081217210140.GD30594@gandalf.nanthrax.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: [PROPOSAL] Apache Scrum
Date: Thu, 18 Dec 2008 11:58:23 +0200
References: <20081217210140.GD30594@gandalf.nanthrax.net>

Hi JB,

A very interesting problem you are addressing with AutoDeploy. JEE =20
deployment tools that I've seen to date don't scale too well, so this =20=

area can use lots of improvement. I've developed a similar system for =20=

a big site of one of our customers, with the main goal to manage a mid-=20=

size cluster (10-100 app server nodes) running Jetty. The main idea is =20=

the same - write an XML descriptor to describe the cluster layout and =20=

app destinations, and then write the tools around that descriptor =20
(deployment, monitoring and what not). But of course the tools is =20
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 =20=

duplicated under lib/ and target/ increasing the size of the download =20=

to 140MB. Poking around the code now. In the meantime a few questions =20=

- do you have a demo system somewhere that would allow to play with =20
the UI without deploying the app? Also are there any diagrams on the =20
deployment flow implemented in AutoDeploy?


Thanks,
Andrus


On Dec 17, 2008, at 11:01 PM, Jean-Baptiste Onofr=E9 wrote:
> Hi,
>
> I would like to introduce my Apache Scrum proposal.
>
> Abstract
>   Apache Scrum is a complete environment manager and deployer =20
> including JEE applications
>   and resources.
>   It's a perfect complement to continuous integration by adding =20
> continuous deployment.
>   The whole software factory chain is cover and the JEE =20
> administrator managed all environments
>   is a secure and safe way, whatever the underlying application =20
> server is.
>
> Proposal
>   Apache Scrum provides two components :
>   - Apache Scrum agent are installed localy on the application =20
> server server
>   - Apache Scrum console controls and manages agents, allowing the =20
> JEE administrator to update
>     all environments from a central web tool.
>
> Background
>   Currently, Apache Scrum is named BuildProcess AutoDeploy =
(http://buildprocess.sourceforge.net=20
> ).
>   The development has begun 4 years ago and several release have =20
> been already provided.
>   AutoDeploy is used in several companies like Fimasys =
(http://www.fimasys.com=20
> ), Vodacom South Africa
>   (http://www.vodacom.com), Mayo Clinic USA (http://=20
> www.mayocinic.com), etc.
>
> Rationale
>   The JEE environments administration is heavy cost task with a high =20=

> level on human action. It suffers :
>   - a different set of script or actions dependning of the =20
> application server used (JBoss, Websphere, Weblogic, etc)
>   - a high level of risk due to human action (for exemple, an =20
> 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 =20
> complexity)
>   - most of resources are stored localy to the application server, =20
> not in a central repository
>   Apache Scrum securise the environment deployment and cover the =20
> whole JEE scope (EAR/WAR archives, JDBC datasources,
>   JMS queues, JMS topics, classloader policy, etc) in a uniq way =20
> 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 =20=

> application server JMX plugins. But quickly, I have
>   seen that multi-application servers support was only a small part =20=

> of the JEE administration need.
>   That's why I have extended AutoDeploy to provide agents and a =20
> central console. Using the console, several JEE administrators
>   can use a central tools to manage all environments in a =20
> 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 =20=

> 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 =20
> number of contributors to improve the functionnality cover
>   of Apache Scrum.
>
> Core Developers
>   AutoDeploy/Apache Scrum was founded by Jean-Baptiste Onofr=E9 in =20
> 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 =20
> 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 =20
> really hope that the ASF approve this project.
> I think that the core product is efficient due to the number of =20
> users on the current stable version. Joining ASF will increase
> the visibility of Scrum and increase the number of contributors, for =20=

> sure.
>
> If you have need more informations, or if you have some questions, =20
> don't hesitate to contact me.
>
> Thanks in advance :)
> Regards
> JB
>
> [1] BuildProcess AutoDeploy (Apache Scrum) :
>   http://buildprocess.sourceforge.net
> --=20
> Jean-Baptiste Onofr=E9 (Nanthrax)
> BuildProcess/AutoDeploy Project Leader
> http://buildprocess.sourceforge.net
> jb@nanthrax.net
> 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