Re: [libvirt] New Feature: Intel MKTME Support
On Mon, Mar 04, 2019 at 07:54:30PM +0000, Mohammed, Karimullah wrote:
Hi Daniel,
QEMU/KVM work is in process of completion and would be published soon for
the community approval(somewhere in March). We are working closely with
development team of KVM/QEMU. Meanwhile, we wanted to start the process
in Libvirt community.
We will submit the work status of QEMU/KVM as they are available.
We are new to the Libvirt community and wanted to know more about the
Libvirt design approval process, and wanted to kick start our work
Question we have are
1. What is the blueprint or design template for a feature approval?.
2. Procedure and requirements for design and code approval.
There's no formal process mandated for libvirt. Either people just send
code patches directly, or for more complex features like this, start off
with a mailing list discussion about design decisions before writing
patches. Libvirt releases once a month so there's no critical deadlines
you need to rush to meet from upstream POV - they'll merge in whatever
release is next once the code has passed review. For complex code it
is common to post several versions adapting to review comments.
In terms of merging code, if it depends on QEMU, then we require that
the QEMU impl is merged before the libvirt impl is merged. We'd encourage
you to develop & publish libvirt patches before QEMU work is finalized.
This helps demonstrate that the QEMU impl is a good match for what libvirt
needs.
3. we wanted to use Libvirt MKTME in Openstack, what are the
requirements?
This is probably more a question for the OpenStack community to answer.
The goal with Libvirt is to expose the feature in XML and/or API in a
way that is suitable for any mgmt application.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|