Open Stack

Hi Patryk,

Thanks a lot for the link and sorry for the late answer!

As stated in my previous email, this is not going to work on our side of
things as our security process prohibits us from modifying the Original
ISO. Not that I CAN'T do it as I obviously have the hand on the whole image
creation, just that if I'm not respecting the workflow those images won't
pass the qualification gate.

What really astonish me is that KVM is CDRom IDE HW Bus aware and able to
mount multiple of them for a same instance, Nova itself knows about those
specific HW bus too as you can actually specify it on the image metadata,
what's really missing in my process for now is the ability to let nova
spawn a VM with both ISO and VIRTIO drivers as CDRom devices.

I'm really wondering why we can't specify any additional HW resources to
nova at spawn time (from Horizon and CLI) except using native nova client
such as instructed in here: https://access.redhat.com/solutions/1225473 or
did I miss something?

Thanks a lot for your answer!

Le mar. 30 nov. 2021 à 00:13, Patryk Jakuszew <patryk.jakuszew at gmail.com> a
écrit :

> On Tue, 30 Nov 2021 at 01:11, Gaël THEROND <gael.therond at bitswalk.com>
> wrote:
> >
> > Starting from an unaltered Microsoft originated ISO image is a mandatory
> requirement for this project (Because of security constraints that I can’t
> have any impact on).
> >
>
> Does that mean you cannot alter the original image? There are methods
> for inserting the virtio drivers into the installation media, but that
> will require generating a new installer ISO out of the modified files.
>
> This article seems to be describing the procedure correctly:
>
> https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000bt28CAA
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20211202/0ce29c69/attachment.htm>