Trove - Timestamp Consistency Across All Bookkeeping Tables

[Auston McReynolds]

Filed as a result of https://review.openstack.org/#/c/45146/

In short, some tables have created_at+updated_at, some just have created_at, others have updated vs. updated_at, etc.

All tables should be assessed for altering to provide some level of consistency across the application. Also consider converting some single-row-updates to multi-row-inserts (RootHistory)

[Ilya Sviridov (isviridov)]

Similar to https://blueprints.launchpad.net/trove/+spec/instance-audit-fields

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/368867

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/368990

[OpenStack Infra (hudson-openstack)]

Change abandoned by Samuel Pilla (<email address hidden>) on branch: master
Review: https://review.openstack.org/368867
Reason: Replaced with https://review.openstack.org/#/c/368990/

[Amrith Kumar (amrith)]

On the whole, I find this bug to be something that generates too much churn for the minimal (if any) benefit that it brings. I'm inclined to ignore any changes related to this bug; I intend to mark the bug as such.

[Amrith Kumar (amrith)]

Sorry Sam

[OpenStack Infra (hudson-openstack)]

Change abandoned by amrith (<email address hidden>) on branch: master
Review: https://review.openstack.org/368990
Reason: per review comments