yahoo-eng-team team mailing list archive

[Ed Leafe <ed@xxxxxxxxx>]

Public bug reported:

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.

** Affects: nova
     Importance: Low
     Assignee: Ed Leafe (ed-leafe)
         Status: Triaged


** Tags: db placement

-- 
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:
  ResourceProvider column 'can_host' is too Nova-specific

Status in OpenStack Compute (nova):
  Triaged

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