Bug #1055

Flavors cannot be removed from circulation

Added by Vangelis Koukis almost 10 years ago. Updated almost 10 years ago.

Status:Closed Start date:09/07/2011
Priority:High Due date:
Assignee:Giorgos Verigakis % Done:

0%

Category:Cyclades API Spent time: -
Target version:v0.6.2

Description

There's no way to stop usage of a Flavor in the API, once it's in the DB.
There should be some way (a public flag? a deleted flag?) to mark a Flavor as not used.
The admin can't just remove the instance of the Flavor model, because this will lead to the deletion of all corresponding instances of VirtualMachine.

The API should honour this flag and not include the relevant flavors in GET /flavors responses.


Related issues

related to Synnefo - Feature #1157: Support deletion of Flavors, support servers referring to... Closed 09/16/2011
related to Synnefo - Feature #1472: Document removal of Flavors from circulation Closed 10/11/2011 10/11/2011

Associated revisions

Revision 2c60cbef
Added by Giorgos Verigakis almost 10 years ago

Add deleted states in Flavor and SynnefoUser

A database migration is needed.

Refs #1055

Revision 870c24a0
Added by Giorgos Verigakis almost 10 years ago

Admin improvements

  • Flavors use the deleted flag instead of deleting the object.
  • SynnefoUsers use the DELETED state instead of deleting the object.
  • Object lists do not show deleted objects.

Refs #849
Refs #1055

History

#1 Updated by Vangelis Koukis almost 10 years ago

  • Category changed from Cyclades UI to Cyclades API

#2 Updated by Giorgos Verigakis almost 10 years ago

Perhaps such a flag should be added to SynnefoUser too then?

Image, VirtualMachine and Network already have such a flag (or a DELETED state). Then we could only delete objects if their deleted flag is True and there are no dependencies.

#3 Updated by Vangelis Koukis almost 10 years ago

  • Status changed from Assigned to Closed
  • Target version changed from v0.7 to v0.6.2

Merged into master, closing.

Also available in: Atom PDF