yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74651
[Bug 1791824] [NEW] RFE: add configurable limit nova-status upgrade check for warning on archive/purge limit
Public bug reported:
This came up in the upgrades SIG room at the Stein PTG:
https://etherpad.openstack.org/p/upgrade-sig-ptg-stein
The request is that failing to archive/purge old deleted records from
the database can cause upgrades to have major downtime because of the
old records (heat and keystone are known major issues here, but clearly
also instances records) - and they would like a nova-status upgrade
check that checks some configured limit on deleted instances and warns
if you should archive/purge prior to starting the upgrade.
The question would be what is a sane default (1000000 soft deleted
instances records?), or something based on a time limit (deleted
instances over 3 years old), etc.
** Affects: nova
Importance: Wishlist
Status: Triaged
** Tags: nova-status upgrades
** Changed in: nova
Importance: Undecided => Wishlist
--
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/1791824
Title:
RFE: add configurable limit nova-status upgrade check for warning on
archive/purge limit
Status in OpenStack Compute (nova):
Triaged
Bug description:
This came up in the upgrades SIG room at the Stein PTG:
https://etherpad.openstack.org/p/upgrade-sig-ptg-stein
The request is that failing to archive/purge old deleted records from
the database can cause upgrades to have major downtime because of the
old records (heat and keystone are known major issues here, but
clearly also instances records) - and they would like a nova-status
upgrade check that checks some configured limit on deleted instances
and warns if you should archive/purge prior to starting the upgrade.
The question would be what is a sane default (1000000 soft deleted
instances records?), or something based on a time limit (deleted
instances over 3 years old), etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1791824/+subscriptions