Am 16.05.2018 um 21:26 hat Eric Blake geschrieben: > On 05/09/2018 11:26 AM, Kevin Wolf wrote: > > This adds a QMP event that is emitted whenever a job transitions from > > one status to another. For the event, a new qapi/job.json schema file is > > created which will contain all job-related definitions that aren't tied > > to the block layer. > > > > Signed-off-by: Kevin Wolf <kw...@redhat.com> > > --- > > > +++ b/qapi/job.json > > > +## > > +# @JOB_STATUS_CHANGE: > > +# > > +# Emitted when a job transitions to a different status. > > +# > > +# @id: The job identifier > > +# @status: The new job status > > +# > > +# Since: 2.13 > > +## > > +{ 'event': 'JOB_STATUS_CHANGE', > > + 'data': { 'id': 'str', > > + 'status': 'JobStatus' } } > > Is it worth also trying to list the old state that the transition came from? > But that's new compared to what block jobs are currently doing, so if we > can't come up with a strong reason to add that, I'm okay.
If a management tool needs this information (I don't see why), it just needs to keep track of the last state it had seen, no? Kevin