Storage space is a concern; really?
If it really is, then keep X of them for some definition of X (days,
number, hours, other)? Offload the snapshot asynchronously if
snapshotting during requests is a problem.
We have the power! :)
Chris Friesen wrote:
On 08/01/2018 11:34 PM, Joshua Harlow wrote:
And I would be able to say request the explanation for a given request id
(historical even) so that analysis could be done post-change and
pre-change (say
I update the algorithm for selection) so that the effects of
alternations to
said decisions could be determined.
This would require storing a snapshot of all resources prior to
processing every request...seems like that could add overhead and
increase storage consumption.
Chris
__________________________________________________________________________
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
__________________________________________________________________________
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
