[
https://issues.apache.org/jira/browse/CLOUDSTACK-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942531#comment-13942531
]
ASF subversion and git services commented on CLOUDSTACK-6170:
-------------------------------------------------------------
Commit a1831bc86417bccc54102a143c047aaa6fc1efe4 in cloudstack's branch
refs/heads/master from [~minchen07]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a1831bc ]
Revert "CLOUDSTACK-6170" due to unit test failure.
This reverts commit 50b5e2e247ebff54fda8c8c2cd4957ffd47bcf12.
> 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 (ESX and KVM are 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)
