Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
thinking about this a little I think a TLP that grouped the Cloud technologies together make a lot of sense. With LibCloud, DeltaCloud, Whirr, etc. as a start there will clearly be some additional projects coming. On May 6, 2010, at 3:54 PM, Paul Querna wrote: I think it does raise the question, should libcloud graduate to a new TLP, with a more generic task or providing cross cloud APIs and libraries. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
On 5/12/10 10:29 AM, Matt Hogstrom wrote: thinking about this a little I think a TLP that grouped the Cloud technologies together make a lot of sense. With LibCloud, DeltaCloud, Whirr, etc. as a start there will clearly be some additional projects coming. +1. I think it'll be easier too for customers to have one entry point, to help figuring out which of our cloud project(s) fit their needs and solves their problems. -- leif - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
+1. Some existing Apache projects such as Tuscany also have interests in this space. Thanks, Raymond Raymond Feng rf...@apache.org Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com On May 12, 2010, at 9:29 AM, Matt Hogstrom wrote: thinking about this a little I think a TLP that grouped the Cloud technologies together make a lot of sense. With LibCloud, DeltaCloud, Whirr, etc. as a start there will clearly be some additional projects coming. On May 6, 2010, at 3:54 PM, Paul Querna wrote: I think it does raise the question, should libcloud graduate to a new TLP, with a more generic task or providing cross cloud APIs and libraries. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
On Wed, May 12, 2010 at 9:58 AM, Raymond Feng enjoyj...@gmail.com wrote: +1. Some existing Apache projects such as Tuscany also have interests in this space. +1 For Paul's suggestion and Raymond's remakrs. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
On Wed, May 12, 2010 at 10:31 PM, Luciano Resende luckbr1...@gmail.comwrote: On Wed, May 12, 2010 at 9:58 AM, Raymond Feng enjoyj...@gmail.com wrote: +1. Some existing Apache projects such as Tuscany also have interests in this space. +1 For Paul's suggestion and Raymond's remakrs. +1. Indeed it makes a lot of sense in the user community PoV. Thanks, Senaka. -- Luciano Resende http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
For me, not so much. A TLP owns a code base and is responsible for it. While I appreciate the sentiment, I don't think it's wise to require that different communities with nothing else in common except cloud in their name have to be managed by the same PMC. How is cloud different from xml or java or web or database? We have many communities in Apache that share buzzwords yet have different approaches. Craig On May 12, 2010, at 9:29 AM, Matt Hogstrom wrote: thinking about this a little I think a TLP that grouped the Cloud technologies together make a lot of sense. With LibCloud, DeltaCloud, Whirr, etc. as a start there will clearly be some additional projects coming. On May 6, 2010, at 3:54 PM, Paul Querna wrote: I think it does raise the question, should libcloud graduate to a new TLP, with a more generic task or providing cross cloud APIs and libraries. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.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: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
On Wed, May 12, 2010 at 12:16 PM, Craig L Russell craig.russ...@oracle.com wrote: For me, not so much. A TLP owns a code base and is responsible for it. While I appreciate the sentiment, I don't think it's wise to require that different communities with nothing else in common except cloud in their name have to be managed by the same PMC. How is cloud different from xml or java or web or database? We have many communities in Apache that share buzzwords yet have different approaches. Right, I think the 3 projects we are talking about can be broken down into simple lines: - deltacloud: portable cloud library (with a http interface) - libcloud: portable cloud library (with a python interface) - whirr: scripts tools built on top of the previous two (or other tools) But my point is not so much about the buzz-wordyness of 'cloud', it was more about overlapping: - committers - community concerns: - cloud portability - access to APIs and documentation To me, the set of the community interested in these things will be similar, and one TLP to wrap them up in that sense makes sense to me, we have dozens of examples of TLPs with multipe products, and not all of them are *bad* TLPs. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
Fair point Craig ... my head was more around grouping like you had with the various DB projects. Each one was independent but kind of under the DB umbrella, right ? I didn't mean to imply one PMC to rule them all ... bad idea. On May 12, 2010, at 3:16 PM, Craig L Russell wrote: For me, not so much. A TLP owns a code base and is responsible for it. While I appreciate the sentiment, I don't think it's wise to require that different communities with nothing else in common except cloud in their name have to be managed by the same PMC. How is cloud different from xml or java or web or database? We have many communities in Apache that share buzzwords yet have different approaches. Craig On May 12, 2010, at 9:29 AM, Matt Hogstrom wrote: thinking about this a little I think a TLP that grouped the Cloud technologies together make a lot of sense. With LibCloud, DeltaCloud, Whirr, etc. as a start there will clearly be some additional projects coming. On May 6, 2010, at 3:54 PM, Paul Querna wrote: I think it does raise the question, should libcloud graduate to a new TLP, with a more generic task or providing cross cloud APIs and libraries. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Luciano Resende wrote: On Thu, May 6, 2010 at 12:41 PM, David Lutterkort lut...@redhat.com 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
Re: [PROPOSAL] Deltacloud Project
On Tue, 2010-05-11 at 10:42 +0530, Selvaratnam Uthaiyashankar wrote: I would like to contribute. Please add me as an initial committer. (shankar AT apache DOT org) . Welcome. Added you to the proposal. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Tue, 2010-05-11 at 10:34 +0530, Chintana Wilamuna wrote: On Fri, May 7, 2010 at 1:11 AM, David Lutterkort lut...@redhat.com wrote: [snip] As Sanjiva mentioned we've been involved with a similar kind of effort as well. May be we can consolidate our efforts. I would also like to contribute to this project. Welcome. Just added you to the proposal. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Sat, 2010-05-08 at 11:16 +0530, Sanjiva Weerawarana wrote: David, +1 for this project. We've been doing something similar in WSO2 (called Ozone) and are happy to jump to this. Have you looked at OpenNebula (http://opennebula.org/) Yes, they actually wrote a Deltacloud driver, so you can use Deltacloud to talk to your ON instance. But having more people with an interest in ON help out will definitely be good. - we were heading towards using that (and adding some Web service APIs etc.). Looks like they decided to form a business a few days ago: http://opennebula.ulitzer.com/node/1382814. Interesting, I hadn't seen that. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project - next steps
On Thu, 2010-05-06 at 12:41 -0700, David Lutterkort wrote: 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. Thanks to everybody on this thread for the very positive reception of Deltacloud. For next steps, I'd like to leave the discussion open until Wednesday 5/12, 5pm PDT and start the formal vote at that time on a separate thread. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Fri, May 7, 2010 at 1:11 AM, David Lutterkort lut...@redhat.com wrote: [snip] As Sanjiva mentioned we've been involved with a similar kind of effort as well. May be we can consolidate our efforts. I would also like to contribute to this project. Bye, -Chintana -- blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
I would like to contribute. Please add me as an initial committer. (shankar AT apache DOT org) . regards, Shankar On Fri, May 7, 2010 at 1:11 AM, David Lutterkort lut...@redhat.com 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
Re: [PROPOSAL] Deltacloud Project
Hi Gurkan, As a Member, just ask to be an IPMC member and you will become one. Craig On May 7, 2010, at 1:04 PM, Gurkan Erdogdu wrote: I would like to mentor but I am not a IPMC member. But if possible I would like to contribute and you could add me as an initial committer. Thanks; --Gurkan From: Carl Trieloff cctriel...@redhat.com To: general@incubator.apache.org Sent: Fri, May 7, 2010 4:18:02 PM Subject: Re: [PROPOSAL] Deltacloud Project On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.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] Deltacloud Project
Hello Craig; Thanks for the solution. I have just sent an subscription email to private-subscr...@i.a.o waiting for confirmation :) -- Gurkan From: Craig L Russell craig.russ...@oracle.com To: general@incubator.apache.org Sent: Sat, May 8, 2010 10:46:10 AM Subject: Re: [PROPOSAL] Deltacloud Project Hi Gurkan, As a Member, just ask to be an IPMC member and you will become one. Craig On May 7, 2010, at 1:04 PM, Gurkan Erdogdu wrote: I would like to mentor but I am not a IPMC member. But if possible I would like to contribute and you could add me as an initial committer. Thanks; --Gurkan From: Carl Trieloff cctriel...@redhat.com To: general@incubator.apache.org Sent: Fri, May 7, 2010 4:18:02 PM Subject: Re: [PROPOSAL] Deltacloud Project On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.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] Deltacloud Project
Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan From: David Lutterkort lut...@redhat.com To: general@incubator.apache.org Sent: Thu, May 6, 2010 10:41:19 PM Subject: [PROPOSAL] Deltacloud Project 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
Re: [PROPOSAL] Deltacloud Project
On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Carl, if you need additional mentors, count me in. thanks, dims On Fri, May 7, 2010 at 9:18 AM, Carl Trieloff cctriel...@redhat.com wrote: On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Davanum Srinivas :: http://davanum.wordpress.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On 05/07/2010 10:21 AM, Davanum Srinivas wrote: Carl, if you need additional mentors, count me in. thanks, dims Dims, That would be great. Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Project look very interesting to me, so I would like to contribute too. Deepal Carl, if you need additional mentors, count me in. thanks, dims On Fri, May 7, 2010 at 9:18 AM, Carl Trieloff cctriel...@redhat.com wrote: On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- If we knew what it was we were doing, it would not be called research, would it? - Albert Einstein http://blogs.deepal.org http://deepal.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Fri, 2010-05-07 at 10:21 -0400, Davanum Srinivas wrote: if you need additional mentors, count me in. Great. I added you to the proposal. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Fri, 2010-05-07 at 11:51 -0400, Deepal jayasinghe wrote: Project look very interesting to me, so I would like to contribute too. Just added you to the proposal. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Thu, 2010-05-06 at 22:15 -0700, Matt Hogstrom wrote: +1 You can add me as a committer as well ... Done. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
+1. I too would like to contribute to this project. Thanks, Senaka. On Fri, May 7, 2010 at 1:11 AM, David Lutterkort lut...@redhat.com 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)
Re: [PROPOSAL] Deltacloud Project
On Fri, 2010-05-07 at 22:14 +0530, Senaka Fernando wrote: +1. I too would like to contribute to this project. Thanks. Just added you to initial committers on the proposal. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
I would like to mentor but I am not a IPMC member. But if possible I would like to contribute and you could add me as an initial committer. Thanks; --Gurkan From: Carl Trieloff cctriel...@redhat.com To: general@incubator.apache.org Sent: Fri, May 7, 2010 4:18:02 PM Subject: Re: [PROPOSAL] Deltacloud Project On 05/07/2010 02:33 AM, Gurkan Erdogdu wrote: Hi; +1; I am happy to help during incubation process; Thanks; --Gurkan Gurkan, Is this an offer to help mentor the project, or just help out as needed. Reason for asking is if you would like to be represented onto the proposal or just voicing support which is greatly appreciated. regards, Carl. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Fri, 2010-05-07 at 13:04 -0700, Gurkan Erdogdu wrote: I would like to mentor but I am not a IPMC member. But if possible I would like to contribute and you could add me as an initial committer. Glad to have you. I just added you to the list of initial committers on the proposal page. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
David, +1 for this project. We've been doing something similar in WSO2 (called Ozone) and are happy to jump to this. Have you looked at OpenNebula (http://opennebula.org/) - we were heading towards using that (and adding some Web service APIs etc.). Looks like they decided to form a business a few days ago: http://opennebula.ulitzer.com/node/1382814. If OpenNebula an Deltacloud have similar missions maybe we can find a way to get them here too - it'll be great for the world to have one superb IaaS cloud abstraction API, under Apache license of course. I plan to join the list and lurk .. looks like you have enough mentors already. Sanjiva. On Fri, May 7, 2010 at 1:11 AM, David Lutterkort lut...@redhat.com 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
Re: [PROPOSAL] Deltacloud Project
Hi Guys, Question: what¹s the relationship of this proposal to Whirr, which we¹re currently voting [1] on? Thanks! Cheers, Chris [1] http://www.mail-archive.com/general@incubator.apache.org/msg24518.html On 5/6/10 12:41 PM, David Lutterkort lut...@redhat.com 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 [...] ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
On Thu, May 6, 2010 at 12:41 PM, David Lutterkort lut...@redhat.com wrote: Hi, I would like to propose the Deltacloud API[1] for addition to the Apache incubator. Awesome! 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. I think Deltacloud can stand on its own, and for purposes of the voting into the Incubator, should ignore the existing libcloud project. Libcloud however is getting closer to being able to Graduate. (hopefully in may/june?). I think it does raise the question, should libcloud graduate to a new TLP, with a more generic task or providing cross cloud APIs and libraries. Libcloud is already moving a little beyond just APIs, with the current discussions around a portable image format, and beyond just python with another discussion of a possible Java port of the library. Deltacloud does have some overlap in comitter-ship too, and I think fundamentally both communities share very similar interests, even if the implementations are different languages. Thoughts? Thanks, Paul - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Thu, May 6, 2010 at 12:53 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Guys, Question: what¹s the relationship of this proposal to Whirr, which we¹re currently voting [1] on? Whirr would be built on top of Deltacloud or Libcloud -- Whirr is more about 'end user' scripts and tools to manage products, while deltacloud and libcloud are both more low level tools and libraries to build on top of. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Hi Paul, Thanks. OK, so then going to your other email, consolidation at some capacity may make sense... Cheers, Chris On 5/6/10 12:57 PM, Paul Querna p...@querna.org wrote: On Thu, May 6, 2010 at 12:53 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Guys, Question: what¹s the relationship of this proposal to Whirr, which we¹re currently voting [1] on? Whirr would be built on top of Deltacloud or Libcloud -- Whirr is more about 'end user' scripts and tools to manage products, while deltacloud and libcloud are both more low level tools and libraries to build on top of. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cross Cloud TLP, was Re: [PROPOSAL] Deltacloud Project
On Thu, 2010-05-06 at 12:54 -0700, Paul Querna wrote: Deltacloud does have some overlap in comitter-ship too, and I think fundamentally both communities share very similar interests, even if the implementations are different languages. On a technical level, the overlap is mostly on the modeling level; I don't think there's much opportunity for sharing code. We definitely need some coordination between the various cloud API projects (be they part of ASF or outside of it like jclouds or fog) To me, this sounds more like finding a way to discuss approaches in a common place (e.g., a mailing list like the cloudhackers list) and making sure hte various communities talk to each other (which they already do) David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
Need additional mentors ? I'll volunteer. This is in scope for what I do at work would like to dabble as well. On May 6, 2010, at 1:01 PM, Mattmann, Chris A (388J) wrote: Hi Paul, Thanks. OK, so then going to your other email, consolidation at some capacity may make sense... Cheers, Chris On 5/6/10 12:57 PM, Paul Querna p...@querna.org wrote: On Thu, May 6, 2010 at 12:53 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Guys, Question: what¹s the relationship of this proposal to Whirr, which we¹re currently voting [1] on? Whirr would be built on top of Deltacloud or Libcloud -- Whirr is more about 'end user' scripts and tools to manage products, while deltacloud and libcloud are both more low level tools and libraries to build on top of. - 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
Re: [PROPOSAL] Deltacloud Project
Oh yeah, I work for IBM. On May 6, 2010, at 2:31 PM, Matt Hogstrom wrote: Need additional mentors ? I'll volunteer. This is in scope for what I do at work would like to dabble as well. On May 6, 2010, at 1:01 PM, Mattmann, Chris A (388J) wrote: Hi Paul, Thanks. OK, so then going to your other email, consolidation at some capacity may make sense... Cheers, Chris On 5/6/10 12:57 PM, Paul Querna p...@querna.org wrote: On Thu, May 6, 2010 at 12:53 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Guys, Question: what¹s the relationship of this proposal to Whirr, which we¹re currently voting [1] on? Whirr would be built on top of Deltacloud or Libcloud -- Whirr is more about 'end user' scripts and tools to manage products, while deltacloud and libcloud are both more low level tools and libraries to build on top of. - 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
Re: [PROPOSAL] Deltacloud Project
On Thu, May 6, 2010 at 12:41 PM, David Lutterkort lut...@redhat.com 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
Re: [PROPOSAL] Deltacloud Project
+1 Craig On 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
Re: [PROPOSAL] Deltacloud Project
+1 from me -- dims Sent from my iPhone On May 6, 2010, at 6:08 PM, Craig L Russell craig.russ...@oracle.com wrote: +1 Craig On 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
Re: [PROPOSAL] Deltacloud Project
On Thu, 2010-05-06 at 14:37 -0700, Luciano Resende wrote: I've been playing with something somewhat related in Tuscany to abstract different Cloud infrastructure services, so this would be of my interest. I'd like to be involved (maybe as initial committer) ... Very happy to have you involved. I added you to the list of initial committers in the proposal[1]. David [1] http://wiki.apache.org/incubator/DeltacloudProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
On Thu, 2010-05-06 at 14:31 -0700, Matt Hogstrom wrote: Need additional mentors ? I'll volunteer. This is in scope for what I do at work would like to dabble as well. Excellent. I've added you to the list of mentors on the proposal[1] David [1] http://wiki.apache.org/incubator/DeltacloudProposal - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Deltacloud Project
+1 You can add me as a committer as well ... On May 6, 2010, at 2:32 PM, Matt Hogstrom wrote: Oh yeah, I work for IBM. On May 6, 2010, at 2:31 PM, Matt Hogstrom wrote: Need additional mentors ? I'll volunteer. This is in scope for what I do at work would like to dabble as well. On May 6, 2010, at 1:01 PM, Mattmann, Chris A (388J) wrote: Hi Paul, Thanks. OK, so then going to your other email, consolidation at some capacity may make sense... Cheers, Chris On 5/6/10 12:57 PM, Paul Querna p...@querna.org wrote: On Thu, May 6, 2010 at 12:53 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Guys, Question: what¹s the relationship of this proposal to Whirr, which we¹re currently voting [1] on? Whirr would be built on top of Deltacloud or Libcloud -- Whirr is more about 'end user' scripts and tools to manage products, while deltacloud and libcloud are both more low level tools and libraries to build on top of. - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
