<div dir="ltr"><div class="gmail_extra"><div class="gmail_extra">Useful information.</div><div>Thank you Gibi.<br></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">BR</div><div class="gmail_extra">Shaohe Feng.. </div><div class="gmail_extra"><br><div class="gmail_quote">2015-11-26 21:29 GMT+08:00 Balázs Gibizer <span dir="ltr"><<a href="mailto:balazs.gibizer@ericsson.com" target="_blank">balazs.gibizer@ericsson.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">> -----Original Message-----<br>
> From: Paul Carlton [mailto:<a href="mailto:paul.carlton2@hpe.com">paul.carlton2@hpe.com</a>]<br>
> Sent: November 26, 2015 12:11<br>
> On 26/11/15 10:48, 少合冯 wrote:<br>
><br>
><br>
> Now, we are agree on getting more migration status details<br>
> info are useful.<br>
><br>
> But How do we get them?<br>
> By REST API or Notification?<br>
><br>
><br>
> IF by API, does the "time_elapsed" is needed?<br>
><br>
> For there is a "created_at" field.<br>
><br>
> But IMO, it is base on the time of the conductor server?<br>
> The time_elapsed can get from libvirt, which from the<br>
> hypervisor.<br>
> Usually, there are ntp-server in the cloud. and we can get the<br>
> time_elapsed by "created_at".<br>
> but not sure there will be the case:<br>
> the time of hypervisor and conductor server host are out of<br>
> sync?<br>
><br>
> Why not both. Just update the _monitor_live_migration method in the<br>
> libvirt driver (and any similar functions in other drivers if they exist) so it<br>
> updates the migration object and also sends notification events. These<br>
> don't have to be at 5 second intervals, although I think that is about right for<br>
> the migration object update. Notification messages could be once event 30<br>
> seconds or so.<br>
><br>
> Operators can monitor the progress via the API and orchestration utilities to<br>
> consume the notification messages (and/or use API).<br>
> This will enable them to identify migration operations that are not making<br>
> good progress and take actions to address the issue.<br>
><br>
> The created_at and updated_at fields of the migration object should be<br>
> sufficient to allow the caller to work out how long the migration has been<br>
> running for (or how long it took in the case of a completed migration).<br>
><br>
> Notification payload can include the created_at field or not. I'd say not.<br>
> There will be a notification message generated when a migration starts so<br>
> subsequent progress messages don't need it, if the consumer wants the<br>
> complete picture they can call the API.<br>
<br>
<br>
</div></div>As a side note if you are planning to add a new notification please consider<br>
aligning with the ongoing effort to make the notification payloads versioned. [1]<br>
Cheers,<br>
Gibi<br>
<br>
[1] <a href="https://blueprints.launchpad.net/nova/+spec/versioned-notification-api" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/nova/+spec/versioned-notification-api</a><br>
<div class=""><div class="h5">><br>
><br>
><br>
> --<br>
> Paul Carlton<br>
> Software Engineer<br>
> Cloud Services<br>
> Hewlett Packard<br>
> BUK03:T242<br>
> Longdown Avenue<br>
> Stoke Gifford<br>
> Bristol BS34 8QZ<br>
><br>
> Mobile: <a href="tel:%2B44%20%280%297768%20994283" value="+447768994283">+44 (0)7768 994283</a><br>
> Email: mailto:<a href="mailto:paul.carlton2@hpe.com">paul.carlton2@hpe.com</a><br>
> Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12<br>
> 1HN Registered No: 690597 England.<br>
> The contents of this message and any attachments to it are confidential and<br>
> may be legally privileged. If you have received this message in error, you<br>
> should delete it from your system immediately and advise the sender. To any<br>
> recipient of this message within HP, unless otherwise stated you should<br>
> consider this message and attachments as "HP CONFIDENTIAL".<br>
<br>
</div></div></blockquote></div><br></div></div>