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 16:54, SCHVENINGER, DOUGLAS P <ds6901 at att.com<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>> 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 to a volume? > > I looked in the specs and I could not see anything like this. > > Has this been talked about before? > > Does this sound like something cinder would like to add? > > > > Doug Schveninger > > Principal Technical Architect > > AIC - AT&T Integrated Cloud > > *AT&T* Services, Inc. > > *Rethink Possible* > > > > Email: ds6901 at > att.com<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at > lists.openstack.org<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>?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
