[Thincrust-devel] packaging of sparse raw disk images

[Bryan Kearney]

Alan Pevec wrote:
> 
> 
> On Fri, Nov 14, 2008 at 7:53 PM, Bryan Kearney <bkearney at redhat.com 
> <mailto:bkearney at redhat.com>> wrote:
> 
>     Perry Myers wrote:
> 
>         Perry Myers wrote:
>         2. Kickstart only contains primary disk, don't create data disk
>         until
>           appliance deployment. 
> 
> 
>         If option 2 can be simplified and automated by the
>         appliance-tools then this is not that big of a problem.
> 
> 
>     Ideally.. I could describe (2) in the virt-image.xml file and have
>     virt-image do it for me.
> 
> 
> virt-image XML has disk at use='scratch' which creates new empty disk image 
> during VM instantiation,
> but you still need ACE to mkfs, create mountpoint, fstab entry etc.


I was thinking along the same lines.. that if you have a disk marked 
"data" it would create a persistent disk at install. But, that would 
assume that the appliance defines it internally. Looking at the ovf vman 
spec[1] there is support for "empty" disks being sent, but no way to 
distinguish between scatch and data. This would mean we would need to 
pick a model for conversion (e.g. always assume data).

-- bk



[1] http://www.dmtf.org/standards/mgmt/vman/