[openstack-dev] Should Cinder have a volume_action table to track changes on a Volume?

Thank for the input I will head in that direction. >Cinder already emits events on all volume actions, and there are a >few projects that do various things with this info (e.g. stacktach). > What do you think the advantages of doing this inside cinder would be? On 30 December 2015 at

Re: [openstack-dev] Should Cinder have a volume_action table to track changes on a Volume?

On Wed, Dec 30, 2015 at 7:54 AM, SCHVENINGER, DOUGLAS P wrote: > I was looking into a support issue and noticed that Nova has an instance > and instance_action table. I was wondering if this is something that cinder > would consider adding a volume_action table to track changes

[openstack-dev] Should Cinder have a volume_action table to track changes on a Volume?

I was looking into a support issue and noticed that Nova has an instance and instance_action table. I was wondering if this is something that cinder would consider adding a volume_action table to track changes to a volume? I looked in the specs and I could not see anything like this. Has this

Re: [openstack-dev] Should Cinder have a volume_action table to track changes on a Volume?

Cinder already emits events on all volume actions, and there are a few projects that do various things with this info (e.g. stacktach). What do you think the advantages of doing this inside cinder would be? On 30 December 2015 at 16:54, SCHVENINGER, DOUGLAS P wrote: > I was