From: Anthony Liguori <aliguori@us.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration
Date: Tue, 15 Nov 2011 07:50:03 -0600 [thread overview]
Message-ID: <4EC26E0B.9000408@us.ibm.com> (raw)
In-Reply-To: <4EC232A1.9080703@redhat.com>
On 11/15/2011 03:36 AM, Kevin Wolf wrote:
> Am 14.11.2011 22:08, schrieb Anthony Liguori:
>> On 11/14/2011 11:40 AM, Juan Quintela wrote:
>>> Anthony Liguori<aliguori@us.ibm.com> wrote:
>>>> I think this is an accurate reflection of the state of migration today. This
>>>> is the second release in a row where we're scrambling to fix a critical issue
>>>> in migration.
>>>
>>> We need to make our mind about it.
>>
>> Ultimately, we need to make migration a priority. That's what I'm trying to do
>> here.
>
> When you make everything a priority, being a priority doesn't have much
> of a meaning any more. Our current priorities are changing the entire
> device model, the monitor, migration, turning the block layer upside
> down - what's left? Okay, maybe vvfat and slirp.
Well, think of it as employment insurance :-)
>
>> The first step is to be open about the state of migration today. I personally
>> don't have the bandwidth to invest a lot of effort in migration, but I can
>> invest time in trying to find more people to work on migration, and help put
>> together a proper roadmap.
>>
>> We need to outline and document what we support and what we don't support. We
>> need to invest in a test infrastructure. We need a roadmap that we can
>> reasonably execute on. In short, we need to turn migration into a first class
>> subsystem.
>>
>> It's not about any single person or any single patch series. It's about
>> deciding that migration is an important feature and deserves more focus and
>> attention.
>
> I don't doubt that everyone will agree with this. The harder question is
> who should concentrate less on which other feature to have time to spend
> for migration.
I don't think it's a question of trading patches in one subsystem for patches in
another subsystem.
I think it's more about having a planned, concerted effort, that systematically
tackles the problems we're facing in migration.
By spending more time planning, it makes it much easier for people to
contribute. There's a lot of interest in migration. If we made it easier to
participate in improving it, I'm sure we would attract at least a few more
people to working on it.
Regards,
Anthony Liguori
>
> Kevin
>
prev parent reply other threads:[~2011-11-15 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 16:07 [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration Anthony Liguori
2011-11-14 17:40 ` Juan Quintela
2011-11-14 21:08 ` Anthony Liguori
2011-11-15 8:32 ` Stefan Hajnoczi
2011-11-15 13:04 ` Avi Kivity
2011-11-15 13:45 ` Anthony Liguori
2011-11-15 9:36 ` Kevin Wolf
2011-11-15 13:50 ` Anthony Liguori [this message]
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=4EC26E0B.9000408@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).