Hi, I recently updated my local repo and noticed that we now require a hypervisor type to be associated with zone-wide primary storage.
I was wondering what the motivation for this might be? In my case, my zone-wide primary storage represents a SAN. Volumes are carved out of the SAN as needed and can currently be utilized on both Xen and VMware (although, of course, once you've used a given volume on one hypervisor type or the other, you can only continue to use it with that hypervisor type). I guess the point being my primary storage can be associated with more than one hypervisor type because of its dynamic nature. Can someone fill me in on the reasons behind this recent change and recommendations on how I should proceed here? Thanks! -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
