[Ovirt-devel] Virtual machine configuration screen

[David Lutterkort]

On Mon, 2008-07-28 at 18:58 -0400, Perry N. Myers wrote:
> David Lutterkort wrote:
> > It's probably better to specify exactly which options need to be
> > supported. Ultimately, the only bits of metadata that integrating with
> > cobbler adds should be
> > 
> >       * The kernel/initrd to boot into (though the user might think of
> >         this as selecting a cobbler distro/profile)
> 
> This is not really applicable in the FV case as we're just provisioning 
> via PXE and image (disk image and CDROM image).  But at some point when we 
> get support for dom0 as a type of managed node then PV provisioning may 
> come into play.  But I think for now we should focus on the FV 
> provisioning types.

I was thinking in terms of the bits that ultimately wind up on the
client - you are right, for FV PXE boot through cobbler, oVirt only
needs to know the desired profile (which implies kernel/initrd and
kickstart)

> Yeah, a cobbler profile includes the kickstart to use.  So no need to 
> split out kickstart as an option in the provisioning UI in oVirt.  But the 
> template variables idea is interesting...  I'd argue that first pass lets 
> get this implemented without template vars and then second pass we can add 
> that in.

Agreed.

David