yahoo-eng-team team mailing list archive

[Rafi Khardalian <1275311@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We currently do not enable the "bootmenu" option within Libvirt.  It
would be beneficial to do so, to allow for some more flexibility when
installing a new OS from ISO.  Having the bootmenu available would allow
for the following:

1. Upload ISO image to Glance.
2. Upload "empty" RAW image to Glance.
3. Create a new Cinder volume, populating it with the ISO from #1.
4. Create a new instance, using the empty RAW from #2.
5. Attach the CInder volume from #3.

At this point, the instance has 2 disks attached: the root disk (vda)
and volume (vdb).  In this case, we want to boot vdb, so that we can
utilize the ISO to install an OS on vda.  There is currently no way to
do this, short of passing block-device-mapping, which is not the same
end result.  Enabling the bootmenu would prompt the user to hit F12 and
select the desired boot device (vdb in this case).

This is an extremely simple change which provides a non-external option
for creating Nova compatible images.

** Affects: nova
     Importance: Undecided
     Assignee: Rafi Khardalian (rkhardalian)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Rafi Khardalian (rkhardalian)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1275311

Title:
  Libvirt BIOS bootmenu should be enabled

Status in OpenStack Compute (Nova):
  New

Bug description:
  We currently do not enable the "bootmenu" option within Libvirt.  It
  would be beneficial to do so, to allow for some more flexibility when
  installing a new OS from ISO.  Having the bootmenu available would
  allow for the following:

  1. Upload ISO image to Glance.
  2. Upload "empty" RAW image to Glance.
  3. Create a new Cinder volume, populating it with the ISO from #1.
  4. Create a new instance, using the empty RAW from #2.
  5. Attach the CInder volume from #3.

  At this point, the instance has 2 disks attached: the root disk (vda)
  and volume (vdb).  In this case, we want to boot vdb, so that we can
  utilize the ISO to install an OS on vda.  There is currently no way to
  do this, short of passing block-device-mapping, which is not the same
  end result.  Enabling the bootmenu would prompt the user to hit F12
  and select the desired boot device (vdb in this case).

  This is an extremely simple change which provides a non-external
  option for creating Nova compatible images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1275311/+subscriptions