yahoo-eng-team team mailing list archive

[HanGuangyu <1943418@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The killed status of images is just a thing in v1. In v2, we are
deprecating the 'killed' status, so it's allowed to restore image from
'saving' to 'queued' so that upload can be retried.

However, some old killed images from v1 may still exist in the DB. We
can't check or list it in CLI.

> Maybe we need a glance-manage command to clean old killed images from
the DB and a prompt message to tell operators to do that thing at some
point?

Such as, add a "clean" agruments for "openstack image" command. The
users could use "openstack image clean" command to clean the old killed
images form database. And When users use "list" command, a check of
killed images will be run. If some old kiled images are in the database,
it will prompt that “Some old images with killed status is existing in
database, and the 'killed' status has been deprecated. You can use
'openstack image clean' command to clean them.”

Looking forword to your comments. If this scheme could be accepted, I can realize it. 
And if you have ideas about specific plans, welcome to discuss it.

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1943418

Title:
  Old killed images can't be manage in CLI, we need a command to clean
  it

Status in Glance:
  New

Bug description:
  The killed status of images is just a thing in v1. In v2, we are
  deprecating the 'killed' status, so it's allowed to restore image from
  'saving' to 'queued' so that upload can be retried.

  However, some old killed images from v1 may still exist in the DB. We
  can't check or list it in CLI.

  > Maybe we need a glance-manage command to clean old killed images
  from the DB and a prompt message to tell operators to do that thing at
  some point?

  Such as, add a "clean" agruments for "openstack image" command. The
  users could use "openstack image clean" command to clean the old
  killed images form database. And When users use "list" command, a
  check of killed images will be run. If some old kiled images are in
  the database, it will prompt that “Some old images with killed status
  is existing in database, and the 'killed' status has been deprecated.
  You can use 'openstack image clean' command to clean them.”

  Looking forword to your comments. If this scheme could be accepted, I can realize it. 
  And if you have ideas about specific plans, welcome to discuss it.

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