@Eric Harney,
I read up the history of this bug, looked at the prev patches.
IIUC, overloading 'progress' field isn't a good idea, so the recent work to introduce new fields in Nova
(See https://review.openstack.org/#/c/172813/) should address the overloading 'progress' field part.
But we still need to have a loop on the Cinder side with _some_ timeout as we wouldn't know
if the Nova/Compute node crashed/stopped responding for some reason, so we don't hang forever on the Cinder side
Do you intend to have some mechanism wherein we wouldn't need a loop on the Cinder side ?
IIUC thats only possible if Nova sends _real_ progress data for the blockjob. Do you have any other solution in mind ?
@Eric Harney,
I read up the history of this bug, looked at the prev patches.
IIUC, overloading 'progress' field isn't a good idea, so the recent work to introduce new fields in Nova /review. openstack. org/#/c/ 172813/) should address the overloading 'progress' field part.
(See https:/
But we still need to have a loop on the Cinder side with _some_ timeout as we wouldn't know
if the Nova/Compute node crashed/stopped responding for some reason, so we don't hang forever on the Cinder side
Do you intend to have some mechanism wherein we wouldn't need a loop on the Cinder side ?
IIUC thats only possible if Nova sends _real_ progress data for the blockjob. Do you have any other solution in mind ?