[
https://issues.apache.org/jira/browse/CLOUDSTACK-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daan Hoogland closed CLOUDSTACK-4712.
-------------------------------------
Resolution: Won't Fix
> Add support for multiple local primary storage devices on KVM and XenServer
> ---------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4712
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4712
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, KVM, Storage Controller, XenServer
> Affects Versions: 4.1.1
> Reporter: Kirk Kosinski
> Labels: kvm, storage, xenserver
>
> If a host has multiple local storage devices, or if a local storage device is
> added to a host after it is added to CloudStack, the only way to add it as
> primary storage in CloudStack is to use the PreSetup option for XenServer or
> SharedMountPoint for KVM.
> One big problem with the workaround on XenServer (and probably on KVM) is
> that the storage allocator assumes that if a primary storage has the
> "PreSetup" pool_type (storage_pool table), it must be shared storage. This
> are multiple problems caused by this, at least:
> 1. Even with system.vm.use.local.storage = false, system VMs will be deployed
> to the local SR added as PreSetup.
> 2. Compute and disk offerings with storage type = local will not deploy to
> the local SR added as PreSetup.
> Due to the above disadvantages and others, and since XenServer and KVM hosts
> support multiple local storage devices, CloudStack should be able to support
> such a configuration. There should be a way to add local primary storage
> besides using the PreSetup and SharedMountPoint options, or if these are
> used, CloudStack should detect if it is local storage and set the correct
> pool_type.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
