in ceilometer we have a bug regarding residual dump tables left after
migration: https://bugs.launchpad.net/ceilometer/+bug/1259724
basically, in a few prior migrations, when adding missing constraints, a
dump table was create to backup values which didn't fit into the new
constraints. i raised the initial bug because i believe there is very
little value to these tables as i would expect any administrator capturing
data of some importance would backup their data before any migration to
begin with. i noticed in Nova, they also clean up their dump tables but i
wanted to raise this on mailing list so that everyone is aware of the
issue before i add a patch which blows away these dump tables. :)
i'd be interested if anyone actually finds value in having these dump
tables persist just so we can see if your use case can be handle without
the tables.
for reference, the dump tables are created in:
https://github.com/openstack/ceilometer/blob/master/ceilometer/storage/sqlalchemy/migrate_repo/versions/012_add_missing_foreign_keys.py
https://github.com/openstack/ceilometer/blob/master/ceilometer/storage/sqlalchemy/migrate_repo/versions/027_remove_alarm_fk_constraints.py
cheers,
gordon chung
openstack, ibm software standards
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev