Re: svn commit: r1213805 - /incubator/public/trunk/site-publish/.htaccess
On Tue, 2011-12-13 at 19:19 +, sebb wrote: On 13 December 2011 17:47, lut...@apache.org wrote: Author: lutter Date: Tue Dec 13 17:47:07 2011 New Revision: 1213805 URL: http://svn.apache.org/viewvc?rev=1213805view=rev Log: Redirect Deltacloud to its new post-graduation site I assume you are going remove the /www/incubator.apache.org/deltacloud site as it is now inacessible? Yes, I just wanted to make sure the redirect was properly in place before removing the old content. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1213805 - /incubator/public/trunk/site-publish/.htaccess
On Tue, 2011-12-13 at 15:23 -0800, David Lutterkort wrote: On Tue, 2011-12-13 at 19:19 +, sebb wrote: On 13 December 2011 17:47, lut...@apache.org wrote: Author: lutter Date: Tue Dec 13 17:47:07 2011 New Revision: 1213805 URL: http://svn.apache.org/viewvc?rev=1213805view=rev Log: Redirect Deltacloud to its new post-graduation site I assume you are going remove the /www/incubator.apache.org/deltacloud site as it is now inacessible? Yes, I just wanted to make sure the redirect was properly in place before removing the old content. Actually, http://incubator.apache.org/deltacloud/ still gives me a 200; what else do I need to do to have the redirect pushed out to the servers ? David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1213805 - /incubator/public/trunk/site-publish/.htaccess
On Wed, 2011-12-14 at 00:26 +, sebb wrote: On 13 December 2011 23:29, David Lutterkort lut...@redhat.com wrote: On Tue, 2011-12-13 at 15:23 -0800, David Lutterkort wrote: On Tue, 2011-12-13 at 19:19 +, sebb wrote: On 13 December 2011 17:47, lut...@apache.org wrote: Author: lutter Date: Tue Dec 13 17:47:07 2011 New Revision: 1213805 URL: http://svn.apache.org/viewvc?rev=1213805view=rev Log: Redirect Deltacloud to its new post-graduation site I assume you are going remove the /www/incubator.apache.org/deltacloud site as it is now inacessible? Yes, I just wanted to make sure the redirect was properly in place before removing the old content. Actually, http://incubator.apache.org/deltacloud/ still gives me a 200; what else do I need to do to have the redirect pushed out to the servers ? Did you update the website on minotaur by running svn update? Now I did ;) The mirror scripts should pick it up in a little bit. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Git to SVN
Hi Leo, what you are looking for is 'grafting' the master branch of your current git repo into subversion via git-svn. This blog post[1] helped me a lot when I was doing the same for Deltacloud. David [1] http://journal.sandesh247.com/2009/06/importing-git-history-into-new-svn.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Graduation of Deltacloud to TLP
Hi all, the vote[1] on graduating Deltacloud produced a result of 5 +1 votes, and no 0 or -1 votes. The +1 votes were Alan Cabrera Christian Grobmeier Chris Mattmann Davanum Srinivas Carl Trieloff With that, I will ask the Board to put graduation of Deltacloud on its agenda for the next board meeting. David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201110.mbox/%3c1318862553.30002.43.ca...@melon.watzmann.net%3E - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
On Thu, 2011-10-13 at 08:30 +0200, Christian Grobmeier wrote: Slowly I begin to understand this is a non-apache package, correct? otherwise I would expect the link to an ASF git mirror instead Yeah, I think we need to tweak the stylesheet. The 'Additional Tools' header doesn't stand out enough, and doesn't make it clear that this is additional stuff, only related to, and not part of, the Apache project. OK thats fine for me then. Btw, the homepage says Deltacloud 0.3.0 is now available, including support for IBM SBC and Eucalyptus in News :-) Wow, what a nitpicker am I. Hope you can forgive me Somebody has to when we don't pick the nits; after all, who wants lice ? We are changing the 'News' box to be feed from @deltacloud on twitter, so this should become much more up-to-date and relevant. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduate Deltacloud to TLP
Hi all, as described in the discussion thread[1], the Deltacloud community feels that we are ready to graduate to a top-level Apache project. To that end, I'd like to have a vote by the IPMC so that we can put the resolution given below onto the agenda of the next Apache Board meeting. Please vote by Thursday, 2011-10-20, 8am PDT. Since starting incubation in May, 2010, we've made several releases, added contributors, and have the support of our mentors to graduate. Thanks for your consideration, and voting, David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201110.mbox/%3c1318464232.2751.7.ca...@melon.watzmann.net%3e Resolution: === WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software implementing web service API's for interacting with cloud providers, and corresponding client libraries, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Deltacloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Deltacloud Project be and hereby is responsible for the creation and maintenance of software related to web service API's for interacting with cloud providers, and corresponding client libraries; and be it further RESOLVED, that the office of Vice President, Deltacloud be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Deltacloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Deltacloud Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Deltacloud Project: * Marios Andreou (mar...@apache.org) * Michal Fojtik (mfoj...@apache.org) * Jim Jagielski (j...@apache.org) * Chris Lalancette (clala...@apache.org) * David Lutterkort (lut...@apache.org) * Sang-Min Park (sp...@apache.org) * Carl Trieloff (cctriel...@apache.org) * Eric Woods (wood...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Lutterkort be appointed to the office of Vice President, Deltacloud, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Deltacloud Project; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Deltacloud podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Deltacloud podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Graduation of Deltacloud to TLP
One small correction to the draft resolution: On Wed, 2011-10-12 at 17:03 -0700, David Lutterkort wrote: RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Deltacloud Project: * Marios Andreou (mar...@apache.org) * Michal Fojtik (mfoj...@apache.org) * Jim Jagielski (j...@apache.org) * Chris Lalancette (clala...@apache.org) * David Lutterkort (lut...@apache.org) * Sang-Min Park (sp...@apache.org) * Eric Woods (wood...@apache.org) Add to this list our sponsor, Carl Trieloff (cctriel...@apache.org) David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
On Wed, 2011-10-12 at 11:13 +0200, Christian Grobmeier wrote: David, congratulations to the new release. Just a comment I cannot see the new release on the website: http://incubator.apache.org/deltacloud/ Should't it be updated together with the release? Yes, this was a case of the mail servers being way faster than the mirroring scripts. It's there now. Then I think it is not very good to send the /dist folder link around, because to my knowledge it is bypassing the mirror system. Instead we usually use some kind of download page generator. Sorry, that was an oversight on my part. I'll replace the links with http://www.apache.org/dyn/closer.cgi/incubator/deltacloud/ in the future. At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. The very first link (Official releases can be downloaded from the Apache website) on that page goes to http://www.apache.org/dist/incubator/deltacloud/ Do you see a different version of the page ? David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
On Wed, 2011-10-12 at 18:42 +0200, Christian Grobmeier wrote: David, At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. The very first link (Official releases can be downloaded from the Apache website) on that page goes to http://www.apache.org/dist/incubator/deltacloud/ Do you see a different version of the page ? Ah, very small, now I see it :-) But: You can get the source code: git clone git://git.fedorahosted.org/deltacloud/libdeltacloud.git Slowly I begin to understand this is a non-apache package, correct? otherwise I would expect the link to an ASF git mirror instead Yeah, I think we need to tweak the stylesheet. The 'Additional Tools' header doesn't stand out enough, and doesn't make it clear that this is additional stuff, only related to, and not part of, the Apache project. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Graduation of Deltacloud to TLP
Hi all, the Deltacloud community and mentors feel that we are ready to graduate to a toplevel Apache project. A while ago, we held a vote on the deltacloud-dev mailing list[1] about graduation, with 8 +1 votes (2 from mentors) and no 0 or -1 votes[2]. Since we started incubation, we've made 4 releases and added 3 new contributors[3] We would like to move the process of graduation forward; to that end, I would like feedback on the draft resolution (included below) and, assuming the discussion doesn't turn up any absolute blockers, call for a vote for the IPMC on this list on 2011-10-17. cheers, David [1] http://mail-archives.apache.org/mod_mbox/incubator-deltacloud-dev/201108.mbox/%3c1313190921.5165.4.ca...@avon.watzmann.net%3E [2] http://mail-archives.apache.org/mod_mbox/incubator-deltacloud-dev/201109.mbox/%3c1316040219.17880.34.ca...@avon.watzmann.net%3E [3] http://incubator.apache.org/projects/deltacloud.html Draft resolution: WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software implementing web service API's for interacting with cloud providers, and corresponding client libraries, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Deltacloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Deltacloud Project be and hereby is responsible for the creation and maintenance of software related to web service API's for interacting with cloud providers, and corresponding client libraries; and be it further RESOLVED, that the office of Vice President, Deltacloud be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Deltacloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Deltacloud Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Deltacloud Project: * Marios Andreou (mar...@apache.org) * Michal Fojtik (mfoj...@apache.org) * Jim Jagielski (j...@apache.org) * Chris Lalancette (clala...@apache.org) * David Lutterkort (lut...@apache.org) * Sang-Min Park (sp...@apache.org) * Eric Woods (wood...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Lutterkort be appointed to the office of Vice President, Deltacloud, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Deltacloud Project; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Deltacloud podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Deltacloud podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] [RESULT] Release deltacloud 0.4.1 rc1
The vote resulted in 6 +1, no 0's or -1's; three +1 votes were cast by mentors (Carl Trieloff, Jim Jagielski, and Davanum Srinivas) With that, the release of Deltacloud 0.4.1 RC1 is approved and I'll move the artifacts to the proper place to make them the GA. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
I am pleased to announce the availability of Apache Deltacloud 0.4.1. Apache Deltacloud is a RESTful cloud abstraction API. The release consists both of the API server and a Ruby client. The release can be found at http://www.apache.org/dist/incubator/deltacloud/0.4.1/ Gems and RPM's for Fedora will become available shortly. Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: * change how dependencies are managed: canonical deps are now in the gemspecs Server: * clarify how user_data injection should work; make sure all drivers accept base64 encoded data and make the decoded version available to instance * fix URL generation so that server works when run behind a reverse proxy * init script: honor defaults from sysconfig file * init script: fix 'status', properly background deltacloudd * deltacloudd: support verbose option * Drivers: + Condor - use UUIDTools instead of UUID to simplify deps + Google - new driver for Google storage API + RHEV-M - treat status as case-insensitive - inject data through a virtual floppy rather than modifying the instance storage directly + vSphere - report minimum of max memory across all hosts in a data center, so that instances can be placed on any host - user_data is placed in file 'deltacloud-user-data.txt' Client: * fix parsing of enums in HWP properties * fix handling of float value for number of vCPU in HWP David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.4.1, rc1
Hi all, I just uploaded the first release candidate for Deltacloud 0.4.1. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.1/rc1/ Please vote on the release candidate by Saturday, 2011-10-07 15:00 PDT KEYS: http://www.apache.org/dist/incubator/deltacloud/KEYS svn tag: https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.1-rc1 This release is mostly a bug fix release. It also adds support for the Google Storage API. Detailed list of changes: * change how dependencies are managed: canonical deps are now in the gemspecs Server: * clarify how user_data injection should work; make sure all drivers accept base64 encoded data and make the decoded version available to instance * fix URL generation so that server works when run behind a reverse proxy * init script: honor defaults from sysconfig file * init script: fix 'status', properly background deltacloudd * deltacloudd: support verbose option * Drivers: + Condor - use UUIDTools instead of UUID to simplify deps + Google - new driver for Google storage API + RHEV-M - treat status as case-insensitive - inject data through a virtual floppy rather than modifying the instance storage directly + vSphere - report minimum of max memory across all hosts in a data center, so that instances can be placed on any host - user_data is placed in file 'deltacloud-user-data.txt' Client: * fix parsing of enums in HWP properties * fix handling of float value for number of vCPU in HWP I will update the website and docs to reflect those changes in time for the official release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] [RESULT] Release deltacloud 0.4.0 rc4
The vote resulted in 8 +1, no 0's or -1's; three +1 votes were cast by mentors (Carl Trieloff, Jim Jagielski, and Davanum Srinivas) With that, the release of Deltacloud 0.4.0 RC4 is approved and I'll move the artifacts to the proper place to make them the GA. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Deltacloud 0.4.0 (incubating)
I am pleased to announce the availability of Apache Deltacloud 0.4.0. Apache Deltacloud is a RESTful cloud abstraction API. The release consists both of the API server and a Ruby client. The release can be found at http://www.apache.org/dist/incubator/deltacloud/0.4.0/ Gems and RPM's for Fedora will become available shortly. Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: Server: * deltacloudd: new option --drivers to list all drivers; new option --daemon to daemonize the server * deltacloudd: new options --ssl, --ssl-key and --ssl-cert to enable HTTPS support * API entrypoint reports features in JSON * unify response behavior: any operation returning a 201 Created also sets the Location header to point to the new resource; ensure the status for an operation is the same regardless of output format * Add type to public addresses; type can be one of 'ipv4', 'mac', 'vnc', and 'hostname' * Complete overhaul of the HTML UI, now uses jquery-mobile * Response status for attach/detach storage is now 202 (instead of 302) * Response status for get/set blob metadata is 204 No Content * Response status for (un)register with load balancer is 204 No Content * The user_name feature now reports the permissible length of the name as the 'max_length' constraint * Add Date header to responses as per RFC 2616 * New collection 'firewalls' for managing sets of firewalling rules * split server/config/drivers.yaml into individual files so each driver can be packaged separately; gives deployers better choice of what drivers they want enabled * Numerous bug fixes and improvements to the test suite * Drivers + Condor - new driver to run a simple cloud based on the Condor grid scheduler + EC2 - Fix bug in reboot instance so that the details returned are those of the stopped instance, not some random instance - Support getting and updating blob metadata - support destroying images - support firewalls (security groups) - do not support user_name anymore; instance tagging is too fragile in EC2 to be used reliably for this - do not support registering an instance with a load balancer upon creation anymore - stream blob PUT to backend (requires thin) - support attaching EBS snapshot to instance upon creation (feature 'attach_snapshot') - support elastic IP's + Eucalyptus - support firewalls (security groups) - support elastic IP's + Gogrid - when retrieving single realm, make sure we return the right one - correctly capture load_balancer params - report a listener if load_balancer has no instances + Mock - support destroying images - refactored driver to fix various bugs, and to make it an easier to understand example of how a driver works + Rackspace - support destroying images - stream blob PUT to backend (requires thin) + RHEV-M - support creating and destroying images - report VNC address of instances - can use Audrey's confserver to fetch IP of an instance + vSphere - turns a VMWare vSphere installation into a cloud - driver stateless, state is stored in vSphere's data store in 'deltacloud' folder - images are template VM's - single HWP, whose max_cpu and max_memory are based on available cpus and memory across all vSphere hosts - support data injection via user_data and user_iso (upload entire ISO image) For both, instance gets virtual CD-ROM with injected data Client: * make authentication info for instances available * retrieve type and address for public addresses of an instance * deltacloudc: allow specifying bucket location when creating a bucket Site: * Major rewrite of REST API docs, covers the entire API now * Add libdeltacloud API docs * Add ASF incubator logo and disclaimer to project site David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc4
On Wed, 2011-08-31 at 07:36 -0400, Chris Lalancette wrote: B1;2601;0cOn 08/30/11 - 03:34:30PM, David Lutterkort wrote: On Tue, 2011-08-30 at 09:21 -0400, Chris Lalancette wrote: On 08/29/11 - 02:48:17PM, David Lutterkort wrote: Yeah, it happens during jquery's loadPage - since this only affects the HTML UI, and is more cosmetic than anything else, I'd like to defer addressing this to the next release. I'm just slightly hesitant to release with this bug in place; after all, the HTML UI is most likely the first thing people will see when they play around with deltacloud. What do others think? Let's see if an update to the beta2 for jquery-mobile 1.0 will help - can you apply the patch at [1] and see if that fixes things for you ? And doesn't break other things ? ;) David [1] http://people.apache.org/~lutter/patches/jquery-mobile-update/ I tried out this patch, but no luck. The error moved around, but is still basically the same: c is undefined I guess at this point I'm OK with us releasing like this. Hopefully it is just on this (older) Firefox version, and this won't be a widespread problem. We really should try to track it down in the near future, though. Yes, I agree, and given that it doesn't fix the problem, I'd rather not update to beta 2 in the rc. If you feel like it, try it with the unminified version of jquery mobile. You need to download both the JS and CSS from [1] and change their file names in server/views/layout.html.haml - essentially the same thing my patch did. Then try the operations that give you errors again with Firebug open - that should give you a more meaningful stacktrace in JS. From a quick look at the source, nothing fishy jumped out. Upstream does claim that they support Firefox from 3.6 on[2], so should be interested in the bug report. If you don't have time to look into it, make sure to file a Jira, so we don't lose track of the issue. David [1] http://jquerymobile.com/download/ [2] http://jquerymobile.com/gbs/#gbs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc4
On Tue, 2011-08-30 at 09:21 -0400, Chris Lalancette wrote: On 08/29/11 - 02:48:17PM, David Lutterkort wrote: Yeah, it happens during jquery's loadPage - since this only affects the HTML UI, and is more cosmetic than anything else, I'd like to defer addressing this to the next release. I'm just slightly hesitant to release with this bug in place; after all, the HTML UI is most likely the first thing people will see when they play around with deltacloud. What do others think? Let's see if an update to the beta2 for jquery-mobile 1.0 will help - can you apply the patch at [1] and see if that fixes things for you ? And doesn't break other things ? ;) David [1] http://people.apache.org/~lutter/patches/jquery-mobile-update/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc4
On Fri, 2011-08-26 at 14:34 -0400, Chris Lalancette wrote: On 08/26/11 - 11:14:15AM, David Lutterkort wrote: On Fri, 2011-08-26 at 10:22 -0400, Chris Lalancette wrote: On 08/24/11 - 04:57:18PM, David Lutterkort wrote: Hi all, I just uploaded the third release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc4/ Please vote on the release candidate by Saturday, 2011-08-27 15:00 PDT KEYS: http://www.apache.org/dist/incubator/deltacloud/KEYS svn tag: https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.0-rc4 So I just tried this out again, and I'm still not getting proper page refreshes when creating firewalls or rules on firewalls from the HTML UI. That is, the firewall or the rule gets created on the backend cloud, but it does not refresh the page properly to show the new firewall or rule. Actually, the same problem exists with Buckets and launching of instances as well. Basically anything that needs to POST won't properly refresh on my machine. Does anyone else see this? This all works flawlessly for me with Firefox 6 on F15. Can you try creating something with the firebug console open and set to 'stop on error' ? Maybe there's some Javascript issue. Heh, yeah, you can tell I haven't done this much. Firebug is giving me: c is undefined [Break On This Error] c=c.replace(location.protocol+//+loc...hadow ui-body-e ui-corner-all'h1 (this is cut-n-pasted from the firebug console) I guess that code comes from: public/javascripts/jquery.mobile-1.0b1.min.js Though that file looks like it is probably auto-generated somehow. Does that help at all? Yeah, it happens during jquery's loadPage - since this only affects the HTML UI, and is more cosmetic than anything else, I'd like to defer addressing this to the next release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc4
On Fri, 2011-08-26 at 10:22 -0400, Chris Lalancette wrote: On 08/24/11 - 04:57:18PM, David Lutterkort wrote: Hi all, I just uploaded the third release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc4/ Please vote on the release candidate by Saturday, 2011-08-27 15:00 PDT KEYS: http://www.apache.org/dist/incubator/deltacloud/KEYS svn tag: https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.0-rc4 So I just tried this out again, and I'm still not getting proper page refreshes when creating firewalls or rules on firewalls from the HTML UI. That is, the firewall or the rule gets created on the backend cloud, but it does not refresh the page properly to show the new firewall or rule. Actually, the same problem exists with Buckets and launching of instances as well. Basically anything that needs to POST won't properly refresh on my machine. Does anyone else see this? This all works flawlessly for me with Firefox 6 on F15. Can you try creating something with the firebug console open and set to 'stop on error' ? Maybe there's some Javascript issue. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc3
On Wed, 2011-08-24 at 15:13 +0100, sebb wrote: On 24 August 2011 00:21, David Lutterkort lut...@redhat.com wrote: Hi all, I just uploaded the third release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc3/ Please vote on the release candidate by Friday, 2011-08-26 15:00 PDT Where is the KEYS file? http://www.apache.org/dist/incubator/deltacloud/KEYS Where is the SVN tag? https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.0-rc3/ David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc3
On Wed, 2011-08-24 at 15:52 +0100, sebb wrote: On 24 August 2011 15:13, sebb seb...@gmail.com wrote: On 24 August 2011 00:21, David Lutterkort lut...@redhat.com wrote: Hi all, I just uploaded the third release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc3/ Please vote on the release candidate by Friday, 2011-08-26 15:00 PDT Where is the KEYS file? Where is the SVN tag? There are some inconsistencies in the archives. The NOTICE files in both archives mention redhat, yet there is no corresponding mention in the license file. If the archive(s) contain redhat code, then the LICENSE must be updated. If there is no redhat code included, then the NOTICE file must be updated to remove the reference - it's important that the NOTICE file only contains required notices. My understanding was that the NOTICE file lists copyright holders - the reference to Red Hat is there because the initial code grant came from Red Hat; since the grant was under the ASL, I don't understand why that would need to be called out separately in the LICENSE file. In any event, is there anywhere on the ASF website that clearly articulates what goes into the NOTICE and LICENSE file ? All the references I looked at are concerned more with the why than with the how. There are some files without AL headers (and no other license), for example: deltacloud-core-0.4.0/bin/deltacloudd deltacloud-core-0.4.0/config/addresses.xml deltacloud-core-0.4.0/config/condor.yaml deltacloud-core-0.4.0/config/drivers/*.yaml deltacloud-core-0.4.0/lib/deltacloud/base_driver/exceptions.rb deltacloud-core-0.4.0/lib/deltacloud/drivers/mock/data/conv.rb deltacloud-core-0.4.0/lib/deltacloud/drivers/rhevm/rhevm_client.rb deltacloud-core-0.4.0/lib/deltacloud/drivers/vsphere/vsphere_client.rb deltacloud-core-0.4.0/lib/deltacloud/drivers/vsphere/vsphere_filemanager.rb deltacloud-core-0.4.0/lib/sinatra/rack_syslog.rb deltacloud-core-0.4.0/public/javascripts/application.js deltacloud-core-0.4.0/public/stylesheets/new.css There are quite a few .yml files as well; not sure if those allow comments or not I'll add AL headers to the code files listed above (deltacloudd, *.rb, *.js, *.css) The YAML and XML files are simply data, and therefore not copyrightable by themselves in any event - I am following the precedent of how httpd ships its config files w/o license headers. The client archive does not have any AL headers in the yml files, but otherwise seems OK. Same here. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.4.0, rc4
Hi all, I just uploaded the third release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc4/ Please vote on the release candidate by Saturday, 2011-08-27 15:00 PDT KEYS: http://www.apache.org/dist/incubator/deltacloud/KEYS svn tag: https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.0-rc4 The rc4 differs from rc3 only in that missing license headers were added to files needing them, and that toplevel NOTICE and LICENSE files were schecked into svn. The rc3 differs from rc2 in the following: 1. Rename parameter 'blob' back to 'blob_id' in create blob operation to maintain backwards compatibility 2. deltacloudd: support daemonizing 3. Drivers: * Eucalyptus: make create_firewall_rule and delete_firewall_rule work * RHEV-M: improve exception handling * Mock: refactored driver to fix various bugs, and to make it an easier to understand example of how a driver works * Condor: ddded support files and configs for condor driver 4. Update/correct copyright and licensing info, based on feedback from Sebb 5. Add ASF incubator logo and disclaimer to project site 6. Various fixes in the HTML UI 7. Added rake task 'routes' to print all routes 8. Client: * fix formatting of instance addresses (Mark McLoughlin) * do not require lib/base_object to avoid LoadError The rc2 differs from rc1 in only two small changes: 1. Fix cucumber tests that failed because of the version bump 2. Fix an issue where POST requests containing matrix params were not processed correctly (e.g. POST /api;driver=mock/instances was failing) I include the announcement for rc1 for convenience: Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: Server: * deltacloudd: new option --drivers to list all drivers * deltacloudd: new options --ssl, --ssl-key and --ssl-cert to enable HTTPS support * API entrypoint reports features in JSON * unify response behavior: any operation returning a 201 Created also sets the Location header to point to the new resource; ensure the status for an operation is the same regardless of output format * Add type to public addresses; type can be one of 'ipv4', 'mac', 'vnc', and 'hostname' * Complete overhaul of the HTML UI, now uses jquery-mobile * Response status for attach/detach storage is now 202 (instead of 302) * Response status for get/set blob metadata is 204 No Content * Response status for (un)register with load balancer is 204 No Content * The user_name feature now reports the permissible length of the name as the 'max_length' constraint * Add Date header to responses as per RFC 2616 * New collection 'firewalls' for managing sets of firewalling rules * split server/config/drivers.yaml into individual files so each driver can be packaged separately; gives deployers better choice of what drivers they want enabled * Numerous bug fixes and improvements to the test suite * Drivers + Condor - new driver to run a simple cloud based on the Condor grid scheduler + EC2 - Fix bug in reboot instance so that the details returned are those of the stopped instance, not some random instance - Support getting and updating blob metadata - support destroying images - support firewalls (security groups) - do not support user_name anymore; instance tagging is too fragile in EC2 to be used reliably for this - do not support registering an instance with a load balancer upon creation anymore - stream blob PUT to backend (requires thin) - support attaching EBS snapshot to instance upon creation (feature 'attach_snapshot') - support elastic IP's + Eucalyptus - support firewalls (security groups) - support elastic IP's + Gogrid - when retrieving single realm, make sure we return the right one - correctly capture load_balancer params - report a listener if load_balancer has no instances + Mock - support destroying images + Rackspace - support destroying images - stream blob PUT to backend (requires thin) + RHEV-M - support creating and destroying images - report VNC address of instances - can use Audrey's confserver to fetch IP of an instance + vSphere - turns a VMWare vSphere installation into a cloud
[VOTE] release deltacloud 0.4.0, rc3
Hi all, I just uploaded the third release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc3/ Please vote on the release candidate by Friday, 2011-08-26 15:00 PDT The rc3 differs from rc1 in the following: 1. Rename parameter 'blob' back to 'blob_id' in create blob operation to maintain backwards compatibility 2. deltacloudd: support daemonizing 3. Drivers: * Eucalyptus: make create_firewall_rule and delete_firewall_rule work * RHEV-M: improve exception handling * Mock: refactored driver to fix various bugs, and to make it an easier to understand example of how a driver works * Condor: ddded support files and configs for condor driver 4. Update/correct copyright and licensing info, based on feedback from Sebb 5. Add ASF incubator logo and disclaimer to project site 6. Various fixes in the HTML UI 7. Added rake task 'routes' to print all routes 8. Client: * fix formatting of instance addresses (Mark McLoughlin) * do not require lib/base_object to avoid LoadError The rc2 differs from rc1 in only two small changes: 1. Fix cucumber tests that failed because of the version bump 2. Fix an issue where POST requests containing matrix params were not processed correctly (e.g. POST /api;driver=mock/instances was failing) I include the announcement for rc1 for convenience: Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: Server: * deltacloudd: new option --drivers to list all drivers * deltacloudd: new options --ssl, --ssl-key and --ssl-cert to enable HTTPS support * API entrypoint reports features in JSON * unify response behavior: any operation returning a 201 Created also sets the Location header to point to the new resource; ensure the status for an operation is the same regardless of output format * Add type to public addresses; type can be one of 'ipv4', 'mac', 'vnc', and 'hostname' * Complete overhaul of the HTML UI, now uses jquery-mobile * Response status for attach/detach storage is now 202 (instead of 302) * Response status for get/set blob metadata is 204 No Content * Response status for (un)register with load balancer is 204 No Content * The user_name feature now reports the permissible length of the name as the 'max_length' constraint * Add Date header to responses as per RFC 2616 * New collection 'firewalls' for managing sets of firewalling rules * split server/config/drivers.yaml into individual files so each driver can be packaged separately; gives deployers better choice of what drivers they want enabled * Numerous bug fixes and improvements to the test suite * Drivers + Condor - new driver to run a simple cloud based on the Condor grid scheduler + EC2 - Fix bug in reboot instance so that the details returned are those of the stopped instance, not some random instance - Support getting and updating blob metadata - support destroying images - support firewalls (security groups) - do not support user_name anymore; instance tagging is too fragile in EC2 to be used reliably for this - do not support registering an instance with a load balancer upon creation anymore - stream blob PUT to backend (requires thin) - support attaching EBS snapshot to instance upon creation (feature 'attach_snapshot') - support elastic IP's + Eucalyptus - support firewalls (security groups) - support elastic IP's + Gogrid - when retrieving single realm, make sure we return the right one - correctly capture load_balancer params - report a listener if load_balancer has no instances + Mock - support destroying images + Rackspace - support destroying images - stream blob PUT to backend (requires thin) + RHEV-M - support creating and destroying images - report VNC address of instances - can use Audrey's confserver to fetch IP of an instance + vSphere - turns a VMWare vSphere installation into a cloud - driver stateless, state is stored in vSphere's data store in 'deltacloud' folder - images are template VM's - single HWP, whose max_cpu and max_memory are based on available cpus and memory across all vSphere hosts - support data injection via user_data and user_iso (upload
Re: [VOTE] release deltacloud 0.4.0, rc2
On Thu, 2011-08-18 at 02:32 +0100, sebb wrote: On 18 August 2011 01:29, David Lutterkort lut...@redhat.com wrote: On Wed, 2011-08-17 at 04:32 +0100, sebb wrote: On 17 August 2011 00:54, David Lutterkort lut...@redhat.com wrote: Hi all, I just uploaded the second release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc2/ Is there an SVN tag that corresponds with the release? Yes, https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.0-rc2/ There should be the NOTICE and DISCLAIMER files alongside the LICENSE file at the top level of the tag. The deltacloud release consists of two main artifacts: the server and the (ruby) client; anything that goes into these artifacts is kept in the server/ and client/ subdirectories. The corresponding NOTICE etc. files are in these directories. None of the other subdirectories in svn are part of the release artifacts - some of them contain the project site, others contain clients that we'd like to add to the releases at some point, but they are currently not in a state where I'd want to include them in a release. Generally all SVN content is also present in the archives, but there can be exceptions, e.g. for sandbox code and the DOAP file. But if some source is omitted, it must still be possible to build the code from the source archive without needing to check out SVN source. Yes, the server and client archives are self-contained (in terms of deltacloud code, of course, they depend on external libraries) and generally users will install them on different machines. Also, what about the KEYS file so sigs can be checked? That's in the official download directory: http://www.apache.org/dist/incubator/deltacloud/ I notice that your key does not mention apache at all. Perhaps you could add your apache e-mail address? Just did that, and uploaded the amended key to the keyserver and updated the KEYS file. Yes, see for example the httpd license file at: http://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE Ok, I just committed changes for the NOTICE and LICENSE files in server/ and client/ 3rd time lucky? There's luck involved ? ;) David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.4.0, rc2
On Wed, 2011-08-17 at 04:32 +0100, sebb wrote: On 17 August 2011 00:54, David Lutterkort lut...@redhat.com wrote: Hi all, I just uploaded the second release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc2/ Is there an SVN tag that corresponds with the release? Yes, https://svn.apache.org/repos/asf/incubator/deltacloud/tags/release-0.4.0-rc2/ Also, what about the KEYS file so sigs can be checked? That's in the official download directory: http://www.apache.org/dist/incubator/deltacloud/ The NOTICE file says 2010 It also mentions 3rd party software by IBM and others, but there don't seem to be any corresponding licences in the LICENSE file. I will fix both these for the next rc. Do I need to include the full text of licenses ? For example, for an MIT licensed component, do I need to add MIT License ... full text ... Component XYZ, written by hack...@example.org, is licensed under the MIT license provided above The jquery headers state that the code is available either under the MIT or GPL 2 licences; the LICENSE file needs to be very clear which one we are choosing, as the ASF policy is not to include GPL 2 code. Yes, using them under MIT is the intent. Sorry, but I think these are blockers. Thanks for pointing these out; I'll send another mail when rc3 is ready, hopefully tomorrow. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.4.0, rc2
Hi all, I just uploaded the second release candidate for Deltacloud 0.4.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.4.0/rc2/ Please vote on the release candidate by Friday, 2011-08-19 15:00 PDT The rc2 differs from rc1 in only two small changes: 1. Fix cucumber tests that failed because of the version bump 2. Fix an issue where POST requests containing matrix params were not processed correctly (e.g. POST /api;driver=mock/instances was failing) I include the announcement for rc1 for convenience: Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: Server: * deltacloudd: new option --drivers to list all drivers * deltacloudd: new options --ssl, --ssl-key and --ssl-cert to enable HTTPS support * API entrypoint reports features in JSON * unify response behavior: any operation returning a 201 Created also sets the Location header to point to the new resource; ensure the status for an operation is the same regardless of output format * Add type to public addresses; type can be one of 'ipv4', 'mac', 'vnc', and 'hostname' * Complete overhaul of the HTML UI, now uses jquery-mobile * Response status for attach/detach storage is now 202 (instead of 302) * Response status for get/set blob metadata is 204 No Content * Response status for (un)register with load balancer is 204 No Content * The user_name feature now reports the permissible length of the name as the 'max_length' constraint * Add Date header to responses as per RFC 2616 * New collection 'firewalls' for managing sets of firewalling rules * split server/config/drivers.yaml into individual files so each driver can be packaged separately; gives deployers better choice of what drivers they want enabled * Numerous bug fixes and improvements to the test suite * Drivers + Condor - new driver to run a simple cloud based on the Condor grid scheduler + EC2 - Fix bug in reboot instance so that the details returned are those of the stopped instance, not some random instance - Support getting and updating blob metadata - support destroying images - support firewalls (security groups) - do not support user_name anymore; instance tagging is too fragile in EC2 to be used reliably for this - do not support registering an instance with a load balancer upon creation anymore - stream blob PUT to backend (requires thin) - support attaching EBS snapshot to instance upon creation (feature 'attach_snapshot') - support elastic IP's + Eucalyptus - support firewalls (security groups) - support elastic IP's + Gogrid - when retrieving single realm, make sure we return the right one - correctly capture load_balancer params - report a listener if load_balancer has no instances + Mock - support destroying images + Rackspace - support destroying images - stream blob PUT to backend (requires thin) + RHEV-M - support creating and destroying images - report VNC address of instances - can use Audrey's confserver to fetch IP of an instance + vSphere - turns a VMWare vSphere installation into a cloud - driver stateless, state is stored in vSphere's data store in 'deltacloud' folder - images are template VM's - single HWP, whose max_cpu and max_memory are based on available cpus and memory across all vSphere hosts - support data injection via user_data and user_iso (upload entire ISO image) For both, instance gets virtual CD-ROM with injected data Client: * make authentication info for instances available * retrieve type and address for public addresses of an instance * deltacloudc: allow specifying bucket location when creating a bucket Site: * Major rewrite of REST API docs, covers the entire API now * Add libdeltacloud API docs I will update the website and docs to reflect those changes in time for the official release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [RESULT] Release deltacloud 0.3.0 rc3
On Thu, 2011-04-28 at 13:49 +0200, Michal Fojtik wrote: On Apr 27, 2011, at 7:20 PM, David Lutterkort wrote: The vote resulted in 8 +1, no 0's or -1's; two +1 votes were cast by mentors (Carl and Jim) With that, the release of Deltacloud 0.3.0 RC3 is approved and I'll move the artifacts to the proper place to make them the GA. Excellent news! So that means I can push gem to rubygems and start RPM packaging? Yes, please. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] [RESULT] Release deltacloud 0.3.0 rc3
The vote resulted in 8 +1, no 0's or -1's; two +1 votes were cast by mentors (Carl and Jim) With that, the release of Deltacloud 0.3.0 RC3 is approved and I'll move the artifacts to the proper place to make them the GA. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.3.0 (RC2)
On Tue, 2011-04-12 at 16:38 -0700, David Lutterkort wrote: I just uploaded the second release candidate for Deltacloud 0.3.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.3.0/rc2/ Cancelling this vote, since I am about to upload RC3 David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.3.0 (RC3)
Hi all, I just uploaded the third release candidate for Deltacloud 0.3.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.3.0/rc3/ This RC fixes a critical bug in the EC2 driver. Please vote on the release candidate by Friday, 2011-04-22 5pm PDT. Overview of the changes for this release: Server: * Dynamic driver switching: select driver on a per-request basis; new toplevel 'drivers' collection describing drivers supported by server * Create images from running instances (EC2, Mock, GoGrid, Rackspace); advertised as action 'create_image' in instance details when possible * New 'user_files' feature for create_instance to advertise RAX-style injection of user data * Return status 204 after successful DELETE operation * Return status 401 when authentication fails because of invalid credentials * Blobs: support user metadata as key/value pairs passed through X-Deltacloud-Blobmeta-KEY: VALUE headers * Support HEAD requests to retrieve the operations and methods supported by a collection * Support for OPTIONS request to retrieve optional and required parameters for operations * Advertise 'create_instance' action for each image * Drivers + EC2 - instance_count feature to allow creating multiple instances at once - run commands inside an insance via ssh - by default, list images owned by 'amazon', when passing in empty owner_id, list _all_ images (thousands) + Eucalyptus - new driver for Eucalyptus (Sang-Min Park) + Gogrid - run commands inside an insance via ssh - allow creating sandbox instances + Rackspace - report root password after instance creation + SBC - new driver for IBM SBC cloud (Eric Woods) Client: * run: new method to run commands via ssh * drivers: list drivers supported by server * properly list blobs in a bucket when showing bucket details * full support for managing blobs and buckets I will update the website and docs to reflect those changes in time for the official release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.3.0
On Fri, 2011-04-08 at 17:03 -0700, David Lutterkort wrote: On Thu, 2011-04-07 at 18:17 +0100, sebb wrote: On 7 April 2011 17:24, David Lutterkort lut...@redhat.com wrote: Many of the source files contain Copyright (C) 2009-2011 Red Hat, Inc. or other copyright attributions. AFAIK, you need to ask the owner for permission to remove them, or at least to move them to the NOTICE file. I've removed all the Red Hat copyright statements from individual files and added a sentence to the NOTICE file. There are a few more copyright statements that could be moved; I have contacted the authors of those to obtain permission to move them. I hope it is ok if we go ahead with the release with those headers in place. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.3.0 (RC2)
Hi all, I just uploaded the second release candidate for Deltacloud 0.3.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.3.0/rc2/ Please vote on the release candidate by Friday, 2011-04-15 5pm PDT. Overview of the changes for this release: Server: * Dynamic driver switching: select driver on a per-request basis; new toplevel 'drivers' collection describing drivers supported by server * Create images from running instances (EC2, Mock, GoGrid, Rackspace); advertised as action 'create_image' in instance details when possible * New 'user_files' feature for create_instance to advertise RAX-style injection of user data * Return status 204 after successful DELETE operation * Return status 401 when authentication fails because of invalid credentials * Blobs: support user metadata as key/value pairs passed through X-Deltacloud-Blobmeta-KEY: VALUE headers * Support HEAD requests to retrieve the operations and methods supported by a collection * Support for OPTIONS request to retrieve optional and required parameters for operations * Advertise 'create_instance' action for each image * Drivers + EC2 - instance_count feature to allow creating multiple instances at once - run commands inside an insance via ssh - by default, list images owned by 'amazon', when passing in empty owner_id, list _all_ images (thousands) + Eucalyptus - new driver for Eucalyptus (Sang-Min Park) + Gogrid - run commands inside an insance via ssh - allow creating sandbox instances + Rackspace - report root password after instance creation + SBC - new driver for IBM SBC cloud (Eric Woods) Client: * run: new method to run commands via ssh * drivers: list drivers supported by server * properly list blobs in a bucket when showing bucket details * full support for managing blobs and buckets I will update the website and docs to reflect those changes in time for the official release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.3.0
Hi, thanks for the review; I've addressed most of the issues you found. I will finish that on Monday and spin RC2. For my education: is there a good checklist for what needs to be in a release ? It seems that the requirements are fairly well distributed across the Apache website. Some comments below: On Thu, 2011-04-07 at 18:17 +0100, sebb wrote: On 7 April 2011 17:24, David Lutterkort lut...@redhat.com wrote: Hi all, I just uploaded a release candidate for Deltacloud 0.3.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.3.0/rc1/ Please vote on the release candidate by Monday, 2011-04-10 8:00 PDT Where is the SVN tag for the release? Only had tag in my local git - pushed that as SVN tag release-0.3.0-rc1 and the KEYS file? http://www.apache.org/dist/incubator/deltacloud/KEYS The tar.gz files don't contain a NOTICE file Moving that from trunk/ to trunk/client/ and trunk/server/ so it gets picked up by the release scripts and they don't contain a LICENSE file - the COPYING file won't do as a substitute. Renamed the files. There's no DISCLAIMER. Added one. The website also needs a disclaimer and a more obvious notification that it is an Incubator project. Will do that on Monday. The hashes need to be stored as separate files, one for each archive (as for the sigs in the .asc files). Changed my release script. Many of the source files contain Copyright (C) 2009-2011 Red Hat, Inc. or other copyright attributions. AFAIK, you need to ask the owner for permission to remove them, or at least to move them to the NOTICE file. There are some other files with non AL headers; these may also need to be attributed in the NOTICE file. I find this extremely confusing - why remove the copyright attribution ? Isn't it clearer if each file states who holds copyright in it ? In any event, I assume I can move the copyright notices for the files that were part of the initial grant, and that come from contributors; there's also a handful of files that we use under the MIT license - can I leave the copyright attribution in them ? Also, it seems to me that the boilerplate text of the NOTICE file is incorrect since it states 'Copyright The Apache Software Foundation' but the contributor license agreement does not actually assign copyright to the ASF (which would be impossible in some jurisdictions anyway) - what exactly does the NOTICE file accomplish ? The FAQ [1] does not really have an answer for this, as it only refers to a previously used header that incorrectly claimed ASF Copyright. David [1] http://apache.org/legal/src-headers.html#notice - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.3.0
Hi all, I just uploaded a release candidate for Deltacloud 0.3.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.3.0/rc1/ Please vote on the release candidate by Monday, 2011-04-10 8:00 PDT Overview of the changes for this release: Server: * Dynamic driver switching: select driver on a per-request basis; new toplevel 'drivers' collection describing drivers supported by server * Create images from running instances (EC2, Mock, GoGrid, Rackspace); advertised as action 'create_image' in instance details when possible * New 'user_files' feature for create_instance to advertise RAX-style injection of user data * Return status 204 after successful DELETE operation * Return status 401 when authentication fails because of invalid credentials * Blobs: support user metadata as key/value pairs passed through X-Deltacloud-Blobmeta-KEY: VALUE headers * Support HEAD requests to retrieve the operations and methods supported by a collection * Support for OPTIONS request to retrieve optional and required parameters for operations * Advertise 'create_instance' action for each image * Drivers + EC2 - instance_count feature to allow creating multiple instances at once - run commands inside an insance via ssh - by default, list images owned by 'amazon', when passing in empty owner_id, list _all_ images (thousands) + Eucalyptus - new driver for Eucalyptus (Sang-Min Park) + Gogrid - run commands inside an insance via ssh - allow creating sandbox instances + Rackspace - report root password after instance creation + SBC - new driver for IBM SBC cloud (Eric Woods) Client: * run: new method to run commands via ssh * drivers: list drivers supported by server * properly list blobs in a bucket when showing bucket details * full support for managing blobs and buckets I will update the website and docs to reflect those changes in time for the official release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] release deltacloud 0.2.0
Sorry - forgot to mention this on the list: seeing how we'll try and make another release in a couple weeks, and the amount of churn fixing the license headers would introduce, we'll just skip 0.2.0. David On Wed, 2011-02-23 at 07:06 +, Mark Struberg wrote: I grepped through all *.rb files which don't have the apache license URL in it and compared this list with the find . -name *.rb. Think there were more than 3 misses, but don't remember in detail anymore. anyway -1 for the 0.2 release and +1 for the relicense. Please also record this fact in the IP clearance log! LieGrue, strub --- On Wed, 2/23/11, David Lutterkort lut...@redhat.com wrote: From: David Lutterkort lut...@redhat.com Subject: Re: [VOTE] release deltacloud 0.2.0 To: general@incubator.apache.org Date: Wednesday, February 23, 2011, 12:11 AM On Mon, 2011-02-21 at 16:23 +, Mark Struberg wrote: I'm not really fit with ruby projects, but there are quite a few sources with LGPL license headers. e.g. ./lib/deltacloud/drivers/opennebula/opennebula_driver.rb Yes, it seems the three files in server/lib/deltacloud/drivers/opennebula/ fell through the cracks when we did the initial code donations. I did get permission to relicense to ASL 2.0 from the original authors at that time - I'll correct the license headers in svn. David - 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: [VOTE] release deltacloud 0.2.0
On Mon, 2011-02-21 at 16:23 +, Mark Struberg wrote: I'm not really fit with ruby projects, but there are quite a few sources with LGPL license headers. e.g. ./lib/deltacloud/drivers/opennebula/opennebula_driver.rb Yes, it seems the three files in server/lib/deltacloud/drivers/opennebula/ fell through the cracks when we did the initial code donations. I did get permission to relicense to ASL 2.0 from the original authors at that time - I'll correct the license headers in svn. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] release deltacloud 0.2.0
Hi all, I just uploaded a release candidate for Deltacloud 0.2.0. The rc is available from http://people.apache.org/~lutter/deltacloud/0.2.0/rc2/ Please vote on whether this should become the official 0.2.0 release by Thursday, 2011-02-17 11:00am PST (Saturday 2011-02-17 19:00 UTC, see http://bit.ly/e0Q2C5 for other local times) Overview of the high-level changes in this release: * Dynamically select driver through the X-Deltacloud-Driver HTTP header; allow passing in driver-specific endpoint with the X-Deltacloud-Provider header * New 'load_balancers' collection, supported for EC2 and GoGrid * Allow creation/deletion of blobs (S3, CloudFiles, Azure) * Return HTTP status 405 when trying to perform an action on a instance that is not available * Drivers + EC2 - security_group and public_ip features for instance creation - switched to aws gem + GoGrid: now have two hardware profiles + RHEV-M: completely rewritten; now uses RHEV-M REST API, not Powershell + Mock: - support 'keys' collection - switch to storage-only driver by setting provider to 'storage' I will update the website and docs to reflect those changes in time for the official release. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Accepting patches in a podling
On Tue, 2010-09-14 at 04:22 +0200, Daniel Shahaf wrote: FWIW, what Subversion uses: http://subversion.apache.org/docs/community-guide/community-guide.html#patches http://subversion.apache.org/docs/community-guide/community-guide.html#patch-manager Briefly, all patches go to dev@, and only the unlucky patches that were neither applied nor rejected get stashed in the issue tracker to avoid being dropped on the floor. This seems a very workable approach - going through Jira for everything is too much work on the part of the contributer. I'll use that as the submission policy for Deltacloud from now on: * Patch submittes must have a CLA on file * Patches need to go to the dev@ list (and be ACK'd there) * In some cases, we might ask the submitter to put the patch into Jira (e.g., for large contributions) Only tangentially related: is there a way to make subversion (especially via git-svn) distinguish between a committer and an author ? That would help keep the patch submission trail much more transparent. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Accepting patches in a podling
What is the offical process for accepting patches from non-comitters in a podling ? Is it enough to insist that contributors that are not committers have a CLA on file or do I also have to make them file each patch in jira ? David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Deltacloud into incubator
Hi all, by my count, the vote for Deltacloud yielded 13 +1 votes and no 0 or -1 votes. I will work with Carl to get Deltacloud set up in the incubator. thanks to everybody for the very positive reception, David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Deltacloud Project
Hi all, after the discussion so far [1], I'd like to put Detlacloud for a vote for acceptance into the Apache Incubator according to the proposal[2] I _think_ I've added everybody who expressed interest in being a mentor or initial committer to the proposal - if I have forgotten anybody, please holler. Please reply to this mail with your vote. David [1] http://mail-archives.apache.org/mod_mbox/incubator-general/201005.mbox/%3c1273174879.7253.99.ca...@avon.watzmann.net%3e [2] 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 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, 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
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
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
[PROPOSAL] Deltacloud Project
into the Incubator. Meritocracy --- Deltacloud API accepts patches from anybody, based solely on technical merit, and will give commit rights to contributors with a proven technical track record. Communication is done through an IRC channel on freenode and the two mailing lists above. The mailing lists will be migrated to the ASF project list on acceptance into the Incubator. Community - Because it was started by Red Hat, the majority of the initial contribution is from Red Hat employees, though we have received and accepted a number of patches from outside sources, particularly, from a number of cloud providers. 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. API Developers -- * Bob McWhirter (initial developer) * David Lutterkort (current maintainer) * Michal Fojtik * Ivan Meredith * Daniel Molina Aranda Alignment - Currently, there are no other Apache projects concerned with building a cross-cloud API as a web service. However, we feel it will be a strong complement to the set of Apache projects, and provide any other Apache project an API for interacting with any cloud provider. Known Risks --- - Orphaned Products Deltacloud API is actively used by other Red Hat projects. I have received interest in Deltacloud API both from some cloud providers and other organizations in joining the project. We feel that it is importatant 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 I have been involved with Open Source Software for over a decade; I have actively contributed to puppet (http://www.puppetlabs.com/), where I was one of the earliest contributors, libvirt (http://libvirt.org/), virt-manager (http://virt-manager.et.redhat.com/), and a number of other projects. I started and maintain two projects, Augeas (http://augeas.net/) and netcf (https://fedorahosted.org/netcf/) related to systems management. - Homogenous Developers While much of the initial code base has been written by Red Hat, several of the backend drivers and some important aspects of the API design have been heavily influenced by outside contributors. - Reliance on Salaried Developers Currently the project has mostly salaried developers. Expanding the diversity of the project's developers is one of the areas we will actively work on in the Incubator, and will be a crucial factor in making Deltacloud a successful project. - Relationships with Other Apache Products Currently there are not really any stong relationships with other Apache projects. There is a certain amount of overlap with libcloud (http://incubator.apache.org/libcloud/), though the projects differ in scope and goals. At its most basic, libcloud is a Python in-process API, whereas Deltacloud is a web service written in Ruby. - An Excessive Fascination with the Apache Brand We seek to build a lasting community around Deltacloud API; the most important reason for proposing this project for the incubator is to clarify project governance to other parties, to allow them more easily to join and contribute to the project, and for the project to be managed and governed independently. Documentation - * API definition (http://deltacloud.org/api.html) * Supported drivers (http://deltacloud.org/drivers.html) * Ruby Client (http://deltacloud.org/client-ruby.html) * Writing new drivers (http://deltacloud.org/framework.html) Documentation is maintained in a separate, public git repository (http://git.fedorahosted.org/git/?p=deltacloud/docs.git;a=shortlog;h=refs/heads/next) Initial Source -- All sources can be found in the git repositories mentioned above. External Dependencies - Deltacloud is written in Ruby; there are a number of Ruby libraries that the code depends on, most importantly: * Ruby * Sinatra (http://www.sinatrarb.com/) * HAML (http://haml-lang.com/) * thin (http://code.macournoyer.com/thin/) A complete list of dependencies can be found in the deltacloud-core.gemspec in the core repository. All dependencies are licensed under either the Ruby License or the MIT License. Cryptography Uses standard Ruby APIs for SSL/HTTPS Required Resources -- * Mailing lists * deltacloud-devel * deltacloud-commits * deltacloud-private * Subversion * https://svn.apache.org/repos/asf/incubator/deltacloud * Issue Tracking * Bugzilla (deltacloud) Initial Committers -- * David Lutterkort lut...@redhat.com * Michal Fojtik mfoj...@redhat.com * Marios Andreou mandr...@redhat.com * Andrew N Cadel cade...@jpmorgan.com Sponsors
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
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
