← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1543562] Re: mitaka pci_request object needs a migration script for an online data migration

 

Reviewed:  https://review.openstack.org/278079
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0970f2a90016c09b86e34a53c2b8734a68a6f917
Submitter: Jenkins
Branch:    master

commit 0970f2a90016c09b86e34a53c2b8734a68a6f917
Author: Nikola Dipanov <ndipanov@xxxxxxxxxx>
Date:   Fri Feb 12 21:40:47 2016 +0000

    nova-manage: Declare a PciDevice online migration script
    
    We want to make sure there is a way for operators to migrate all PciDevice
    records to the new format. The original online migration code was added
    was part of the following change:
    
    https://review.openstack.org/#/c/249015/
    
    Closes-bug: 1543562
    Change-Id: I2fc2f9ffac860cf25535abc9b53733bce6ddf345


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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):
  Fix Released

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


References