From general-return-24403-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Tue Jan 12 15:06:42 2010 Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 62280 invoked from network); 12 Jan 2010 15:06:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jan 2010 15:06:40 -0000 Received: (qmail 90091 invoked by uid 500); 12 Jan 2010 15:06:40 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 89852 invoked by uid 500); 12 Jan 2010 15:06:39 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Delivered-To: moderator for general@incubator.apache.org Received: (qmail 70125 invoked by uid 99); 12 Jan 2010 13:52:55 -0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gsiasf@gmail.com designates 209.85.210.174 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=K8AkrS1oaAo9TxrnEWcJmZsd/6oBecSoUtw88QUMka4=; b=rtfJNWfE+beBMW6MKd+IYxKuvLl4K9h/Q9Hmc3J/JAZIIRIpCKBOS0cmZAsVIz91YP SUHuTUSTBMgXFMlg7y6fvoQVwbcpoksl4VlxvABPgvUQ9czAymUDEmZP/1d1HDYRR+IJ r4GMHVPTeGtxoMVXDfNIe9kJIhTTqK5V3HVVg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=bV8u0j1sdCXsUrx3q3cs13DVnJdxh1lNjOUL7u2ZGbQvuY+S58SQ5yr3AnWZYRIw+e w03vu0DVz5cS3RE5PAARNWY9hbnGH6DFs0++TEzTQsf8w2yogHAdiiiItkoOl8OsPwix 1jjNJypmimXsYOwbqhosaKGU7I0MLI70h6DNE= Sender: Grant Ingersoll Subject: Re: [Proposal] JPPF : a parallel processing framework for Java Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=iso-8859-1 From: Grant Ingersoll In-Reply-To: <4B4C6A11.6080904@gmail.com> Date: Tue, 12 Jan 2010 08:52:20 -0500 Cc: Laurent Cohen Content-Transfer-Encoding: quoted-printable Message-Id: <2D9D4C85-A6EB-45CE-923A-3B811353D8B9@apache.org> References: <4B4C6A11.6080904@gmail.com> To: general@incubator.apache.org X-Mailer: Apple Mail (2.1077) Seems like this might fit nicely with Hadoop. Has anyone approached = their PMC about sponsoring? On Jan 12, 2010, at 7:24 AM, Emmanuel Lecharny wrote: > Hi guys, >=20 > On behalf of the JPPF community, I'd like to bring the following > proposal for discussion within the Incubator. I had a meeting > with Laurent last week when he investigated about using MINA into > JPPF, and I suggested that this project could be a good fit for > the Incubator. >=20 > We will need mentors for this proposal >=20 > WDYT ? >=20 > Thanks! >=20 > http://wiki.apache.org/incubator/JppfProposal >=20 > --- Current Wiki Text below --- > =3D JPPF : a parallel processing framework for Java =3D > =3D=3D=3D Abstract =3D=3D=3D > JPPF enables applications with large processing power requirements to = be > run on any number of computers, in order to dramatically reduce their > processing time. This is done by splitting an application into smaller > parts that can be executed simultaneously on different machines. >=20 > =3D=3D=3D Proposal =3D=3D=3D > JPPF aims at facilitating the parallelization of computation-intensive > applications, with a focus on ease of use, performance and = reliability. >=20 > To achieve these goals, the framework comes with a number of = outstanding > features: >=20 > - Comprehensive, easy to use APIs: passing from a single-threaded > application model to a grid-based parallel model can be a daunting = task. > JPPF facilitates this work by providing developers with a set of APIs > that are simple, can be learned quickly and require a minimal or no > modification to the existing code. >=20 > - No configuration usage: in most environments, JPPF can be deployed > without any additional configuration burden. Nodes and application > clients will automatically dicover the servers on the network. The > server will automatically adapt to workload changes and optimize the > throughput. Required code and libraries will be automatically deployed > where they are needed. >=20 > - Dynamic grid scaling and self-repair: the JPPF grid is = fault-tolerant, > meaning that the failure of a node, or even a server, does not > compromise the jobs currently executing or scheduled. In most cases, = the > performance degradation will be barely noticeable, as JPPF = automatically > adapts to topology and workload changes. Furthermore, nodes and = servers > can be dynamically started and will be automatically recognized, > allowing JPPF to function in "crunch mode". In addition to this, JPPF > components benefit from automatic recovery functionalities. >=20 > - Job-level SLA: each job submitted to the JPPF grid runs within = limits > defined by its own SLA (service level agreement). This allows to = specify > the characteristics (i.e. available memory, processors, disk space, > operating systems, etc.) of the nodes a job can run on, as well as how > many nodes it can run on. As many functionalities in JPPF, this one = can > be dynamically adjusted, manually or automatically. >=20 > - Advanced Management and monitoring: full-fledged management and > monitoring features are provided out of the box: server and nodes = status > monitoring, detailed statistics and events, remote administration, > job-level real-time monitoring and management, charts, cpu utilization > (for billing). These functionalities are available via a graphical = user > interface as well as from the JPPF APIs. >=20 > - Integration with leading application and web servers: by complying > with the Java Connector Architecture 1.5 specification, JPPF = integrates > seamlessly with and completes the offering of leading J2EE application > servers: Apache Geronimo, JBoss, Glassfish, IBM Websphere, Oracle > Weblogic, Oracle OC4J. JPPF also integrates with GigaSpaces eXtreme > Application Platform and Apache Tomcat web server >=20 > - Extensibility: JPPF offers a number of hooks and extension points = that > allow users to extend the framework and adapt it to their own > requirements and needs. Such extension mechanisms are available for > custom management and monitoring MBeans, startup classes for grod > components, network data transformation/encryption, additional > load-balancing algorithms, alternate object serialization mechanisms. >=20 > =3D=3D=3D Background =3D=3D=3D > JPPF is a project being actively developed at SourceForge. It was > created to address a class of problems called "embarassingly = parallel", > which groups computational problems that can be decomposed into many > smaller sub-problems, that are independant from each other and that = can > thus be executed in parallel. >=20 > =3D=3D=3D Rationale =3D=3D=3D > Given these last years' emergence of technologies that make commodity > hardware, virtualization and cloud computing available to a = fast-growing > computing ecosystem, the project answers the need to execute > applications ever faster, with a low entry cost, while at the same = time > preserving historical technological investments. >=20 > =3D=3D Current Status =3D=3D > =3D=3D=3D Meritocracy =3D=3D=3D > MWe acknowledge that a meritocratic governance is the only way for the > project to grow and expand, in the spirit of open source and the ASF. = It > will benefit the project, its communities, the ASF, as well as the = outer > ecosystems. >=20 > =3D=3D=3D Community =3D=3D=3D > JPPF already has a relatively small, but steadily growing community of > users. Given the applicability of the project to numerous industries = and > technological areas such as scientific research, finance, > graphical/video rendering, telecoms, data mining, etc.., we are > confident that there is a very large growth potential for developers = and > users communities around JPPF. >=20 > =3D=3D=3D Core Developers =3D=3D=3D > JPPF was founded in April 2005 by Laurent Cohen (laurent.cohen at > jppf.org), who is currently the only active developer and code = committer. > The other active contributor is John Channing (john.channing at > gmail.com) who provides advice and peer review on the project's > architecture, design, requirements and promotion. > Other project members and former project contributors include: > - Domingos Creado (dcreado at users.sourceforge.net) > - Mahendra Kutare (mahendra.kutare at gmail.com) > - Guy Korland (Guy at gigaspaces.com) > - Fredreric Barachant (pepe-barachant at users.sourceforge.net) > - Peter Becker (nc-heuelhe at netcologne.de) > - Wolfgang Wagner (wolfgang.wagner at iname.com) > - Jay Yusko (jay.yusko at gensolco.com) >=20 > =3D=3D=3D Alignment =3D=3D=3D > The project is currently undergoing a refactoring of its network > communication infrastructure, relying essentially on Mina, in order to > provide a greater maintainability of the code, as well as extend its > scalability and provide new functionalities such as truly secure > communications and integration of other distributed computing models > (e.g. P2P, map/reduce). > JPPF also offers connectors for Geronimo and Tomcat. >=20 > =3D=3D Known Risks =3D=3D > =3D=3D=3D Orphaned products =3D=3D=3D > This is the main and most obvious risk of this project. The knowledge = of > the code is owned by a single developer, Laurent Cohen, who has > committed about 98% of the existing code in the current repository. We > are well aware of this problem, and it is our hope and challenge that > integrating the Apache community will inspire the growth of a strong > developers community around JPPF. >=20 > =3D=3D=3D Inexperience with Open Source =3D=3D=3D > JPPF was created as an Open Source project in April 2005, and has > remained so since. >=20 > =3D=3D=3D Homogenous Developers =3D=3D=3D > A single active developer implies homogeneity. >=20 > =3D=3D=3D Reliance on Salaried Developers =3D=3D=3D > ANo one is currently paid to work on JPPF. >=20 > =3D=3D=3D Relationships with Other Apache Products =3D=3D=3D > JPPF is currently refactoring its network communication infrastructure > with the help of Mina (which is how we came to find a sponsor). > The project's logging relies entirely on commons-logging and Log4j. > The project also provides connectors for Geronimo and Tomcat. > Builds are done with Ant, and we are currently looking at switching to > Maven-based builds. > We foresee that JPPF could be used by many other Apache projects to > speed-up the execution of unit tests by running them in parallel, and = to > serve as a basis for running distributed charge and load tests. > One of our samples uses Lucene to demonstrate a simple use of a > distributed framework for web search, crawling and indexing >=20 > =3D=3D=3D A Excessive Fascination with the Apache Brand =3D=3D=3D > Our main hope in joining the Apache community is that it will help = build > a strong developers and committers community around the project, and > remove its reliance on a single developer. We aim at achieving this > while attracting new users, in conformance with the Apache spirit and > policies. >=20 > =3D=3D Documentation =3D=3D > Information on JPPF can be found at: > http://www.jppf.org (main site, documentation and user forums) > http://sourceforge.net/projects/jppf-project (code repository, bug > tracker, features tracker) >=20 > =3D=3D Initial Source =3D=3D > OThe entire code for JPPF is held in a SourceForge CVS repository, and > has been so since the project's inception in April 2005. This entire > code base will be donated to Apache. > The source code has been licensed under the ASL 2.0 since August 2007. > Before that it was LGPL. > All artifacts in the trunk and existing branches (1 branch) are now > licensed under the ASL 2.0, with corresponding header when applicable. >=20 > =3D=3D External Dependencies =3D=3D > Other than the Apache products used in JPPF, the project currently > depends on the following ASL 2.0 compatible products/licenses: > - Rhino (MPL) > - JGoodies Looks (BSD) > - Groovy (ASL 2.0) > - Hazelcast (ASL 2.0) > - JUnit (CPL) > - MigLayout (BSD) > - Smart and Simple Web Crawler (ASL 2.0) >=20 > Dependencies on libraries with non AL-compatible licenses: > - JFreeChart (LGPL) - runtime dependency only > - SaverBeans SDK (LGPL) - in the process of being removed > - JAligner (GPL) > - Izpack (GPL) > - NSIS (zlib/libpng, bzip2, CPL) - in the process of being removed >=20 > =3D=3D Cryptography =3D=3D > JPPF does not have any cryptographic component. However, the > distribution includes a sample that shows encryption/decryption of = data > as a demonstration of one of its features. The sample is delivered = with > full source code and can be found at: > = http://www.jppf.org/wiki/index.php?title=3DExtending_and_Customizing_JPPF#= Transforming_and_encrypting_networked_data >=20 > =3D=3D Required Resources =3D=3D > Mailing lists >=20 > * jppf-private (with moderated subscriptions) > * jppf-dev > * jppf-commits > * jppf-user >=20 > Subversion Repository >=20 > * https://svn.apache.org/repos/asf/incubator/jppf >=20 > Issue Tracking >=20 > * JIRA (JPPF) >=20 > Others >=20 > * Web site: Confluence (JPPF) >=20 > =3D=3D Initial Committers =3D=3D > * Laurent Cohen (laurent.cohen at jppf.org) > * John Channing (john.channing at gmail.com) >=20 > =3D=3D Affiliations =3D=3D > None of the initial committers are paid by their employer, nor do they > represent their employer in any activity related to JPPF. >=20 > =3D=3D Sponsors =3D=3D > Champion >=20 > * Emmanuel Lecharny (elecharny at apache dot org) >=20 > Nominated Mentors >=20 > We are currently looking for mentors within the community. >=20 > Sponsoring Entity >=20 > * Apache Incubator >=20 >=20 > --=20 > Regards, > Cordialement, > Emmanuel L=E9charny > www.nextury.com >=20 >=20 >=20 > --------------------------------------------------------------------- > 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