)]}'
{"doc/source/use-cases.rst":[{"author":{"_account_id":10311,"name":"Joseph Davis","email":"joseph.davis@suse.com","username":"joadavis"},"change_message_id":"73b3520eed93236c0009e238869c08a8243550d1","unresolved":false,"context_lines":[{"line_number":4,"context_line":"When adding a new use case, please use ``use-cases/template.rst`` as"},{"line_number":5,"context_line":"a starting point."},{"line_number":6,"context_line":""},{"line_number":7,"context_line":".. commented out until files are added"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"   .. toctree::"},{"line_number":10,"context_line":"      :glob:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfb3d3c7_48fc423d","side":"PARENT","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":38},"updated":"2019-05-30 14:57:58.000000000","message":"Ahhh, that is the bit I was missing, I glossed right over the fact that the toctree was commented out.","commit_id":"9b1840cd655fe4b36bfe768e2cf8a367a87a8717"},{"author":{"_account_id":12404,"name":"Rico Lin","email":"ricolin@ricolky.com","username":"rico.lin"},"change_message_id":"50ec627e457451baa0a4473bbed275a64c29b80d","unresolved":false,"context_lines":[{"line_number":14,"context_line":"   :glob:"},{"line_number":15,"context_line":"   :maxdepth: 1"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"   use-cases/*"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Control plane scaling"},{"line_number":20,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfb3d3c7_17441746","line":17,"range":{"start_line":17,"start_character":3,"end_line":17,"end_character":14},"updated":"2019-06-12 08:58:04.000000000","message":"This line will include `use-cases/autoscale-compute-basic-metrics.rst` which I believe should belong to control plane scaling","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"},{"author":{"_account_id":27224,"name":"Duc Truong","email":"duc.openstack@gmail.com","username":"dtruong2"},"change_message_id":"24a780784bbe37fd3c0e98bf3a888884ac9009a5","unresolved":false,"context_lines":[{"line_number":14,"context_line":"   :glob:"},{"line_number":15,"context_line":"   :maxdepth: 1"},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"   use-cases/*"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Control plane scaling"},{"line_number":20,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fb8cfa7_19ba336d","line":17,"range":{"start_line":17,"start_character":3,"end_line":17,"end_character":14},"in_reply_to":"bfb3d3c7_17441746","updated":"2019-06-12 18:39:34.000000000","message":"I don\u0027t think autoscale-compute-basic-metrics.rst belongs to control plane scaling.  It talks about scaling compute resources (e.g. VMs).  \n\nControl plane scaling to me means scaling the infrastructure running the OpenStack services (nova, keystone, etc).","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"}],"use-cases/autoscale-compute-custom-metrics.rst":[{"author":{"_account_id":27224,"name":"Duc Truong","email":"duc.openstack@gmail.com","username":"dtruong2"},"change_message_id":"128671009325fff7d68524dcd9d3db769c19675b","unresolved":false,"context_lines":[{"line_number":19,"context_line":""},{"line_number":20,"context_line":"An Application developer will define metrics which their application"},{"line_number":21,"context_line":"can emit to a Monitoring Service.  This could be a report of RPS from"},{"line_number":22,"context_line":"a web application.  Or information about distribution of objects reported"},{"line_number":23,"context_line":"by Swift.  The Monitoring Service would generate alarms based on the"},{"line_number":24,"context_line":"metrics or report them to a Decision Service for analysis.  Commands"},{"line_number":25,"context_line":"would be passed to an Orchestration Engine to scale up or down."}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fb8cfa7_69abf31c","line":22,"range":{"start_line":22,"start_character":17,"end_line":22,"end_character":21},"updated":"2019-06-04 18:13:44.000000000","message":"Nit: probably should merge the two sentences into one.","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"}],"use-cases/autoscale-compute-resource-balancing.rst":[{"author":{"_account_id":27224,"name":"Duc Truong","email":"duc.openstack@gmail.com","username":"dtruong2"},"change_message_id":"128671009325fff7d68524dcd9d3db769c19675b","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  configure highly available autoscaling services with Free Open"},{"line_number":7,"context_line":"  Source Software."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"* As an operator of OpenStack I want to be able to add additional"},{"line_number":10,"context_line":"  compute nodes to my cluster from a pool of available bare metal"},{"line_number":11,"context_line":"  inventory automatically in response to resource consumption within"},{"line_number":12,"context_line":"  my cloud."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* As an operator of OpenStack I want to be able to remove compute"},{"line_number":15,"context_line":"  nodes from my cluster and return them to the pool of available bare"},{"line_number":16,"context_line":"  metal inventory nodes in response to an excess quantity of compute"},{"line_number":17,"context_line":"  resource availability within my cloud."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* As an app deployer I want to automatically scale-in one app to free"},{"line_number":20,"context_line":"  up physical infra to scale-out another app which needs the resources"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fb8cfa7_a44a7224","line":17,"range":{"start_line":9,"start_character":0,"end_line":17,"end_character":40},"updated":"2019-06-04 18:13:44.000000000","message":"I think these two use cases should be separated out into its own use case, maybe something called Auto-scale Bare Metal Compute? It seems confusing to include with the priority based auto-scaling.","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"},{"author":{"_account_id":27224,"name":"Duc Truong","email":"duc.openstack@gmail.com","username":"dtruong2"},"change_message_id":"24a780784bbe37fd3c0e98bf3a888884ac9009a5","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  configure highly available autoscaling services with Free Open"},{"line_number":7,"context_line":"  Source Software."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"* As an operator of OpenStack I want to be able to add additional"},{"line_number":10,"context_line":"  compute nodes to my cluster from a pool of available bare metal"},{"line_number":11,"context_line":"  inventory automatically in response to resource consumption within"},{"line_number":12,"context_line":"  my cloud."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* As an operator of OpenStack I want to be able to remove compute"},{"line_number":15,"context_line":"  nodes from my cluster and return them to the pool of available bare"},{"line_number":16,"context_line":"  metal inventory nodes in response to an excess quantity of compute"},{"line_number":17,"context_line":"  resource availability within my cloud."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* As an app deployer I want to automatically scale-in one app to free"},{"line_number":20,"context_line":"  up physical infra to scale-out another app which needs the resources"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fb8cfa7_19d313d7","line":17,"range":{"start_line":9,"start_character":0,"end_line":17,"end_character":40},"in_reply_to":"9fb8cfa7_07b3bb4e","updated":"2019-06-12 18:39:34.000000000","message":"Sounds good to me.","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"},{"author":{"_account_id":10311,"name":"Joseph Davis","email":"joseph.davis@suse.com","username":"joadavis"},"change_message_id":"6db0f80f0ab144dc70d891d38f0de338f1e4adaa","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  configure highly available autoscaling services with Free Open"},{"line_number":7,"context_line":"  Source Software."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"* As an operator of OpenStack I want to be able to add additional"},{"line_number":10,"context_line":"  compute nodes to my cluster from a pool of available bare metal"},{"line_number":11,"context_line":"  inventory automatically in response to resource consumption within"},{"line_number":12,"context_line":"  my cloud."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* As an operator of OpenStack I want to be able to remove compute"},{"line_number":15,"context_line":"  nodes from my cluster and return them to the pool of available bare"},{"line_number":16,"context_line":"  metal inventory nodes in response to an excess quantity of compute"},{"line_number":17,"context_line":"  resource availability within my cloud."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* As an app deployer I want to automatically scale-in one app to free"},{"line_number":20,"context_line":"  up physical infra to scale-out another app which needs the resources"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fb8cfa7_d01b29c7","line":17,"range":{"start_line":9,"start_character":0,"end_line":17,"end_character":40},"in_reply_to":"9fb8cfa7_a44a7224","updated":"2019-06-11 17:47:59.000000000","message":"I\u0027d included them together as they were discussed in the PTG, but we can certainly start breaking them down.  It seems like we will have a few classes of use cases, like bare metal computes vs priority based vs control plane.","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"},{"author":{"_account_id":12404,"name":"Rico Lin","email":"ricolin@ricolky.com","username":"rico.lin"},"change_message_id":"50ec627e457451baa0a4473bbed275a64c29b80d","unresolved":false,"context_lines":[{"line_number":6,"context_line":"  configure highly available autoscaling services with Free Open"},{"line_number":7,"context_line":"  Source Software."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"* As an operator of OpenStack I want to be able to add additional"},{"line_number":10,"context_line":"  compute nodes to my cluster from a pool of available bare metal"},{"line_number":11,"context_line":"  inventory automatically in response to resource consumption within"},{"line_number":12,"context_line":"  my cloud."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"* As an operator of OpenStack I want to be able to remove compute"},{"line_number":15,"context_line":"  nodes from my cluster and return them to the pool of available bare"},{"line_number":16,"context_line":"  metal inventory nodes in response to an excess quantity of compute"},{"line_number":17,"context_line":"  resource availability within my cloud."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* As an app deployer I want to automatically scale-in one app to free"},{"line_number":20,"context_line":"  up physical infra to scale-out another app which needs the resources"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9fb8cfa7_07b3bb4e","line":17,"range":{"start_line":9,"start_character":0,"end_line":17,"end_character":40},"in_reply_to":"9fb8cfa7_d01b29c7","updated":"2019-06-12 08:58:04.000000000","message":"If we have further plan to write some more detail about each case, then there are certainly benefits to separate them into different use cases doc. But IMO we can do it in the future (aka following patch)","commit_id":"8e2ce29cdf38f951cc501e5e0764d90182083626"}]}