Reviewed: https://review.openstack.org/461494 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fcfe28192eaa63d2ca000d38bc435a5e662ad8f5 Submitter: Jenkins Branch: master
commit fcfe28192eaa63d2ca000d38bc435a5e662ad8f5 Author: EdLeafe <e...@leafe.com> Date: Mon May 1 15:32:06 2017 +0000 Remove the can_host column Originally it was felt that we would need this column to distinguish between compute nodes and non-compute providers. With the advent of traits, though, this column is no longer used or needed. Closes-Bug: #1648197 Change-Id: I614db98727f4737deb6728ee874ab0f68024ebe5 ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1648197 Title: Remove the column 'can_host' from the ResourceProvider table Status in OpenStack Compute (nova): Fix Released Bug description: There is a column in the ResourceProvider table named 'can_host'. It is used to distinguish compute nodes (can_host=1) from shared storage providers (can_host=0) for queries that need to distinguish those different types of providers. However, the name is very Nova-specific, and when the Placement engine is extended to support a variety of resource allocation requirements, it will probably cause confusion. After a discussion on IRC, we decided to change the name to "shared", and reverse any logic using can_host, since can_host=1 will now be shared=0, and vice-versa. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1648197/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp