Tom Barron ca0799125f Remove confusing DB deprecation messages ... When share instances were introduced a number of fields were moved in the database model to the underlying share instance and proxied back to the share in order to maintain compatability with APIs that assume these to belong to the share. A deprecation warning was added for these. The warning spams the API log and confuses end users because it sounds like they or their client should make a change to get rid of them and that cannot actually be done. The API would have to change to expose share instances to end users rather than just administrators and that is not something that we plan to do. Remove these confusing warnings. Closes-Bug: #1776947 Change-Id: I95e99b26f416bbf25cfd1c8f7295f3ba6220efb3 (cherry picked from commit 8bdbbd86ae) (cherry picked from commit 0c182bca86)		2018-06-23 11:15:35 +00:00
..
migrations	Add 'consistent_snapshot_support' attr to 'share_groups' DB model	2017-02-07 17:14:42 +00:00
sqlalchemy	Remove confusing DB deprecation messages	2018-06-23 11:15:35 +00:00
__init__.py	Remove vim headers	2014-10-06 15:00:27 +02:00
api.py	Fix multiple export locations during migration	2017-02-01 16:59:54 -02:00
base.py	Reuse 'periodic_task' from oslo_service	2015-07-20 19:38:19 +03:00
migration.py	Remove vim headers	2014-10-06 15:00:27 +02:00