You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Graham Gear (JIRA)" <ji...@apache.org> on 2013/05/02 00:24:16 UTC
[jira] [Comment Edited] (WHIRR-721) Improve robustness of volume
device detection
[ https://issues.apache.org/jira/browse/WHIRR-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647005#comment-13647005 ]
Graham Gear edited comment on WHIRR-721 at 5/1/13 10:22 PM:
------------------------------------------------------------
Patch [graham-patch-WHIRR-721-1.patch|https://issues.apache.org/jira/secure/attachment/12581429/graham-patch-WHIRR-721-1.patch] submitted:
* Attempts to map cloud provider devices to new Xen VPS device names if the existing mapping fails
* Bails out on volume format/mount/link if device mapping not found
* If no cloud provider boot volume defined, assume it is the first in the natural order device name list
Tested on EC2 with CentOS 6.4, medium and large instances.
was (Author: graham.gear):
Patch [graham-patch-WHIRR-721-1.patch|https://issues.apache.org/jira/secure/attachment/12581429/graham-patch-WHIRR-721-1.patch] submitted:
* Attempts to map cloud provider devices to new Xen VPS device names if the existing mapping fails
* Bails out on volume format/mount/link if device mapping not found
* If no cloud provider boot volume defined, assume it is the first in the natural order device name list
> Improve robustness of volume device detection
> ---------------------------------------------
>
> Key: WHIRR-721
> URL: https://issues.apache.org/jira/browse/WHIRR-721
> Project: Whirr
> Issue Type: Improvement
> Components: service/hadoop
> Affects Versions: 0.8.2
> Reporter: Graham Gear
> Assignee: Graham Gear
> Fix For: 0.8.3
>
> Attachments: graham-patch-WHIRR-721-1.patch
>
>
> The current volume device detection does not account for the cloud provider often not reporting the boot device and the new remapping of Xen VPS devices in later kernels (eg RHEL/CentOS 6.1+).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira