yahoo-eng-team team mailing list archive

[David Ripton <dripton@xxxxxxxxxx>]

Since we do comparisons on the hypervisor_version, we cannot change it
to a string unless we're willing to live with string compares.  Which
would cause regressions since "10" < "9".  So we would need "smart"
version number comparison code.  Too dangerous for a bugfix; we'd need a
blueprint instead.

** Changed in: nova
       Status: New => Invalid

** Changed in: nova
       Status: Invalid => Opinion

-- 
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/1207058

Title:
  hypervisor_version in the compute_nodes table needs to be a string

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  hypervisor_version reported by vmwareapi, powervm, hyperv and the fake
  driver all use strings as their "version number" and it would make
  supporting new hypervisors easier if the hypervisor_version in the
  compute_nodes table.

  Based on discussion here:
  * https://review.openstack.org/#/c/34685/4/nova/virt/vmwareapi/host.py

  Several hypervisors use version numbers like 1.0.0 and may not adhere
  to version numbers that convert to strings easily. It would facilitate
  support for alternate hypervisors if the column hypervisor_version
  could hold any version "number" string. Such as "1.0.0_beta1" for
  example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1207058/+subscriptions