qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
	Leonardo Bras <leobras@redhat.com>,
	Fabiano Rosas <farosas@suse.de>
Subject: [PATCH v4 0/4] Migration documentation
Date: Wed, 18 Oct 2023 13:28:23 +0200	[thread overview]
Message-ID: <20231018112827.1325-1-quintela@redhat.com> (raw)

Hi

on this v4:
- Add ..contents
- Address all comments
- Create a new Backwards Compatibility section at the end of the file for this.

Please review.

Thanks, Juan.

Continuing on my saga to not have a pointer about how migration
works/should work, this are the doc for the long mails that I had to do last week:

1 - Document how backwards compatibility is supposed to work (that is
    what it was on v1 and v2)

2 - Document how to handle features that depend of things outside of qemu
    a.k.a. we make this a libvirt/management app problem.

3 - Document how we are supposed to fix backwards compatibility
    brokenness.

You can see that I was able to find commits on tree to illustrate 1
and 3.  The problem for 2 appeared from a discussion with Avihai about
future vfio devices.  Do anyone have a good idea about a commit
already on tree to document it?

Please review.

Later, Juan.

Juan Quintela (4):
  migration/doc: Add contents
  migration/doc: Add documentation for backwards compatiblity
  migration/doc: How to migrate when hosts have different features
  migration/doc: We broke backwards compatibility

 docs/devel/migration.rst | 520 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 520 insertions(+)

-- 
2.41.0



             reply	other threads:[~2023-10-18 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 11:28 Juan Quintela [this message]
2023-10-18 11:28 ` [PATCH v4 1/4] migration/doc: Add contents Juan Quintela
2023-10-19 21:16   ` Fabiano Rosas
2023-10-18 11:28 ` [PATCH v4 2/4] migration/doc: Add documentation for backwards compatiblity Juan Quintela
2023-10-18 11:28 ` [PATCH v4 3/4] migration/doc: How to migrate when hosts have different features Juan Quintela
2023-10-19 21:15   ` Fabiano Rosas
2023-10-18 11:28 ` [PATCH v4 4/4] migration/doc: We broke backwards compatibility Juan Quintela

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=20231018112827.1325-1-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=farosas@suse.de \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).