Howdy Folks,
So Michal and I have been working on a Condor based cloud using deltacloud as the front end API. The code base can be found here:
http://git.fedorahosted.org/git/?p=condor-cloud.git
There are still some cleanups and testing to be done but I would like to get this into Fedora 16 as a feature. I am hoping you guys can take a look and let me know if this is acceptable and what needs to be fixed to make it so.
There are actually two parts to this project, one is the deltacloud driver, which can be found under the deltacloud-condor-driver directory. The rest deals with condor configuration and scripts.
I'm thinking I may name this project 'falcondor' as it seems unused and more interesting :).
Thanks!
Ian
Greetings! Ian Main wrote:
Howdy Folks,
So Michal and I have been working on a Condor based cloud using deltacloud as the front end API. The code base can be found here:
http://git.fedorahosted.org/git/?p=condor-cloud.git
There are still some cleanups and testing to be done but I would like to get this into Fedora 16 as a feature. I am hoping you guys can take a look and let me know if this is acceptable and what needs to be fixed to make it so.
There are actually two parts to this project, one is the deltacloud driver, which can be found under the deltacloud-condor-driver directory. The rest deals with condor configuration and scripts.
I'm thinking I may name this project 'falcondor' as it seems unused and more interesting :).
Thanks!
Ian
Thank you for your work on this, this looks interesting. The Condor grid community will likely find this interesting as a way to enable private cloud services on existing compute grids - but you should let them know by sending something to condor-users and/or condor-devel.
What's the status on committing the aeolus-condor patches upstream? I think you'd need to provide pointers in DEVELOPERS.txt on how to pull from Condor's upstream instead of pulling from aeolus's yum repo before you send that community an announcement.
Along the same vein, this seems like it might be a good candidate for a contributed module to Condor:
https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=ContribModules
Has that been considered? Doing so would increase exposure within the Condor community, who would presumeably be the primary user of this project.
-- Lans Carstensen, Systems Engineering, Dreamworks Animation Vision without execution is hallucination. -- Thomas Edison
On Sat, Jul 09, 2011 at 06:37:52PM -0700, Lans Carstensen wrote:
Greetings! Ian Main wrote:
Howdy Folks,
So Michal and I have been working on a Condor based cloud using deltacloud as the front end API. The code base can be found here:
http://git.fedorahosted.org/git/?p=condor-cloud.git
There are still some cleanups and testing to be done but I would like to get this into Fedora 16 as a feature. I am hoping you guys can take a look and let me know if this is acceptable and what needs to be fixed to make it so.
There are actually two parts to this project, one is the deltacloud driver, which can be found under the deltacloud-condor-driver directory. The rest deals with condor configuration and scripts.
I'm thinking I may name this project 'falcondor' as it seems unused and more interesting :).
Thanks!
Ian
Thank you for your work on this, this looks interesting. The Condor grid community will likely find this interesting as a way to enable private cloud services on existing compute grids - but you should let them know by sending something to condor-users and/or condor-devel.
What's the status on committing the aeolus-condor patches upstream? I think you'd need to provide pointers in DEVELOPERS.txt on how to pull from Condor's upstream instead of pulling from aeolus's yum repo before you send that community an announcement.
Along the same vein, this seems like it might be a good candidate for a contributed module to Condor:
https://condor-wiki.cs.wisc.edu/index.cgi/wiki?p=ContribModules
Has that been considered? Doing so would increase exposure within the Condor community, who would presumeably be the primary user of this project.
Well one thing at a time I think. I think getting this into deltacloud is the next logical step since it is very tightly coupled to deltacloud. Getting it into the codebase will allow it to be more easily installed.
Once that happens I'll see about spreading the word a bit more.
Ian
On Fri, 2011-07-08 at 13:06 -0700, Ian Main wrote:
So Michal and I have been working on a Condor based cloud using deltacloud as the front end API. The code base can be found here:
Very cool.
I completely agree that this should be merged into deltacloud proper. Some notes from looking at the code:
* Remove 'Copyright ...' from all source files (have a look at the other drives for proper headers) * There's some trailing whitespace trouble * condor_driver.rb:58: Don't set CONDOR_MAPPER_DIR to something that's relative to File::dirname(__FILE__) - instead write to /var/tmp (we really ought to claim /var/lib/deltacloud for things like this) * condor_driver.rb (create_instance): I find encoding config_server IP and uuid very ugly. Could the config_server IP become part of the config of condor-cloud ? Could we use the API_PROVIDER for this ? The uuid could be passed in as the user_name of the instance. The comment explaining what's happening with user_data also doesn't match the code * condor_driver.rb (valid_credentials?): something a little less hardcoded would be nice ;) * condor_driver.rb (remove_key): do we really want to ignore _all_ exceptions and just log a warning ? If that is really intended, it deserves a comment * client/base_models.rb: I assume this will be removed, and the code will use the standard models from lib/deltacloud/models/ * there don't seem to be any tests for the actual driver - we will need to figure out a plan for adding them
David
[ CC'd incubator list - DOH! ]
On Mon, Jul 11, 2011 at 03:41:06PM -0700, David Lutterkort wrote:
On Fri, 2011-07-08 at 13:06 -0700, Ian Main wrote:
So Michal and I have been working on a Condor based cloud using deltacloud as the front end API. The code base can be found here:
Very cool.
I completely agree that this should be merged into deltacloud proper. Some notes from looking at the code:
* Remove 'Copyright ...' from all source files (have a look at the other drives for proper headers) * There's some trailing whitespace trouble * condor_driver.rb:58: Don't set CONDOR_MAPPER_DIR to something that's relative to File::dirname(__FILE__) - instead write to /var/tmp (we really ought to claim /var/lib/deltacloud for things like this) * condor_driver.rb (create_instance): I find encoding config_server IP and uuid very ugly. Could the config_server IP become part of the config of condor-cloud ? Could we use the API_PROVIDER for this ? The uuid could be passed in as the user_name of the instance. The comment explaining what's happening with user_data also doesn't match the code * condor_driver.rb (valid_credentials?): something a little less hardcoded would be nice ;) * condor_driver.rb (remove_key): do we really want to ignore _all_ exceptions and just log a warning ? If that is really intended, it deserves a comment * client/base_models.rb: I assume this will be removed, and the code will use the standard models from lib/deltacloud/models/ * there don't seem to be any tests for the actual driver - we will need to figure out a plan for adding them
David
OK, I will start on these today. Thanks!
Ian
deltacloud-devel@lists.fedorahosted.org