yahoo-eng-team team mailing list archive

[Nikola Đipanov <ndipanov@xxxxxxxxxx>]

Public bug reported:

The following change adds an online data migration to the PciDevice
object.

https://review.openstack.org/#/c/249015/ (50355c45)

When we do that we normally want to couple it together with a script
that will allow operators to run the migration code even for rows that
do not get accessed and saved during normal operation, as we normally
drop any compatibility code in the release following the change. This is
normally done using a nova-manage script, an example of which can be
seen in the following commit:

https://review.openstack.org/#/c/135067/

The above patch did not add such a script and so does not provide admins
with any tools to make sure their data is updated for the N release
where we expect the data to be migrated as per our current upgrade
policy (http://docs.openstack.org/developer/nova/upgrade.html#migration-
policy)

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  mitaka pci_request object needs a migration script for an online data
  migration

Status in OpenStack Compute (nova):
  New

Bug description:
  The following change adds an online data migration to the PciDevice
  object.

  https://review.openstack.org/#/c/249015/ (50355c45)

  When we do that we normally want to couple it together with a script
  that will allow operators to run the migration code even for rows that
  do not get accessed and saved during normal operation, as we normally
  drop any compatibility code in the release following the change. This
  is normally done using a nova-manage script, an example of which can
  be seen in the following commit:

  https://review.openstack.org/#/c/135067/

  The above patch did not add such a script and so does not provide
  admins with any tools to make sure their data is updated for the N
  release where we expect the data to be migrated as per our current
  upgrade policy (http://docs.openstack.org/developer/nova/upgrade.html
  #migration-policy)

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