yahoo-eng-team team mailing list archive

[OpenStack Infra <1751192@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/556751
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e822360b6696c492bb583240483ee9593d7d24e1
Submitter: Zuul
Branch:    master

commit e822360b6696c492bb583240483ee9593d7d24e1
Author: Jake Yip <jake.yip@xxxxxxxxxxxxxx>
Date:   Tue Feb 20 16:14:10 2018 +1100

    Add --before to nova-manage db archive_deleted_rows
    
    Add a parameter to limit the archival of deleted rows by date. That is,
    only rows related to instances deleted before provided date will be
    archived.
    
    This option works together with --max_rows, if both are specified both
    will take effect.
    
    Closes-Bug: #1751192
    Change-Id: I408c22d8eada0518ec5d685213f250e8e3dae76e
    Implements: blueprint nova-archive-before


** 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/1751192

Title:
  nova-manage archive_deleted_rows date limit

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===========

  Currently we have a large number of rows in our nova databases, which
  will greatly benefit from `nova-manage archive_deleted_rows`
  (thanks!). What we would like to do is to archive all deleted records
  before a certain time (say >1 year ago). This will allow us to
  continue running reports on newly deleted instances, and allow `nova
  list --deleted` to work (up to a certain period).

  Reading the code, however, reveals that there is no ability to do
  that. Currently, it has a --max-rows, but there are certain
  shortcomings with this option

  1) related records are archived inconsistently. Due to foreign keys,
  it has to archive fk tables first. It will take up to `--max-rows`
  from the first table it encounters, working its way through all tables
  eventually reaching `instances` table last. What this means, is that
  instances is always archived last. An instance might have all of it's
  information in fk tables archived before itself is.

  2) there is no ability to keep records up to certain timerange ago.

  We are working on an in-house patch to achieve this. If this is of use
  to the community I'd be happy to work on this to be included upstream.

  Environment
  ===========
  We are running Newton Nova

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