Remove the column 'can_host' from the ResourceProvider table
Bug #1648197 reported by
Ed Leafe
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Ed Leafe |
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.
tags: | added: db |
Changed in nova: | |
status: | New → Triaged |
To post a comment you must log in.
I remain somewhat unconvinced that can_host or shared are necessary when we have resource classes. Doesn't VCPU mean 'can_host'?
Or I suppose the problem there is that in the world of NUMA VCPU is not always going to be a requested resource class for something destined for a compute-node? If that's the case that seems like a potential semantic problem that ought to resolved, rather than making a special case flag for compute- node/not- compute- node.