You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/07/28 14:01:44 UTC
[jira] [Commented] (CLOUDSTACK-6170) Support managed storage for
root disks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076162#comment-14076162 ]
ASF subversion and git services commented on CLOUDSTACK-6170:
-------------------------------------------------------------
Commit 1e9e53039150f3f3743bb343e0d06e05aafb5b84 in cloudstack's branch refs/heads/4.4 from [~mike-tutkowski]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1e9e530 ]
CLOUDSTACK-6170 (VMware root-disk support for managed storage)
(cherry picked from commit a542b6fd825da1d3582a282bcc0e67abd62964bf)
> Support managed storage for root disks
> --------------------------------------
>
> Key: CLOUDSTACK-6170
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6170
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.4.0
> Environment: I expect to support managed storage for root disks on XenServer and ESX (KVM is targeted for 4.5).
> Reporter: Mike Tutkowski
> Assignee: Mike Tutkowski
> Fix For: 4.4.0
>
>
> Cloud environments have a need for guaranteed storage performance. By this I mean having the ability to specify a minimum and maximum number of IOPS on a volume-by-volume basis.
> I added support for this for XenServer and ESX in 4.2 for data disks.
> I added support for this for KVM in 4.3 for data disks.
> It is my intent to add support for this for XenServer and ESX in 4.4 for root disks (with subsequent support for root disks on KVM expected in 4.5).
> The main changes are expected to occur in CloudStack logic that controls hypervisors and additions to the way root-volume orchestration happens.
--
This message was sent by Atlassian JIRA
(v6.2#6252)