)]}'
{"specs/backlog/approved/limit-spawn-rate-for-users.rst":[{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"63ccf7c49dd62947f36a24aa8fa87c25a1092050","unresolved":false,"context_lines":[{"line_number":20,"context_line":"Problem description"},{"line_number":21,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Using the max_count in an API call for the creation of instances, a user can"},{"line_number":24,"context_line":"ask for as many instances he wants except he will be limited by his quota."},{"line_number":25,"context_line":"The rate-limit available with api filters can only the number of calls."},{"line_number":26,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a29b11f_683b409d","line":23,"updated":"2015-10-20 02:35:22.000000000","message":"There is a possibility that this functionality will be removed in mitaka see:\n\n https://review.openstack.org/#/c/188575/","commit_id":"277d248016068b16ea35fa7a39a46c5dded7da14"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"63ccf7c49dd62947f36a24aa8fa87c25a1092050","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"As an operator, I want to provide high quota to my users and I want to limit"},{"line_number":34,"context_line":"the number of instance creations they can call at a time in order to protect"},{"line_number":35,"context_line":"the service from deny of service or slow responses."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Project Priority"},{"line_number":38,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a29b11f_28e1c8fe","line":35,"updated":"2015-10-20 02:35:22.000000000","message":"If slowing down API/conductor availability is the issue why not scale these resources?","commit_id":"277d248016068b16ea35fa7a39a46c5dded7da14"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"9832dce533d15c94d408273348444195c3706c75","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"As an operator, I want to provide high quota to my users and I want to limit"},{"line_number":34,"context_line":"the number of instance creations they can call at a time in order to protect"},{"line_number":35,"context_line":"the service from deny of service or slow responses."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Project Priority"},{"line_number":38,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a29b11f_5c87fcd6","line":35,"in_reply_to":"3a29b11f_28e1c8fe","updated":"2015-10-20 18:55:20.000000000","message":"If you spawning many vms in very short time periods then I think that bottleneck is scheduler which is not scalling well (at least now)","commit_id":"277d248016068b16ea35fa7a39a46c5dded7da14"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"426fd1a6d9417f4f9cb1a3774dd8e6b3be59aca3","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"As an operator, I want to provide high quota to my users and I want to limit"},{"line_number":34,"context_line":"the number of instance creations they can call at a time in order to protect"},{"line_number":35,"context_line":"the service from deny of service or slow responses."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Project Priority"},{"line_number":38,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a29b11f_d36f6e29","line":35,"in_reply_to":"3a29b11f_5c87fcd6","updated":"2015-10-21 01:11:51.000000000","message":"It\u0027d be great to see some numbers to back up this statement.","commit_id":"277d248016068b16ea35fa7a39a46c5dded7da14"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"231763e981fe95f84a88f3866105f96631910ac4","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"As an operator, I want to provide high quota to my users and I want to limit"},{"line_number":34,"context_line":"the number of instance creations they can call at a time in order to protect"},{"line_number":35,"context_line":"the service from deny of service or slow responses."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"Project Priority"},{"line_number":38,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a8ffd7b_af5e7974","line":35,"in_reply_to":"3a29b11f_d36f6e29","updated":"2015-11-24 11:10:07.000000000","message":"If you run the caching scheduler, and the current in tree filters and weighers, you should be fine now (i.e. that removes all db access during a user\u0027s scheduling decision). You may also need to reduce the number of eventlet workers. Not sure if we document this anywhere yet.\n\nHaving said that, I still get you *might* want this for other reasons, such as limited capacity, and trying to share resources.","commit_id":"277d248016068b16ea35fa7a39a46c5dded7da14"}]}