The initial set of configurable options that I'm looking at are:
Cobbler integration:
- a name for the virtual machine (should be unique)
- a notes section [1]
- a way of listing available system profiles or image profiles
- the number of CPUs to use [2]
- the amount of memory for the VM [2]
- a way of specifying a set of optional arguments for koan
- a field for setting the MAC address (must be unique)
Anybody see anything missing?
Questions:
- should we also include iptable configuration?
[1] - I like the idea of a maintenance log, but could just be a general
"this machine is for this purpose" text.
[2] - The value returned from Cobbler should be treated as the minimum value.
--
Darryl L. Pierce, Sr. Software Engineer
Red Hat, Inc. - http://www.redhat.com/
oVirt - Virtual Machine Management - http://www.ovirt.org/
"What do you care what other people think, Mr. Feynman?"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL:
<http://listman.redhat.com/archives/ovirt-devel/attachments/20080728/dc896f3c/attachment.sig>
On Mon, Jul 28, 2008 at 11:10:31AM -0400, Darryl L. Pierce wrote:> The initial set of configurable options that I'm looking at are: > > Cobbler integration: > - a name for the virtual machine (should be unique) > - a notes section [1] > - a way of listing available system profiles or image profiles > - the number of CPUs to use [2] > - the amount of memory for the VM [2] > - a way of specifying a set of optional arguments for koan > - a field for setting the MAC address (must be unique) Anybody see > anything missing? > > Questions: > - should we also include iptable configuration? > > [1] - I like the idea of a maintenance log, but could just be a general > "this machine is for this purpose" text. > [2] - The value returned from Cobbler should be treated as the minimum value. >Hey... This sounds very much like the "create VM" screen, where we already collect vcpus, VM name, and memory, and display MAC address and UUID. All we really need for Cobbler integration as far as the UI goes is a drop-down list of available profiles, added to the "create VM" screen. We don't use koan at all, so there's not much sense specifying arguments for it. Take care, --Hugh
Darryl L. Pierce
2008-Jul-28 15:38 UTC
[Ovirt-devel] Re: Virtual machine configuration screen
+++ Darryl L. Pierce [28/07/08 11:10 -0400]:> The initial set of configurable options that I'm looking at are: > > Cobbler integration:This was a little unclear. I meant this to be a description of what the VM configuration page should look like and is a result of the Cobbler integration work I'm doing currently. -- Darryl L. Pierce, Sr. Software Engineer Red Hat, Inc. - http://www.redhat.com/ oVirt - Virtual Machine Management - http://www.ovirt.org/ "What do you care what other people think, Mr. Feynman?" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: not available URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20080728/7e611c66/attachment.sig>
Darryl L. Pierce wrote:> The initial set of configurable options that I'm looking at are: > > Cobbler integration: > - a name for the virtual machine (should be unique) > - a notes section [1]We may want to make a small model change here. Right now, we have a single field, called 'description' in the model, but displayed as 'name'. We may want to keep description (for the notes field) but add an actual 'name' field. We're also not checking uniqueness -- but that's a more general comment -- we need a major overhaul of validation rules for model params.> - a way of listing available system profiles or image profilesIs this something we should keep a copy of in the PG database, or should we just grab a list of cobbler profiles when displaying the form to the user (and then store this as a string)?> - the number of CPUs to use [2] > - the amount of memory for the VM [2]These are already on the 'new VM' form.> - a way of specifying a set of optional arguments for koan > - a field for setting the MAC address (must be unique) Anybody see > anything missing? >We have a mac address for each VM now -- it's auto-generated with a random value, but the user can change it. The whole MAC thing will have to be reworked if we end up supporting multiple virtual NICS for VMs. Scott
On Mon, 2008-07-28 at 11:10 -0400, Darryl L. Pierce wrote:> The initial set of configurable options that I'm looking at are: > > Cobbler integration: > - a name for the virtual machine (should be unique) > - a notes section [1] > - a way of listing available system profiles or image profilesYou should also have a quick look at Genome[1] - I don't think it's quite ready for prime time, but ultimately that's the kind of provisioning solution you want to integrate with. From the oVirt side, it shouldn't require much more metadata than cobbler (essentially, just a list of puppet classes on top of Cobler metadata).> - the number of CPUs to use [2] > - the amount of memory for the VM [2] > - a way of specifying a set of optional arguments for koanIt'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) * The kickstart to use (again, expressed as a cobbler distro/profile) plus any template variables needed for that kickstart Any data that is needed to actually construct the VM should be independent of cobbler - from a user's point of view, cobbler only comes into play when the VM is at the point where a kernel is booted.> Questions: > - should we also include iptable configuration?Do you mean iptables on the host ? If so, I don't think that is really related to cobbler integraton, more around 'OVirt networking'. David [1] http://genome.et.redhat.com/index.php