On Mon, 14 Jun 2010 09:35:52 -0500 Anthony Liguori <aligu...@linux.vnet.ibm.com> wrote:
> On 06/14/2010 09:24 AM, Luiz Capitulino wrote: > > On Mon, 14 Jun 2010 08:58:19 -0500 > > Anthony Liguori<aligu...@linux.vnet.ibm.com> wrote: > > > > > >> For 0.13, we need to focus on introducing the least disruptive change > >> that addresses the fundamental requirement--allow clients to avoid a > >> polling loop for determining when migration ends. Having a single event > >> with no payload is an extremely simple change. > >> > > Agreed. > > > > Actually, I'm slightly against introducing the done event too. While the > > polling is undesired, I don't think that having an event only for a release > > is worth it. > > > > I don't think we can realistically remove it. In my mind, what > deprecate means with respect to QMP is that we never add additional > features to the deprecated commands. Oh, by 'only for a release' I meant 'useful only for a release', ie. I didn't mean we would remove it but that it will only be useful for 0.13. > Right now, 'migrate', 'info migrate', and MIGRATE_DONE do not provide > very rich error reporting. They really just provide a boolean > failed/succeeded. > > For 0.14, we'll have to introduce a 'migrate2' command and deprecate the > old 'migrate' command. 'migrate2' will provide rich error reporting and > all new features will be added to 'migrate2'. > > BTW, I lack any kind of naming creativity so 'migrate2' is not > necessarily what it ought to be called. We can have a contest.
