Hi All,
K8s resources Pod/RC/Service share same 'bay_uuid' which it gets from the Bay 'uuid' (which happens to be the primary key for Bay). Shouldn't it be a good idea to make pod/rc/service 'bay_uuid' be foreign key for Bay 'uuid'. Are there any cons in doing so ? Why was it done in this specific way initially ? Listing down some pros in doing so :- 1. It helps to give a clear indication whether a Bay exist or not; if the Pod/RC/Service 'bay_uuid' is a foreign key for Bay 'uuid'. 2. No additional lookup is necessary for the Bay table to check the existence of Bay. Nova already does so by [1]. Even other projects do follow the same pattern. - Vilobh [1] https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L352
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
