Hi Nikolay - Is your concern that mistral.db.sqlalchemy.models.* and mistral.model.* will lead to confusion or something else?
IMHO as per your change model seems like the appropriate usage while what is stored in the DB is also a model. If we pick appropriate names to distinguish between nature of the objects we should be able to avoid any confusion and whether or not model appears in the module name should not matter much. Thanks, Manas On Mon, Mar 3, 2014 at 8:43 AM, Nikolay Makhotkin <nmakhot...@mirantis.com>wrote: > Hi, team! > > Please look at the commit . > > Module 'mistral/model' now is responsible for object model representation > which is used for accessing properties of actions, tasks etc. > > We have a name problem - looks like we should rename module > 'mistral/model' since we have DB models and they are absolutely different. > > > Thoughts? > > > Best Regards, > Nikolay > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
