Wrong "can_host" field of compute node resource providers

[Yingxin]

The "can_host" field of compute node records should be 1. However, according to the latest placement implementation, it is 0.

mysql> select * from resource_providers;
+---------------------+---------------------+----+--------------------------------------+-----------------+------------+----------+
| created_at | updated_at | id | uuid | name | generation | can_host |
+---------------------+---------------------+----+--------------------------------------+-----------------+------------+----------+
| 2016-09-12 08:54:19 | 2016-09-12 09:33:41 | 1 | 508f3973-8e1a-4241-afec-ee3e21be0611 | host1 | 80 | 0 |
+---------------------+---------------------+----+--------------------------------------+-------+------------+----------+
1 row in set (0.00 sec)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/369218

[Chris Dent (cdent)]

Jay Pipes, Dan Smith and others decided in a hangout that the can_host file is not going to be used and will remain as a vestigial column in the database tables.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Yingxin Cheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/369218
Reason: No longer needed, because the usage of can_host field is still undetermined.