Public bug reported: We don't have an API to delete a consumer. It gets created implicitly when allocations are created against it, but it doesn't get deleted when the consumer's last allocation is removed. In some uses of placement, such as nova's, there is a high rate of turnover of consumers (instances, in nova) so this leakage has the potential to be problematic.
(Note that we have the same issue for aggregates, but don't currently have a known use case with a lot of aggregate turnover, so it is less likely to be a problem soon.) Possible solutions: - Delete a consumer record automatically when its last allocation goes away. This is nice and symmetrical, but a behavior change for the guy *recreating* a consumer (today he has to use the current generation; with this change he would have to use ``null``). - Provide an operation for deleting consumers. This is an extra step for callers (which is okay). But do we also provide an explicit (redundant) operation for creating them, just for the sake of symmetry? - Your idea here. ** Affects: nova Importance: Undecided Status: New ** Tags: placement -- 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/1778763 Title: Consumers never get deleted Status in OpenStack Compute (nova): New Bug description: We don't have an API to delete a consumer. It gets created implicitly when allocations are created against it, but it doesn't get deleted when the consumer's last allocation is removed. In some uses of placement, such as nova's, there is a high rate of turnover of consumers (instances, in nova) so this leakage has the potential to be problematic. (Note that we have the same issue for aggregates, but don't currently have a known use case with a lot of aggregate turnover, so it is less likely to be a problem soon.) Possible solutions: - Delete a consumer record automatically when its last allocation goes away. This is nice and symmetrical, but a behavior change for the guy *recreating* a consumer (today he has to use the current generation; with this change he would have to use ``null``). - Provide an operation for deleting consumers. This is an extra step for callers (which is okay). But do we also provide an explicit (redundant) operation for creating them, just for the sake of symmetry? - Your idea here. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1778763/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp