On 2016年02月05日 12:02, Bhandaru, Malini K wrote:
I agree with Daniel, keep the periods consistent 5 - 5 . Another thought, for such ephemeral/changing data, such as progress, why not save the information in the cache (and flush to database at a lower rate), and retrieve for display to active listeners/UI from the cache. Once complete or aborted, of course flush the cache.
hi MaliniIt's good idea to use cache to save the information while doing migration, but the problem is how can we access that cache while we use CLI (nova-api)? These information are generated from nova-compute node , there should be one method to sync them to nova-conductor(which means DB).
Also should we provide a "verbose flag", that is only capture progress information when requested? That is when a human user might be issuing the command from the cli or GUI tool.
I am +1 on this, yeah, some of other service may help. -- Best Regards, Eli(Li Yong)Qiao Intel OTC China
<<attachment: liyong_qiao.vcf>>
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
