[CLOUDSTACK-4712] Add support for multiple local primary storage devices on KVM and XenServer

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 4.1.1
• Component/s: Hypervisor Controller, KVM, Storage Controller, XenServer
• Security Level: Public (Anyone can view this level - this is the default.)
• Labels: kvm storage xenserver
• Assignee: Unassigned
• Reporter: Kirk Kosinski
• Created: 19/Sep/13 22:55
• Updated: 08/Feb/17 09:23
• Resolved: 08/Feb/17 09:23

Description

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.