I have gone thru the Heat Database and found the drawbacks in the existing model as listed below. Could you review and add anything missing here. Thanks.
Heat Database model is having following drawbacks: 1. Duplicate information 2. Incomplete naming of columns 3. Inconsistency in the identifiers (id) and deleted_at columns across the tables 4. resource table is specific to nova and make it generic 5. Pre-defined constants are not using enum. And the section provided below describes these problem on table vice. Stack Duplicate info Tenant & stack_user_project_id Credentials_id & username , owner_id. Tenant is also part of user_creds and Stack always has credentials_id, so what is the need of having tenant info in stack table and in stack table only the credentials_id is sufficient. Status & action should be enum of predefined status User_creads correct the spelling in Truststore_id Resource Status & action should be enum of predefined status Rsrc_metadata - make full name resource_metadata Why only nova_instance column how about for other services like cinder, glance resource, could be renamed to be generic enough?? Watch_rule Last_evaluated -> append _at State should be an enum Event Why uuid and id both used? Resource_action is being used in both event and resource table, so it should be moved to common table Resource_status should be any enum Regards Kanagaraj M
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
