Re: [PROPOSAL] Deltacloud Project
Luciano Resende wrote: On Thu, May 6, 2010 at 12:41 PM, David Lutterkort wrote: Hi, I would like to propose the Deltacloud API[1] for addition to the Apache incubator. I have added the initial proposal to the Wiki[2]; it is also included below for convenience. There are a few additional people that have expressed interest in becoming initial committers; I am waiting for their express consent to list them as committers, and will add them to the Wiki as I get that. We are looking forward to any and all feedback and/or questions on the proposal. We already have two mentors, but would very much welcome additional volunteers to help steer Deltacloud through the incubation process. David [1] http://deltacloud.org/ [2] http://wiki.apache.org/incubator/DeltacloudProposal Deltacloud, a cross-cloud web service API = Abstract Deltacloud defines a web service API for interacting with cloud service providers and resources in those clouds in a unified manner. In addition, it consists of a number of implementations of this API for the most popular clouds. Proposal * Define a REST-based API for managing and manipulating cloud resources in a manner that isolates the API client as much as possible from the particulars of specific cloud API's * Provide an open API definition for cloud providers for their IaaS clouds and a basis on which PaaS providers can layer their offering * Provide image management and directory capabilities as part of the API * The current implementation allows instance lifecycle management (create, start, stop, destroy, reboot), and querying of related resources like available images, instance sizes, and allowed instance actions for a number of public and private clouds * Currently supported are Amazon EC2, Eucalyptus, Rackspace, RimuHosting, GoGrid, OpenNebula, and RHEV-M * Future enhancements should broaden the scope of the API to include networking, firewalling, authentication, accounting, and image management Background -- An important issue for cloud users is that of avoiding lock-in to a specific cloud. By providing a cross-cloud API for infrastructure-as-a-service (IaaS) clouds, Deltacloud addresses this concern and strives to provide the best possible API for writing cloud-management applications that can target multiple clouds. There are also no efforts currently to define a truly open-source cloud API, one for which there is a proper upstream, independent of any specific cloud provider. Deltacloud API strives to create a community around building an open-source cloud API in a manner that fully allows for tried-and-true open source mechanisms such as user-driven innovation. By providing a web-service API, Deltacloud is language agnostic, and one of its subordinated goals is to provide a practical vocabulary for talking about IaaS cloud resources and operations on them. Rationale - IaaS clouds provide numerous advantages to their users, for example, making provisioning new servers more agile. If users directly use the 'native' cloud API's, they risk locking themselves in to the API of a specific cloud provider. There is therefore a strong need for an API that can be used across a wide range of public and private clouds, and that can serve as the basis for developing cloud management applications; in contrast to several existing language-specific efforts in this direction, Deltacloud is conceived as a web service. This will allow the project to attract a broad community of users of the API and cloud providers interested in offering a truly open-source API, with a proper upstream community. We strongly believe that the best way to drive such an API effort is by developing the API and open-source implementations of the API side-by-side. Initial Goals - Deltacloud is an existing open source project; initially started by Red Hat, it has attracted a number of outside contributors. We look at moving this project to the ASF as the next step to broaden the community, and put the project on solid footing since the ASF governance model is well suited for the Deltacloud project goals. The ASF is a great location for Deltacloud to build a community and will benefit from ASL licensing. Current Status -- Deltacloud API is licensed under the LGPL: * Deltacloud Website (http://deltacloud.org) There are two projects hosted there: the API under consideration here and the Aggregator (not part of this proposal, though also open source) * Deltacloud git repository ( http://git.fedorahosted.org/git/?p=deltacloud/core.git;a=summary) * Deltacloud mailing lists - users (https://fedorahosted.org/mailman/listinfo/deltacloud-users) - developers ( https://fedorahosted.org/mailman/listinfo/deltacloud-devel) Transition to Apache All current contributors have consented to relicensing the Deltacloud API code under the Apache Software Lic
Re: [PROPOSAL] Nuvem Project
Hi, I'd like to contribute too. -- Jean-Sebastien Luciano Resende wrote: Hi, I would like to propose the Nuvem project for addition to the Apache incubator. The initial proposal is available at the the Wiki[1], and it is also included below for convenience. We are looking forward to any and all feedback and/or questions on the proposal. We are also looking for a Champion and mentors, and would very much welcome additional volunteers to help steer Nuvem through the incubation process. [1] http://wiki.apache.org/incubator/Nuvem Apache Nuvem, a cross-cloud application programming interface = Abstract --- Nuvem will define an open application programming interface for common cloud application services, allowing applications to be easily ported across the most popular cloud platforms. Proposal --- * Define an open API that abstracts common cloud platform services to help decouple the application logic from the particulars of a specific proprietary cloud. * Implement the Nuvem API for popular clouds such as Google AppEngine, Amazon EC2 and Microsoft Azure. * Initially focus on User Authentication and Authorization, Distributed Cache, Data Store, Queuing; then extend to other services such as Chat, Logging, and Debugging. Background An important issue for application developers is to avoid lock-in to a specific cloud application platform. By providing a cross-cloud application programming interface that abstracts common cloud platform services, Nuvem addresses this concern and strives to help make applications easily portable across multiple clouds. In mixed cloud deployments, applications need to access platform services across cloud boundaries. Nuvem will make this possible by providing a remote API for these cloud application platform services. Rationale - There are currently no efforts to define a truly open-source API to abstract common cloud platform services. Nuvem strives to create a community around building an open-source cloud application programming interface in a manner that fully allows for tried-and-true open source mechanisms such as user-driven innovation. Initial Goals --- A Nuvem prototype is currently being developed in an Apache Tuscany sandbox, providing initial support for some cloud platform services from Google AppEngine and Amazon EC2. We look at moving this prototype to the Apache Incubator as the next step to broaden the community, expand the API to support more services and cloud platforms. Current Status --- The initial code has been developed under the Apache Software License 2.0 by current Apache committers. Meritocracy --- We recognize the importance of running the project as a meritocracy. We are eager to engage other members of the community and operate to the standard of meritocracy that Apache emphasizes; we believe this is the most effective method of growing our community and enabling widespread adoption. Community --- The initial committer list consists of a couple of independent developers. We expect that the project will greatly increase in contribution base, and this is one aspect the project will monitor in becoming ready for graduation. Alignment - Currently, there are no other Apache projects concerned with building a cross-cloud API for application platform services. We feel that it would be a good complement to the set of Apache projects and could provide them with an API for interacting with cloud application platforms. Nuvem complements Apache libCloud and Deltacloud projects (which both cover provisioning and elasticity in the cloud), providing portability of applications and application services across heterogeneous cloud environments. Orphaned Products -- The Nuvem developers have a long-term interest in use and maintenance of the code and there is also hope that different cloud providers will be interested in providing support for the Nuvem API and will join the project. We feel that it is important to put formal governance in place both for the project and the contributors as the project expands. We feel the ASF is the best location for this. Inexperience with Open Source --- Luciano Resende have been involved with Open Source Software for several years; he has actively contributed to Apache Tuscany, Apache PhotArk and contributed to and/or mentored other Apache podlings. He is also part of the Apache Community Development PMC and Admin/co-Admin for the Google Summer of Code mentoring project. Raymond Fend, is also a long time committer and PMC member of Apache Tuscany and/or other Apache projects. Reliance on Salaried Developers The project is being implemented by developers in their independent personal time and is not founded by a specific corporation.
Re: [VOTE] Nuvem Project
Luciano Resende wrote: On Sat, Jun 19, 2010 at 8:07 AM, Luciano Resende wrote: After initial discussion [1], please vote on the acceptance of Nuvem Project for incubation at the Apache Incubator. The full proposal is available at the end of this message and on the wiki at http://wiki.apache.org/incubator/Nuvem We ask the Incubator PMC to sponsor the project with Luciano Resende as the Champion and Jean-Frederic Clere, Paul Fremantle, Ant Elder and Donald Woods volunteering to be mentors. Please cast your votes: [ ] +1, bring Nuvem into Incubator [ ] +0, I don't care either way [ ] -1, do not bring Nuvem into Incubator, because... The vote is open for the next 72 hours and only votes from the Incubator PMC are binding. +1, bring Nuvem into Incubator +1 (non binding) -- Jean-Sebastien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany
On Mon, Nov 19, 2012 at 9:41 PM, Luciano Resende wrote: > Apache Nuvem will define an open application programming interface > for common cloud application services, allowing applications to be > easily ported across the most popular cloud platforms. It is > currently composed of multiple cloud SCA components (Data, Queue, Chat), > and supports multiple cloud platforms such as AWS, GAE, etc as well > as standalone deployment. Nuvem was accepted for Incubation on June, 2010, > and several of the active committers are already part of the Tuscany PMC. > > Nuvem was accepted for Incubation on June 2010, and is currently a small > community, where the contributions are 100% done by volunteers in their own > free time, which makes the level of activity > low, compared to what is required for graduating it as a TLP. > > Having said that, Nuvem has a great synergy with Apache Tuscany, and after > discussion between the two projects, we are seeking IPMC approval to allow > graduation of Apache Nuvem as a sub-project under Apache Tuscany. > > Nuvem Graduation Vote thread > *http://s.apache.org/nuvem-graduation* > *http://s.apache.org/nuvem-graduation-result* > > Tuscany Graduation Vote thread > *http://s.apache.org/tuscany-accept-nuvem* > *http://s.apache.org/tuscany-accept-nuvem-result* > > Please cast your votes: > > [ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany > > [ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache > Tuscany, because ... > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > +1 (non binding) - Jean-Sebastien
Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)
+1 (non binding, just been playing with Mesos) - Jean-Sebastien On Thu, May 30, 2013 at 11:16 AM, Benjamin Hindman wrote: > +1 > > Thanks Vinod! > > > On Tue, May 28, 2013 at 11:24 AM, Vinod Kone wrote: > > > Please vote on releasing the following candidate as Apache Mesos > > (incubating) > > version 0.11.0. This will be the third incubator release for Mesos in > > Apache > > > > . > > > > The candidate for Mesos 0.11.0-incubating release is available at: > > > > > > > http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz > > > > > > The tag to be voted on: > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbcaa0d348a88188c17a8b06b57306832a7a5885 > > > > > > The MD5 checksum of the tarball can be found at: > > > > > > > http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.md5 > > > > > > The signature of the tarball can be found at: > > > > > > > http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.11.0-incubating.tar.gz.asc > > > > PGP key used to sign the release: > > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2B1D89DA5C6E508C > > > > Please vote on releasing this package as Apache Mesos 0.11.0-incubating! > > > > The vote is open until Friday, May 31st at 18:30 UTC and passes if a > > > > majority of at least 3 +1 IPMC votes are cast. > > > > [ ] +1 Release this package as Apache Mesos 0.11.0-incubating > > [ ] -1 Do not release this package because ... > > > > To learn more about Apache Mesos, please see > > http://incubator.apache.org/mesos. > > >
Re: [PROPOSAL] Apache Aries incubator for Enterprise OSGi
Niklas Gustavsson wrote: On Wed, Sep 9, 2009 at 8:14 PM, Kevan Miller wrote: Cool! So, IMO would be best to post the names here on general@ and let Jeremy update the Wiki. Since we're at it, I'd like to sign up as a committer as well (apache username ngn). Will be quite time constrained in the next two-three months but the areas deeply interests me so I'll chime in where possible. /niklas Hi, I'd like to help and sign up as a committer too (apache user name jsdelfino). I have experience with Apache, SCA and OSGi as I did quite a bit of OSGi work in Apache Tuscany. Jeremy, do you want me to add my name? or are you making all the updates to the Wiki page? -- Jean-Sebastien - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Tuscany as a top level project
Mike Edwards wrote: Folks, ant elder wrote: Having both the last two sentences start "This software will..." doesn't sound perfect to me so if we are able to move the "for distribution at no charge..." bit up to the top that seems better, which gives: ...establish a Project Management Committee charged with the creation and maintenance of open-source software for distribution at no charge to the public, that simplifies the development, deployment and management of distributed applications composed of independently acting, loosely coupled, linguistically heterogeneous components connected using any of a wide range of communication technologies. This software will implement relevant open standards including, but not limited to, standards defined by the OASIS OpenCSA group. That first sentence is starting to get quite long but unless anyone can come up with some better wording I could live with that. ...ant I'm sorry, but I don't find this wording at all convincing. I suspect that most people would be mystified by the section: "distributed applications composed of independently acting, loosely coupled, linguistically heterogeneous components connected using any of a wide range of communication technologies" So, let me try another version, which turns out to be longer, but I hope that it is easier to comprehend. I also explicitly mention SCA and SDO since these are two core standards that are implemented by Tuscany. "...establish a Project Management Committee charged with the creation and maintenance of open-source software for distribution at no charge to the public, that simplifies the development, deployment and management of distributed applications built as compositions of service components, where the components may be written using any of a wide range of programming languages and where the components can be connected using any of a wide range of communication technologies. This software will implement relevant open standards including, but not limited to, the SCA and SDO standards defined by the OASIS OpenCSA member section." Yours, Mike. This version looks better to me. I was a little mystified by the "linguistically heterogeneous" part as well :) I like the "built as compositions of service components" which describes well what we do in Tuscany and the fact that you explicitly mention the SCA and SDO standards. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Please review the Tuscany M1 release candidate
Hi! I have initiated a vote on tuscany-dev@ws.apache.org to publish a release of Tuscany. The vote email thread is available there: http://article.gmane.org/gmane.comp.apache.webservices.tuscany.devel/3259 We have read the Apache release guidelines and the incubator release policy, but this is the first time that we are doing an incubation release so I would appreciate if you could take a look at the distributions at http://people.apache.org/~jsdelfino/test-incubating-M1/, give us feedback and let us know if we need to fix anything. If the vote on tuscany-dev is successful, we will send a summary of that vote to the Incubator's general list to formally request the Incubator PMC to approve the release. Thank you. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Please review Tuscany M1 release candidate
Hi! I have initiated a vote on tuscany-dev@ws.apache.org to publish a release of Tuscany. The vote email thread is available there: http://article.gmane.org/gmane.comp.apache.webservices.tuscany.devel/3259 We have read the Apache release guidelines and the incubator release policy, but this is the first time that we are doing an incubation release so I would appreciate if you could take a look at the distributions at http://people.apache.org/~jsdelfino/test-incubating-M1/, give us feedback and let us know if we need to fix anything. If the vote on tuscany-dev is successful, we will send a summary of that vote to the Incubator's general list to formally request the Incubator PMC to approve the release. Thank you. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please review Tuscany M1 release candidate
robert burrell donkin wrote: On 5/19/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: Hi! I have initiated a vote on tuscany-dev@ws.apache.org to publish a release of Tuscany. The vote email thread is available there: http://article.gmane.org/gmane.comp.apache.webservices.tuscany.devel/3259 We have read the Apache release guidelines and the incubator release policy, but this is the first time that we are doing an incubation release so I would appreciate if you could take a look at the distributions at http://people.apache.org/~jsdelfino/test-incubating-M1/<http://people.apache.org/%7Ejsdelfino/test-incubating-M1/>, give us feedback and let us know if we need to fix anything. (non-binding) a few little nits (nothing serious, more FYI for next time): 1 there are some encoding issues down at the bottom of the LICENSE.txt. they don't effect the meaning. 2 STATUS seems like it might be a little outdated re:PENDING ISSUES. might be good to list M1 in the release status 3 MANIFEST files lack a Implementation-Vendor-Id and so are not fully complient. it's conventional to use 'org.apache'. one slightly more serious point: 4 the tuscany jar's don't contain NOTICE files. all distributed artifacts *must* contain these LICENSE and NOTICE files. if these jars don't contain these files then they cannot be released via the apache jar repository (which is mirrored to the maven repository on ibiblio). read http://www.apache.org/dev/release.html. it's traditional to include LICENSE and NOTICE files within META-INF (but that's not mandatory). http://jakarta.apache.org/commons/releases/prepare.html contains maven 1 snippets. but overall not bad :-) - robert Robert, Thanks for your feedback. I fixed the issues you reported (see JIRA http://issues.apache.org/jira/browse/TUSCANY-414) and uploaded the updated files to http://people.apache.org/~jsdelfino/test-incubating-M1/. I also started a new vote on tuscany-dev@ws.apache.org to publish the updated distribution. The vote email thread is available there: http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200605.mbox/[EMAIL PROTECTED] -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
