[Ovirt-devel] Details about pending cobbler image support & ovirt integration

[Bryan Kearney]

David Lutterkort wrote:
> On Wed, 2008-07-09 at 09:28 -0400, Michael DeHaan wrote:
>> Images are the new object.   We want cobbler to track them like other 
>> objects.
>>
>>     # cobbler image add --name=QuestionableRemondInstallISO 
>> --file=/mnt/nfs/blah/foo.img
> 
> Are images also meant for bare-metal installs or only for VM installs ?
> 
>> After that, we also teach "cobbler image add" to track images that can 
>> be fed to virt-image, AKA virt disk images.   This will have a similar 
>> syntax, most likely...
>>
>> # cobbler image add --name=MysteryOS --file=/mnt/nfs/blah/foo.img 
>> --image-type=blah [--virt-ram=] [--virt-disk=] [etc]
>>
>> The --virt parameters will work basically as they do with cobbler 
>> profiles today.
> 
> It would be much simpler for VM images to tell cobbler to add an
> image.xml; all the parameters above are listed in that, and adding a VM
> image to a cobbler server would be as simple as
>         
>         # cobbler image add /foo/bar/image.xml
>         
> and koan would basically take the same command line args as virt-image;
> the only thing on top of what virt-image does is that koan would have to
> make the actual disk files available on the local host.
> 
> There's one small wrinkle: when you instantiate from an image, you can
> treat that image either as an immutable template (in which case you'd
> have to copy the disk files) or as the image for a specific VM (in which
> case you'd directly use the disk files to back the VM)

I would assume that you are using cobbler to provisiion.. so it is more 
of the former. Given Michaels  description abovethe image is a 
combination of distro+profile.. not system.