All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: vitalif@yourcmc.ru
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Can I contribute Vitastor block driver? Or maybe introduce a QAPI plugin system?
Date: Wed, 26 Mar 2025 10:38:11 +0100	[thread overview]
Message-ID: <871pukb08s.fsf@pond.sub.org> (raw)
In-Reply-To: <bd5c6126f8c345b1eeac617d4023fa58@yourcmc.ru> (vitalif@yourcmc.ru's message of "Sat, 22 Mar 2025 17:13:00 +0000")

I'm not speaking for the QEMU project.  I hope to be helpful anyway.  I
am the QAPI maintainer, so my thoughts carry a bit more weight there.

I understand your block driver depends on your libvitastor_client
library.

Dependencies that aren't available on at least one supported build
platform (and thus covered by CI) are problematic.  For Linux,
"available" generally means "provided by the distribution".  I doubt
there's a way around getting your library packaged by distributions.

The QAPI schema is (for better or worse) fixed at compile time by
design.  Changing that would be a major undertaking.  Whether the
benefits could justify the costs and risks seems rather doubtful to me.

In my experience, the project invites contributions, not out-of-tree
extensions.  The latter require external interfaces, which can only be
harder to maintain than internal ones.  There's also the risk of abuse
to circumvent the GPL (I have absolutely no reason to assume you'd try
that!).



  reply	other threads:[~2025-03-26  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-22 17:13 Can I contribute Vitastor block driver? Or maybe introduce a QAPI plugin system? vitalif
2025-03-26  9:38 ` Markus Armbruster [this message]
2025-03-26 13:53   ` Stefan Hajnoczi
2025-04-05 16:37   ` vitalif

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871pukb08s.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vitalif@yourcmc.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.