Open Stack

Hi all,

Is there a policy regarding use of _extra_specs for supplying the virt
layer with information that it requires to start an instance? I ask because
right now, _extra_specs is not getting passed with the $instance object to
driver.spawn(), but IMHO the baremetal driver should be utilizing this. If
it's OK to do this, I will propose that patch.


A little background -- baremetal deployment process is a two (or more) step
process.
1. PXE boot the hw into a "deploy" kernel+ramdisk. This is used to write
the user-specified image onto the local disks.
2. hw restarts, and PXE boots into the kernel+ramdisk which belong to the
user-specified image.

(*) there could be other steps chained into this, such as hw discovery,
burn-in, etc, but that's ancillary to the question here.

For baremetal, a flavor represents a specific set of hardware capabilities
(how much physical ram, cpu, disk, etc). The deploy k+r used in step 1 is
likely to be hardware specific, eg. dependent upon CPU arch, any specific
network drivers that need to be loaded, and so on. Thus, it seems logical
to specify it on the flavor extra_specs as opposed to the current
approaches, both of which I see problems with: a) nova config option, b)
image metadata.

Regards,
Devananda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121114/b73469ca/attachment.html>