[
https://issues.apache.org/jira/browse/HADOOP-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796811#action_12796811
]
Aaron Kimball commented on HADOOP-6464:
---------------------------------------
Can you please describe the test plan you used to actually test end-to-end
coverage of rackspace?
regarding the patch:
see comments re. TERREMARK_KEY in HADOOP-6465 for RACKSPACE_KEY, etc.
re. boot script: I noticed a lot of very similar code in the terremark boot
script. Can some of this be factored out into a common utility script that gets
sourced in? This seems to be a looming maintenence problem.
RackspaceCluster.wait_for_instances() looks like a clone of
TerremarkCluster.wait_for_instances(). Can this be pushed up into cluster?
Ditto with _all_started(), _ip_list_to_string(), terminate()?
Why is rackspace remote-setup.sh strictly-ubuntu-based? The boot script looks
like it also handles centos.
> Write a Rackspace cloud provider
> --------------------------------
>
> Key: HADOOP-6464
> URL: https://issues.apache.org/jira/browse/HADOOP-6464
> Project: Hadoop Common
> Issue Type: New Feature
> Components: contrib/cloud
> Reporter: Tom White
> Assignee: Tom White
> Attachments: HADOOP-6464.patch
>
>
> The scripts in contrib/cloud currently only support running on EC2. This
> issue is to add support for running Hadoop clusters on Rackspace Cloud
> Servers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
