Comment 5 for bug 1417304
Revision history for this message
| Nikhil Komawar (nikhil-komawar) wrote Re: Upload/Import image continues consuming glance host cpu/memory/network resources even after the image is deleted | #5 |
I do not believe so. The intent of the author seems to indicate that they are interested in stopping the asynchronous operations when a delete call is made to the image. This however, cannot be guaranteed with asynchronous style operations being performed on the tasks.
The solution from a operator point of view seem to be to implement a rate-limiting kind of setup and possibly allow only trusted users(groups) to operate on /tasks resource if this is being considered a potential security flaw. This way it would be easier to get some sort of amendment from the user to guarantee that they will not use the resources for any malicious purposes and such.
The above mentioned approach can be implemented using tools like nginx.