Description of problem: Raising a RFE as a customer would like to have "virtio-scsi multiqueue" is exposed through OpenStack services such as Nova for virtual machine instances. Customer is looking for improved I/O performance from our instances in OpenStack. For our non-openstack instances on libivrt, we use virtio-scsi multiqueue for improved I/O performance and would like this option available in OpenStack and like to have this feature included to help with performance. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: - If not supported for RHOSP 13 then Can this be treated as an RFE for a future release ?
also related to this when looking to enable this feature we should consider it holistically with support for iothreads. previous advice from the virt team during the os 13/16 dev cycle was to not enable iothread in nova from some preliminarly discsusion i have had in the last 24 hours it seams like that recomendation is changing. https://www.qemu.org/2021/01/19/virtio-blk-scsi-configuration/ was recently published corving the topic of virtio blk an scsi configuration with a followup expected to cover io treads. when we evaulate this feature for 18 we should try an incoperate the latest best practices by reaching out to the autors of that serise and likely start a thread upstream on qemu-devel or downstream on virt-devel including stefanha we have previously discussed enabling multi queue in the upstream nova team meeting and agree to file an minimal spec when we plan to work on it so we could combine the two feature in that one spec and track it with this singel bz.
Starting with the Antelope upstream release, DFG:Compute is tracking its feature backlog in Jira. This feature request has been migrated to DFG:Compute’s new Jira backlog. The Jira tracker for this feature request can be found below. At the time of this writing, only Red Hat associates have access to the Jira tracker, but we are actively working on changing that as more and more of the OSP organization uses Jira for more things. https://issues.redhat.com/browse/OSP-1601