yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Public bug reported:

http://developer.openstack.org/api-ref/compute/?expanded=delete-server-
detail#delete-server

The API reference for deleting a server is making the assumption that
the instance is going to be (hard) deleted from the system, but it
doesn't take into account the case that CONF.reclaim_instance_interval
is set, which if > 0 makes the API 'soft delete' the instance, so that
the instance's vm status is set to 'SOFT_DELETED' and at some later time
(after the CONF.reclaim_instance_interval has expired since the instance
was soft deleted), a periodic task on the compute node will delete the
instance.

So we should update the reference to talk about the soft deleted wrinkle
so we can set expectations, and it's also just in general kind of a
gross API behavior change based on configuration, but that's another
story.

** Affects: nova
     Importance: Low
         Status: Triaged


** Tags: api-ref

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

Title:
  The delete server API reference doesn't mention the SOFT_DELETED
  wrinkle

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  http://developer.openstack.org/api-ref/compute/?expanded=delete-
  server-detail#delete-server

  The API reference for deleting a server is making the assumption that
  the instance is going to be (hard) deleted from the system, but it
  doesn't take into account the case that CONF.reclaim_instance_interval
  is set, which if > 0 makes the API 'soft delete' the instance, so that
  the instance's vm status is set to 'SOFT_DELETED' and at some later
  time (after the CONF.reclaim_instance_interval has expired since the
  instance was soft deleted), a periodic task on the compute node will
  delete the instance.

  So we should update the reference to talk about the soft deleted
  wrinkle so we can set expectations, and it's also just in general kind
  of a gross API behavior change based on configuration, but that's
  another story.

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