Hi
@smooney@redhat.com , and
@Karl Kloppenborg
Thanks for your helps. I also have questions regarding to your suggestion as below:
@smooney@redhat.com
Did you mention about cinder-volume with LVM driver? I tested it before, but the performance does not meet the requirement cause of the transportation of data via iSCSI protocol and it hard to compare with direct attach via libvirt. Your second idea are using
flavor with ephemeral disk, right?
@Karl Kloppenborg
Your workaround suggestion looks good to me; I will search around for the accurate RabbitMQ event as you mentioned.
Best Regards
Sang.
From: Karl Kloppenborg <kkloppenborg@resetdata.com.au>
Sent: Wednesday, January 24, 2024 6:45 AM
To: smooney@redhat.com; Sang Tran Quoc <SangTQ8@fpt.com>; openstack-discuss@lists.openstack.org
Subject: Re: Mapping local SSD to virtual machine persistently
Hey guys,
One suggestion which might help you as a work around:
Libvirt regenerates the xml’s based on nova receiving events via the RabbitMQ event bus.
One option (which will require a bit of programming on your part) is to listen to the events that might impact the libvirt generation and execute the commands on your behalf.
This would necessitate knowing/storing that VM->Device mapping somewhere, i.e a database.
Thanks,
Karl.