Hi Edison and Marcus (and anyone else this may be of interest to), So, as of 4.3 I have added support for data disks for managed storage for XenServer, VMware, and KVM (a 1:1 mapping between a CloudStack volume and a volume on a storage system). One of the most useful abilities this enables is support for guaranteed storage quality of service in CloudStack.
One of the areas I'm working on for CS 4.4 is root-disk support for managed storage (both with templates and ISOs). I'd like to get your opinion about something. I noticed when we download a template to a XenServer SR that we leverage a table in the DB called template_spool_ref. This table keeps track of whether or not we've downloaded the template in question to the SR in question already. The problem for managed storage is that the storage pool itself can be associated with many SRs (not all necessarily in the same cluster even): one SR per volume that belongs to the managed storage. What this means is every time a user wants to place a root disk (that uses a template) on managed storage, I will need to download a template to the applicable SR (the template will never be there in advance). That is fine. The issue is that I cannot use the template_spool_ref table because it is intended on mapping a template to a storage pool (1:1 mapping between the two) and managed storage can download the same template many times. It seems I will need to add a new table to the DB to support this feature. My table would allow a mapping between a template and a volume from managed storage. Do you see an easier way around this or is this how you recommend I proceed? 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> *™*
