Bug #1055
Flavors cannot be removed from circulation
| 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
Associated revisions
History
#1 Updated by Vangelis Koukis about 12 years ago
- Category changed from Cyclades UI to Cyclades API
#2 Updated by Giorgos Verigakis about 12 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 about 12 years ago
- Status changed from Assigned to Closed
- Target version changed from v0.7 to v0.6.2
Merged into master, closing.