Red Hat Bugzilla – Bug 887986
RFE: Configurable hardware models for disk/nic based manual user input
Last modified: 2016-04-26 12:57:29 EDT
+++ This bug was initially created as a clone of Bug #887968 +++
This bug is a clone of bug # 865345. That bug will be focused on using tools like libguestfs/libosinfo to select the proper drivers for each guest in an automated fashion.
This bug will be a simpler method, providing users the ability to manually select driver types on a per guest basis via API calls/parameters
Users should be able to choose between virtio for NIC/disk and options like e1000/rtl and IDE/SCSI
Not sure if other options should be exposed in addition to those, so add'l comments welcome on those lists.
What changes do we want for this in Horizon?
I don't really know what Horizon provides in terms of UI for uploading disk images yet. If it already has UI for setting arbitrary glance metadata properties, then no work is required. If not, then either we need some kind of generic UI for setting arbitrary properties, or we create specific UI tailored towards each individual property we care about. I don't really have an opinion on the right approach here.
There is no UI to upload disk images yet.
we have a UI to set the name (for reference), disk format, image location (to be copied from), minimum RAM and minimum disk and a checkbox to specify, if this is a public image.
Well I guess you could add further UI to set the disk bus, cdrom bus & nic model then.
Is there some info about what has been added?
Currently being worked on upstream.
No Metadata/property is avaliable on Horizon. User can only create new one
It looks like this blueprint was overridden during the same Juno cycle by https://blueprints.launchpad.net/horizon/+spec/glaance-metadata-flavors , see https://review.openstack.org/#/c/104956/ which includes in the review message "This patch also removes Edit Image Custom Properties screen as new widget provides the same functionality." That other blueprint seems to be tracked in BZ in bug 1125093 so we probably should close this one and track the testing over there instead.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.