)]}'
{"nova/service.py":[{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"3efdb9de6f66b2a40a1f479e4268df8ef3dc559e","unresolved":false,"context_lines":[{"line_number":79,"context_line":"    cfg.IntOpt(\u0027osapi_compute_listen_port\u0027,"},{"line_number":80,"context_line":"               default\u003d8774,"},{"line_number":81,"context_line":"               help\u003d\u0027The port on which the OpenStack API will listen.\u0027),"},{"line_number":82,"context_line":"    cfg.IntOpt(\u0027osapi_compute_workers\u0027,"},{"line_number":83,"context_line":"               help\u003d\u0027Number of workers for OpenStack API service. The default \u0027"},{"line_number":84,"context_line":"                    \u0027will be the number of CPUs available.\u0027),"},{"line_number":85,"context_line":"    cfg.StrOpt(\u0027metadata_manager\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_aa5c184c","line":82,"updated":"2014-12-12 18:36:01.000000000","message":"This should be controlling the number of workers for your case, and is what is being set in devstack.  Should this be deprecated and renamed to the above?  And is there a bug lurking here that this used to work and no longer does?","commit_id":"0a11a8023881f8024c1887922d172af5347ae924"},{"author":{"_account_id":6589,"name":"Jesse Keating","email":"jkeating@j2solutions.net","username":"jesse-keating"},"change_message_id":"3a30db4846f7e42fb8fbc81ea83d6cac4d2aa749","unresolved":false,"context_lines":[{"line_number":79,"context_line":"    cfg.IntOpt(\u0027osapi_compute_listen_port\u0027,"},{"line_number":80,"context_line":"               default\u003d8774,"},{"line_number":81,"context_line":"               help\u003d\u0027The port on which the OpenStack API will listen.\u0027),"},{"line_number":82,"context_line":"    cfg.IntOpt(\u0027osapi_compute_workers\u0027,"},{"line_number":83,"context_line":"               help\u003d\u0027Number of workers for OpenStack API service. The default \u0027"},{"line_number":84,"context_line":"                    \u0027will be the number of CPUs available.\u0027),"},{"line_number":85,"context_line":"    cfg.StrOpt(\u0027metadata_manager\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_ad00a802","line":82,"in_reply_to":"3a961159_2f16734c","updated":"2014-12-13 01:16:20.000000000","message":"I can do that, but looking closer there are also config grabs for listen address and port. Do you want those to come from osapi_compute_* too? Was it ever intended to run a v2 endpoint differently than a v1.1 or a v3 end point?","commit_id":"0a11a8023881f8024c1887922d172af5347ae924"},{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"f790bc069256bdf827a1e4810b25ab16c2398215","unresolved":false,"context_lines":[{"line_number":79,"context_line":"    cfg.IntOpt(\u0027osapi_compute_listen_port\u0027,"},{"line_number":80,"context_line":"               default\u003d8774,"},{"line_number":81,"context_line":"               help\u003d\u0027The port on which the OpenStack API will listen.\u0027),"},{"line_number":82,"context_line":"    cfg.IntOpt(\u0027osapi_compute_workers\u0027,"},{"line_number":83,"context_line":"               help\u003d\u0027Number of workers for OpenStack API service. The default \u0027"},{"line_number":84,"context_line":"                    \u0027will be the number of CPUs available.\u0027),"},{"line_number":85,"context_line":"    cfg.StrOpt(\u0027metadata_manager\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_2f16734c","line":82,"in_reply_to":"3a961159_40b0f3dc","updated":"2014-12-12 20:58:11.000000000","message":"From my quick testing it looks like those are being pulled from the enabled_apis config option, and then matched against paste.ini.  It also looks like the osapi_compute option is a superset of openstack_compute_api_v* so I\u0027m not sure what the use case is for both being listed.  Regardless, I would like to avoid a proliferation of configuration options here for all the different API versions so I think a better fix would be to have osapi_compute_workers work for \"openstack_compute_api_v*\" as well.","commit_id":"0a11a8023881f8024c1887922d172af5347ae924"},{"author":{"_account_id":6589,"name":"Jesse Keating","email":"jkeating@j2solutions.net","username":"jesse-keating"},"change_message_id":"853d464aec6ef925a4365f34d14ad02b99e5bcd3","unresolved":false,"context_lines":[{"line_number":79,"context_line":"    cfg.IntOpt(\u0027osapi_compute_listen_port\u0027,"},{"line_number":80,"context_line":"               default\u003d8774,"},{"line_number":81,"context_line":"               help\u003d\u0027The port on which the OpenStack API will listen.\u0027),"},{"line_number":82,"context_line":"    cfg.IntOpt(\u0027osapi_compute_workers\u0027,"},{"line_number":83,"context_line":"               help\u003d\u0027Number of workers for OpenStack API service. The default \u0027"},{"line_number":84,"context_line":"                    \u0027will be the number of CPUs available.\u0027),"},{"line_number":85,"context_line":"    cfg.StrOpt(\u0027metadata_manager\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_e5001104","line":82,"in_reply_to":"3a961159_aa5c184c","updated":"2014-12-12 19:01:26.000000000","message":"That\u0027s a good question. I used debugging to find the \"name\" of the service being started, but didn\u0027t actually check to see if osapi_compute was one of them. I\u0027ll dig a bit more.","commit_id":"0a11a8023881f8024c1887922d172af5347ae924"},{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"acaa81cabfe4ed313211388b4f8d1fd933fa19a7","unresolved":false,"context_lines":[{"line_number":79,"context_line":"    cfg.IntOpt(\u0027osapi_compute_listen_port\u0027,"},{"line_number":80,"context_line":"               default\u003d8774,"},{"line_number":81,"context_line":"               help\u003d\u0027The port on which the OpenStack API will listen.\u0027),"},{"line_number":82,"context_line":"    cfg.IntOpt(\u0027osapi_compute_workers\u0027,"},{"line_number":83,"context_line":"               help\u003d\u0027Number of workers for OpenStack API service. The default \u0027"},{"line_number":84,"context_line":"                    \u0027will be the number of CPUs available.\u0027),"},{"line_number":85,"context_line":"    cfg.StrOpt(\u0027metadata_manager\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_aa04ea49","line":82,"in_reply_to":"3a961159_ad00a802","updated":"2014-12-16 14:54:19.000000000","message":"V3 as it currently exists is essentially dead.  So the question becomes is it intended to run v2.1 differently than v2 and I don\u0027t believe there is any intention of allowing that currently.\n\nI\u0027m not familiar with all of the history, but my understanding is that v2 and v1.1 are equivalent.  v1.1 was renamed to v2 at some point I think.","commit_id":"0a11a8023881f8024c1887922d172af5347ae924"},{"author":{"_account_id":6589,"name":"Jesse Keating","email":"jkeating@j2solutions.net","username":"jesse-keating"},"change_message_id":"7277beacbe25e6992e03d34a40ef1343d836fb5b","unresolved":false,"context_lines":[{"line_number":79,"context_line":"    cfg.IntOpt(\u0027osapi_compute_listen_port\u0027,"},{"line_number":80,"context_line":"               default\u003d8774,"},{"line_number":81,"context_line":"               help\u003d\u0027The port on which the OpenStack API will listen.\u0027),"},{"line_number":82,"context_line":"    cfg.IntOpt(\u0027osapi_compute_workers\u0027,"},{"line_number":83,"context_line":"               help\u003d\u0027Number of workers for OpenStack API service. The default \u0027"},{"line_number":84,"context_line":"                    \u0027will be the number of CPUs available.\u0027),"},{"line_number":85,"context_line":"    cfg.StrOpt(\u0027metadata_manager\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_40b0f3dc","line":82,"in_reply_to":"3a961159_e5001104","updated":"2014-12-12 19:10:41.000000000","message":"Just checked again, and when services start here, there are start ups (and worker checks) for ec2, osapi_compute, metadata, and openstack_compute_api_v2. So this does indeed look like a need for the tuneable, not a deprecation issue.","commit_id":"0a11a8023881f8024c1887922d172af5347ae924"},{"author":{"_account_id":6062,"name":"jichenjc","email":"jichenjc@cn.ibm.com","username":"jichenjc"},"change_message_id":"8d53717b43e24ef554eafb2b592312932c89d783","unresolved":false,"context_lines":[{"line_number":332,"context_line":"        self.loader \u003d loader or wsgi.Loader()"},{"line_number":333,"context_line":"        self.app \u003d self.loader.load_app(name)"},{"line_number":334,"context_line":"        # inherit all compute_api worker counts from osapi_compute"},{"line_number":335,"context_line":"        if name.startswith(\u0027openstack_compute_api\u0027):"},{"line_number":336,"context_line":"            wname \u003d \u0027osapi_compute\u0027"},{"line_number":337,"context_line":"        else:"},{"line_number":338,"context_line":"            wname \u003d name"}],"source_content_type":"text/x-python","patch_set":2,"id":"3a961159_3fa76ca8","line":335,"updated":"2014-12-15 02:07:03.000000000","message":"I assuming here we are talking about openstack_compute_api_xx\nwhile xx is v2/v3/v2.1 etc\nbut those are only versions of API so the number of workers should be same no matter how many version of APIs we supported","commit_id":"446c75612705fcdd64821980149c7ead1ab16be6"},{"author":{"_account_id":5441,"name":"Andrew Laski","email":"andrew@lascii.com","username":"alaski"},"change_message_id":"79a1f56be3b5a8cb121fa126eb272e06336358cc","unresolved":false,"context_lines":[{"line_number":332,"context_line":"        self.loader \u003d loader or wsgi.Loader()"},{"line_number":333,"context_line":"        self.app \u003d self.loader.load_app(name)"},{"line_number":334,"context_line":"        # inherit all compute_api worker counts from osapi_compute"},{"line_number":335,"context_line":"        if name.startswith(\u0027openstack_compute_api\u0027):"},{"line_number":336,"context_line":"            wname \u003d \u0027osapi_compute\u0027"},{"line_number":337,"context_line":"        else:"},{"line_number":338,"context_line":"            wname \u003d name"}],"source_content_type":"text/x-python","patch_set":2,"id":"3a961159_36e67c17","line":335,"in_reply_to":"3a961159_3fa76ca8","updated":"2014-12-16 15:01:07.000000000","message":"I agree, but I would be okay with pushing that off as a second bug to be addressed separately.  This at least addresses the case where someone configures just v2 with openstack_compute_api_v2 and their workers differ from what they expected based on a previous configuration.","commit_id":"446c75612705fcdd64821980149c7ead1ab16be6"}]}