Re: ASF: what do we have left?
On Mon, Jan 11, 2010 at 7:12 PM, Craig L Russell craig.russ...@sun.com wrote: When we discussed graduation requirements on the incubator general list, the idea was to have the incubator review a release made by the team, and review the process of releasing. my exams are next week but should then be free(ish) for a couple of weeks after then - robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Lucene Connector Framework Kickoff
Hi Grant, For those of us new to working with apache, could you give a quick overview of the best way to communicate among group members? Specifically, what sorts of posts should be sent to gene...@incubator, and what sorts should go to gene...@lucene? Also, I am in the process of determining the strategy and the exact list of files for the software grant from MetaCarta, and I'd love to get people's feedback as to what should be included, and how. What list would be appropriate for that? Should we set one up? Thanks again, Karl Wright Grant Ingersoll wrote: Hi All, (Please keep replies to general@incubator.apache.org) I opened the following JIRA issues for starting LCF: https://issues.apache.org/jira/browse/INFRA-2431 I need two volunteers from the list of committers to be moderators. Please signify your willingness to be a committer by adding your name to the JIRA ticket. Confluence Wiki: https://issues.apache.org/jira/browse/INFRA-2432 JIRA project https://issues.apache.org/jira/browse/INFRA-2433 I added SVN at: https://svn.apache.org/repos/asf/incubator/lcf/ The following people need to submit iCLAs: Brian Pinkerton Karl Wright (kwright at metacarta) Josiah Strandberg (jstrandberg at metacarta) Ken Baker (bakerkj at metacarta) Marc Meadows (mam at metacarta) Once they are on file, I can request accounts. Everyone else should have permission to commit, as they are existing committers. Cheers, Grant -- Karl Wright Software Engineer MetaCarta, Inc. 350 Massachusetts Avenue, 4th Floor, Cambridge, MA 02139 USA (617)-301-5511 www.metacarta.com http://www.metacarta.com Where to find it. This message may contain privileged, proprietary, and otherwise private information. If you are not the intended recipient, please notify the sender immediately. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Proposal] JPPF : a parallel processing framework for Java
Hi guys, 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. We will need mentors for this proposal WDYT ? Thanks! http://wiki.apache.org/incubator/JppfProposal --- Current Wiki Text below --- = JPPF : a parallel processing framework for Java = === Abstract === 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. === Proposal === JPPF aims at facilitating the parallelization of computation-intensive applications, with a focus on ease of use, performance and reliability. To achieve these goals, the framework comes with a number of outstanding features: - 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. - 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. - 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. - 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. - 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. - 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 - 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. === Background === 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. === Rationale === 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. == Current Status == === Meritocracy === 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. === Community === 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,
Re: [VOTE] Dealing with copyright issue (See ESME-47)
In that case it wouldn't hurt to notifiy gene...@incubator about this issue, so I've ccd them. The skinny is that esme has had a committer violate ASF policy on copyright notices in his commits and he elected to resign instead of comply. ESME is mopping up after him, and this is what they've decided to do. IPMC members please consider hopping on esme-dev@ and expressing your +1 / -1 if you feel the urge. Thanks. - Original Message From: Bertrand Delacretaz bdelacre...@apache.org To: esme-...@incubator.apache.org Sent: Tue, January 12, 2010 8:56:24 AM Subject: Re: [VOTE] Dealing with copyright issue (See ESME-47) On Tue, Jan 12, 2010 at 2:15 PM, Bertrand Delacretaz wrote: On Tue, Jan 12, 2010 at 2:04 PM, Richard Hirsch wrote: 1. The following text will be added to the NOTICE file: This product contains software developed by David Pollak and licensed to the Apache Software Foundation via a Contributor's License Agreement. 2. The wording of the copyright notice in the individuals files is currently: Copyright 2008-2009 WorldWide Conferencing, LLC This copyright notice will be changed to Copyright 2008-2009 WorldWide Conferencing, LLC (under David Pollak's CLA) +1 Forgot to mention that I'm an Incubator PMC member as well - let's get at least 3 such votes (mentors please?) so that this is a decision of the Incubator PMC. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Lucene Connector Framework Kickoff
On Jan 12, 2010, at 5:55 AM, Karl Wright wrote: Hi Grant, For those of us new to working with apache, could you give a quick overview of the best way to communicate among group members? Specifically, what sorts of posts should be sent to gene...@incubator, and what sorts should go to gene...@lucene? We should have the connectors mailing list in a few days or less, at which point we can use those. For now, we should use gene...@incubator.apache.org. I CC'd gene...@lucene.a.o so that people who are in the Lucene community who don't subscribe to incubator would be aware. Also, I am in the process of determining the strategy and the exact list of files for the software grant from MetaCarta, and I'd love to get people's feedback as to what should be included, and how. What list would be appropriate for that? Should we set one up? connectors-...@incubator.a.o will be the place for this. -Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
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, 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. We will need mentors for this proposal WDYT ? Thanks! http://wiki.apache.org/incubator/JppfProposal --- Current Wiki Text below --- = JPPF : a parallel processing framework for Java = === Abstract === 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. === Proposal === JPPF aims at facilitating the parallelization of computation-intensive applications, with a focus on ease of use, performance and reliability. To achieve these goals, the framework comes with a number of outstanding features: - 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. - 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. - 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. - 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. - 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. - 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 - 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. === Background === 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. === Rationale === 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. == Current Status == === Meritocracy === 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
Re: Lucene Connector Framework Kickoff
FYI: I've started putting together a basic site w/ the same skin as most of the other Lucene sites, but w/ Incubator branding. On Jan 11, 2010, at 5:40 PM, Grant Ingersoll wrote: Hi All, (Please keep replies to general@incubator.apache.org) I opened the following JIRA issues for starting LCF: https://issues.apache.org/jira/browse/INFRA-2431 I need two volunteers from the list of committers to be moderators. Please signify your willingness to be a committer by adding your name to the JIRA ticket. Confluence Wiki: https://issues.apache.org/jira/browse/INFRA-2432 JIRA project https://issues.apache.org/jira/browse/INFRA-2433 I added SVN at: https://svn.apache.org/repos/asf/incubator/lcf/ The following people need to submit iCLAs: Brian Pinkerton Karl Wright (kwright at metacarta) Josiah Strandberg (jstrandberg at metacarta) Ken Baker (bakerkj at metacarta) Marc Meadows (mam at metacarta) Once they are on file, I can request accounts. Everyone else should have permission to commit, as they are existing committers. Cheers, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fw: [VOTE] Imperius 1.0.0 rc6
Hi All, We still need two more binding votes for our first release. Would really appreciate it if anyone can take some time to review our release. Thanks Neeraj ~ It is hard enough to remember my opinions, without also remembering my reasons for them. -Friedrich Wilhelm Nietzsche Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ - Forwarded by Neeraj Joshi/Durham/IBM on 01/12/2010 10:28 AM - From: Neeraj Joshi/Durham/i...@ibmus To: general@incubator.apache.org Date: 12/14/2009 04:43 PM Subject: [VOTE] Imperius 1.0.0 rc6 The Imperius community voted on and approved the release of Apache Imperius 1.0.0. We would now like to request the approval of the Incubator PMC for this release. Imperius is a rule-based policy evaluation engine based on the CIM-SPL language from Distributed Management Task Force (dtmf.org). The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 17 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the Imperius mailing list (and further below is the original vote email) Thanks Neeraj ~ Neeraj Joshi (knee-rudge) IBM WebSphere ComputeGrid Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/14/2009 03:45 PM Subject: [VOTE][RESULT] Imperius 1.0.0 rc6 Hello All, Voting on the Imperius 1.0.0rc6 candidate release has concluded Results: 1 binding +1 vote 6 non-binding +1 votes Kevan Miller(*) +1 David Kaminsky +1 David Wood +1 Mark Carlson +1 Erik Bengston +1 Xiping Wang +1 Jorge Lobo +1 Comments received: 1. Comments from Erik Bengston - In the zip/tar file we have a /log.txt file that should be removed. - Inside the jars we have a /META-INF/maven that should be removed too. - imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt - IMO, the lib/javaspl-samples-1.0.0.jar should be moved to samples/lib/javaspl-samples-1.0.0.jar - IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in META-INF folder. It was concluded that it is too early to make all/any Apache Imperius artifacts available in the Maven repository The other issues did not violate Apache policies and would be accommodated in subsequent releases. 2. Comments from Kevan Miller I note that the source distribution contains the following file: imperius-cimsplclientsideprovider/customexpressions.properties which is not in the svn tag. The contents of this file are: SPL_CUSTOM_EXPRESSIONS SPL_CUSTOM_ACTIONS This file is innocuous and gets generated during JUnit testing I will now take this vote to the general mailing list for a final vote. We still need 2 +1 votes from IPMC members. Thanks Neeraj ~ Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/04/2009 10:06 AM Subject: [VOTE] Imperius 1.0.0 rc6 Hi All, The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 08 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Upon a positive majority of binding votes and no binding vetoes, the results of this vote will be brought to the Incubator PMC and voted upon there. Thanks, -Neeraj Change log: 1. Checked in the build.xml from the release
Resigning from Aries mentorship
Hi Aries team and Incubator PMC, After discussing with the other Aries mentors, I have decided to resign from mentoring that project. Coping with four podlings is a bit too much work for me at the moment, and the three remaining mentors look more than qualified to bring the project to graduation! http://incubator.apache.org/projects/aries.html should be updated soon, I have removed my name from that in svn, changes should be live soon. So long, and thanks for all the bundles ;-) -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Olio 0.2
Thank you. The src release also includes the binaries so that a user does not have to do his own build. Shanti ant elder wrote: +1 The Java src archive seems to include some of the binary artifacts (eg webapp.war), the license/notice covers everything so its not an issue just pointing it out in case its not intentional. ...ant On Mon, Jan 11, 2010 at 10:52 PM, Shanti Subramanyam shanti.subraman...@gmail.com wrote: A reminder to please take a look at the Olio release and Vote. Thanks Shanti -- Forwarded message -- From: Shanti Subramanyam shanti.subraman...@sun.com Date: Tue, Jan 5, 2010 at 5:39 PM Subject: [VOTE] Release Olio 0.2 To: general@incubator.apache.org The Olio community has voted to release Olio 0.2. We now request the Incubator PMC for a vote. The proposed release artifacts are located at http://people.apache.org/~shanti/olio_0.2. There are 3 versions (PHP, Rails and Java) in both binary and source formats. Each package is available in both tar and zip format and include asc and md5 checksums. The file names should be self-explanatory. The rat outputs are in *rat-0.2.out. The link to the voting thread can be found here : http://mail-archives.apache.org/mod_mbox/incubator-olio-dev/200912.mbox/browser Please do review the artifacts and we would appreciate it if you could cast your vote by Jan 12. Thanks in advance Shanti - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[Discuss] Apache Shindig as a TLP
Hi folks FYI, the Shindig community has successfully voted for graduation [1]. If no objection on the charter or other, I will start a formal acceptance vote soon. Cheers, Vincent [1] http://shindig-dev.markmail.org/message/c47amdxjtntkjij5 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Olio 0.2
Reviewed signatures and rat output. Nice work. +1 Craig On Jan 4, 2010, at 3:24 PM, Shanti Subramanyam wrote: The Olio community has voted to release Olio 0.2. We now request the Incubator PMC for a vote. The proposed release artifacts are located at http://people.apache.org/~shanti/olio_0.2. There are 3 versions (PHP, Rails and Java) in both binary and source formats. Each package is available in both tar and zip format and include asc and md5 checksums. The file names should be self-explanatory. The rat outputs are in *rat-0.2.out. The link to the voting thread can be found here : http://mail-archives.apache.org/mod_mbox/incubator-olio-dev/200912.mbox/browser Please do review the artifacts and cast your vote by Jan 11. Thanks in advance Shanti Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@sun.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
On Jan 12, 2010, at 10:12 AM, Emmanuel Lcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. Yeah, Hadoop isn't just about Map-Reduce. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
Happy to help a a mentor. Regards, Alan On Jan 12, 2010, at 4:24 AM, Emmanuel Lecharny wrote: Hi guys, 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. We will need mentors for this proposal WDYT ? Thanks! http://wiki.apache.org/incubator/JppfProposal --- Current Wiki Text below --- = JPPF : a parallel processing framework for Java = === Abstract === 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. === Proposal === JPPF aims at facilitating the parallelization of computation-intensive applications, with a focus on ease of use, performance and reliability. To achieve these goals, the framework comes with a number of outstanding features: - 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. - 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. - 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. - 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. - 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. - 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 - 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. === Background === 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. === Rationale === 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. == Current Status == === Meritocracy === 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. === Community === JPPF already has a relatively small,
Re: [Proposal] JPPF : a parallel processing framework for Java
Grant Ingersoll a écrit : On Jan 12, 2010, at 10:12 AM, Emmanuel LŽcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. I posted a mail to priv...@hadoop.apache.org. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
On Jan 12, 2010, at 7:27 AM, Grant Ingersoll wrote: On Jan 12, 2010, at 10:12 AM, Emmanuel LŽcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. Yeah, Hadoop isn't just about Map-Reduce. Just curious, if there's no Hadoop tech in the project then why have it sponsored by Hadoop? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
Alan D. Cabrera a écrit : On Jan 12, 2010, at 7:27 AM, Grant Ingersoll wrote: On Jan 12, 2010, at 10:12 AM, Emmanuel LŽcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. Yeah, Hadoop isn't just about Map-Reduce. Just curious, if there's no Hadoop tech in the project then why have it sponsored by Hadoop? Well, probably because it would be the place where we can find some people interested in participating in the project, increasing the community around it. Or maybe merging with Hadoop if there are many parts that can be shared, or becoming a subproject if it's substancially different in some areas, but have parts in common. At the end of the day, if Hadoop peeps think that the project is orthogonal to what they do, at least they can say so. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Proposal] JPPF : a parallel processing framework for Java
A great idea! I like JPPF's approach whereas I've always had trouble really grasping the map-reduce approach at grid computing (I'm not coming from the search engine side). I'm a bit reluctant to sign up as a mentor just yet because I'm still in a very busy period and probably couldn't dedicate enough time right now. Otherwise, I would have signed up immediately. On 12.01.2010 13:24:49 Emmanuel Lecharny wrote: Hi guys, 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. We will need mentors for this proposal WDYT ? Thanks! http://wiki.apache.org/incubator/JppfProposal --- Current Wiki Text below --- = JPPF : a parallel processing framework for Java = === Abstract === 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. === Proposal === JPPF aims at facilitating the parallelization of computation-intensive applications, with a focus on ease of use, performance and reliability. To achieve these goals, the framework comes with a number of outstanding features: - 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. - 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. - 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. - 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. - 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. - 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 - 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. === Background === 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. === Rationale === 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
Re: [Proposal] JPPF : a parallel processing framework for Java
On Jan 12, 2010, at 11:06 AM, Emmanuel Lcharny wrote: Alan D. Cabrera a écrit : On Jan 12, 2010, at 7:27 AM, Grant Ingersoll wrote: On Jan 12, 2010, at 10:12 AM, Emmanuel LŽcharny wrote: Grant Ingersoll a écrit : Seems like this might fit nicely with Hadoop. Has anyone approached their PMC about sponsoring? No, not yet, but that's clearly an option. At least, a better fit than MINA, IMO. Let's do that. Yeah, Hadoop isn't just about Map-Reduce. Just curious, if there's no Hadoop tech in the project then why have it sponsored by Hadoop? Well, probably because it would be the place where we can find some people interested in participating in the project, increasing the community around it. Or maybe merging with Hadoop if there are many parts that can be shared, or becoming a subproject if it's substancially different in some areas, but have parts in common. At the end of the day, if Hadoop peeps think that the project is orthogonal to what they do, at least they can say so. Makes sense to me. Thanks. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Discuss] Apache Shindig as a TLP
Big +1 On Tue, Jan 12, 2010 at 10:04 AM, Vincent Siveton vsive...@apache.org wrote: Hi folks FYI, the Shindig community has successfully voted for graduation [1]. If no objection on the charter or other, I will start a formal acceptance vote soon. Cheers, Vincent [1] http://shindig-dev.markmail.org/message/c47amdxjtntkjij5 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Olio 0.2
Pulled down and looked through the package. +1 (binding) On Jan 4, 2010, at 6:24 PM, Shanti Subramanyam wrote: The Olio community has voted to release Olio 0.2. We now request the Incubator PMC for a vote. The proposed release artifacts are located at http://people.apache.org/~shanti/olio_0.2. There are 3 versions (PHP, Rails and Java) in both binary and source formats. Each package is available in both tar and zip format and include asc and md5 checksums. The file names should be self-explanatory. The rat outputs are in *rat-0.2.out. The link to the voting thread can be found here : http://mail-archives.apache.org/mod_mbox/incubator-olio-dev/200912.mbox/browser Please do review the artifacts and cast your vote by Jan 11. Thanks in advance Shanti Matt Hogstrom m...@hogstrom.org A Day Without Nuclear Fusion Is a Day Without Sunshine - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fw: [VOTE] Imperius 1.0.0 rc6
+1 ...ant On Tue, Jan 12, 2010 at 3:30 PM, Neeraj Joshi jnee...@us.ibm.com wrote: Hi All, We still need two more binding votes for our first release. Would really appreciate it if anyone can take some time to review our release. Thanks Neeraj ~ It is hard enough to remember my opinions, without also remembering my reasons for them. -Friedrich Wilhelm Nietzsche Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ - Forwarded by Neeraj Joshi/Durham/IBM on 01/12/2010 10:28 AM - From: Neeraj Joshi/Durham/i...@ibmus To: general@incubator.apache.org Date: 12/14/2009 04:43 PM Subject: [VOTE] Imperius 1.0.0 rc6 The Imperius community voted on and approved the release of Apache Imperius 1.0.0. We would now like to request the approval of the Incubator PMC for this release. Imperius is a rule-based policy evaluation engine based on the CIM-SPL language from Distributed Management Task Force (dtmf.org). The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 17 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the Imperius mailing list (and further below is the original vote email) Thanks Neeraj ~ Neeraj Joshi (knee-rudge) IBM WebSphere ComputeGrid Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/14/2009 03:45 PM Subject: [VOTE][RESULT] Imperius 1.0.0 rc6 Hello All, Voting on the Imperius 1.0.0rc6 candidate release has concluded Results: 1 binding +1 vote 6 non-binding +1 votes Kevan Miller(*) +1 David Kaminsky +1 David Wood +1 Mark Carlson +1 Erik Bengston +1 Xiping Wang +1 Jorge Lobo +1 Comments received: 1. Comments from Erik Bengston - In the zip/tar file we have a /log.txt file that should be removed. - Inside the jars we have a /META-INF/maven that should be removed too. - imperius-splcore-1.0.0.jar does not have NOTICE.txt and LICENSE.txt - IMO, the lib/javaspl-samples-1.0.0.jar should be moved to samples/lib/javaspl-samples-1.0.0.jar - IMO, NOTICE.txt and LICENSE.txt files in jar files should lie in META-INF folder. It was concluded that it is too early to make all/any Apache Imperius artifacts available in the Maven repository The other issues did not violate Apache policies and would be accommodated in subsequent releases. 2. Comments from Kevan Miller I note that the source distribution contains the following file: imperius-cimsplclientsideprovider/customexpressions.properties which is not in the svn tag. The contents of this file are: SPL_CUSTOM_EXPRESSIONS SPL_CUSTOM_ACTIONS This file is innocuous and gets generated during JUnit testing I will now take this vote to the general mailing list for a final vote. We still need 2 +1 votes from IPMC members. Thanks Neeraj ~ Neeraj Joshi (knee-rudge) Apache Imperius - http://incubator.apache.org/imperius ~ From: Neeraj Joshi/Durham/i...@ibmus To: imperius-...@incubator.apache.org Date: 12/04/2009 10:06 AM Subject: [VOTE] Imperius 1.0.0 rc6 Hi All, The Imperius 1.0.0 RC6 release candidate has been tagged, packaged, and is ready for a vote. The artifacts, KEYS file, RAT report and release notes can be found at http://people.apache.org/~jneeraj/apache-imperius-1.0.0-rc6/ The tag from which the release artifacts were generated can be found at http://svn.apache.org/repos/asf/incubator/imperius/tags/release1.0.0rc6/ Revision no is 887217 In addition, my PGP public code signing key can be found at the MIT key server (http://pgp.mit.edu/) The KEYS file is checked in at http://svn.apache.org.repos/asf/incubator/imperius/KEYS Please vote to publish this release by Tuesday, Dec 08 18:00 EST., please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Upon a positive majority of binding votes and no binding
[VOTE RESULTS] Release Olio 0.2
This vote has passed with the following PMC members voting for it. A big thanks to them (and of course the Olio community) on getting this release done. Ant Elder +1 Craig Russell +1 Matt Hogstrom +1 I will send out a note once the release is made available for download. Shanti - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
