On 02/04/2016 11:02 PM, Bhandaru, Malini K wrote:
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.
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 agree with you, Malini, on the above suggestion that there is some
doubt as to the value of saving this temporal data to the database.
Why not just have an on-demand model that simply routes the request for
progress information directly to the compute node and sends the progress
amount back directly to the nova-api service instead of going to the
database at all?
Another alternative would be to use a push model instead of a poll
model, but that would require a pretty significant change to the code...
Best,
-jay
__________________________________________________________________________
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
