)]}'
{"specs/ocata/approved/cache-occupancy-strategy.rst":[{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"7392e6033de9ffc72ee5cf9a0526bc2eabf0653f","unresolved":false,"context_lines":[{"line_number":48,"context_line":"* Use Ceilometer client to get following metrics for detecting noisy neighbor:"},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"  * cpu_l3_cache - occupancy on a VM basis"},{"line_number":51,"context_line":"  * cache_miss - total # of misses, L2 and L3 level correlate to VMs"},{"line_number":52,"context_line":"  * memory.bandwidth - local and total defined per VM"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* An algorithm to detect if cache occupancy goes beyond threshold with system"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_f81622f0","line":51,"range":{"start_line":51,"start_character":4,"end_line":51,"end_character":14},"updated":"2016-12-08 07:48:26.000000000","message":"I can\u0027t find the \u0027cache_miss\u0027 metric in the link:\nhttp://docs.openstack.org/admin-guide/telemetry-measurements.html","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"},{"author":{"_account_id":19055,"name":"Alexander Chadin","email":"joker946@gmail.com","username":"joker946"},"change_message_id":"38690f06b46f1df2f5f2c5ddd68b22a141c4c521","unresolved":false,"context_lines":[{"line_number":51,"context_line":"  * cache_miss - total # of misses, L2 and L3 level correlate to VMs"},{"line_number":52,"context_line":"  * memory.bandwidth - local and total defined per VM"},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* An algorithm to detect if cache occupancy goes beyond threshold with system"},{"line_number":55,"context_line":"  level cache starving and then choose the right target node for migration."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_ba92a549","line":55,"range":{"start_line":54,"start_character":2,"end_line":55,"end_character":75},"updated":"2016-12-09 09:55:19.000000000","message":"Could you please describe your algorithm a little bit more? What actions the strategy will do when threshold is triggered?","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"},{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"7392e6033de9ffc72ee5cf9a0526bc2eabf0653f","unresolved":false,"context_lines":[{"line_number":95,"context_line":"Other deployer impact"},{"line_number":96,"context_line":"---------------------"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"To enable these cache metrics, latest Intel server with CMT support is"},{"line_number":99,"context_line":"required."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_f8ed42f0","line":98,"range":{"start_line":98,"start_character":56,"end_line":98,"end_character":59},"updated":"2016-12-08 07:48:26.000000000","message":"Please provide an explanation or reference link","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"},{"author":{"_account_id":19055,"name":"Alexander Chadin","email":"joker946@gmail.com","username":"joker946"},"change_message_id":"38690f06b46f1df2f5f2c5ddd68b22a141c4c521","unresolved":false,"context_lines":[{"line_number":117,"context_line":"Work Items"},{"line_number":118,"context_line":"----------"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"1. Function to get required metrics via Ceilometer client"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"2. Define proper threshold for cache occupancy and memory bandwidth"},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"3. Write the execute function to locate the noisy neighbor: both cpu_l3_cache"},{"line_number":125,"context_line":"   and memory bandwidth are high.  Then select the least L3 cache competition"},{"line_number":126,"context_line":"   node as target for live migration. This can be done in similar way as the"},{"line_number":127,"context_line":"   one choosing noisy neighbor."},{"line_number":128,"context_line":""},{"line_number":129,"context_line":"Dependencies"},{"line_number":130,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_9a04097f","line":127,"range":{"start_line":120,"start_character":0,"end_line":127,"end_character":31},"updated":"2016-12-09 09:55:19.000000000","message":"You need to list here changes in project structure, like\n\"Add cache-occupancy-strategy to watcher/decision_engine/strategy/strategies\"\n\"Add appropriate unit and functional tests\"\nAnd so on","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"},{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"7392e6033de9ffc72ee5cf9a0526bc2eabf0653f","unresolved":false,"context_lines":[{"line_number":131,"context_line":""},{"line_number":132,"context_line":"* https://wiki.openstack.org/wiki/Ceilometer/blueprints/APIv2"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"* http://docs.openstack.org/admin-guide-cloud/telemetry-measurements.html"},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"* http://docs.openstack.org/developer/python-novaclient/api.html"},{"line_number":137,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_7813f20d","line":134,"range":{"start_line":134,"start_character":2,"end_line":134,"end_character":73},"updated":"2016-12-08 07:48:26.000000000","message":"http://docs.openstack.org/admin-guide/telemetry-measurements.html","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"},{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"7392e6033de9ffc72ee5cf9a0526bc2eabf0653f","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Testing"},{"line_number":140,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"Unit and funcational test are needed."},{"line_number":143,"context_line":""},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_38d7ba24","line":142,"range":{"start_line":142,"start_character":9,"end_line":142,"end_character":20},"updated":"2016-12-08 07:48:26.000000000","message":"functional ?","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"},{"author":{"_account_id":13111,"name":"Hidekazu Nakamura","email":"hidekazuna@gmail.com","username":"hid-nakamura"},"change_message_id":"27992381e318391ab574f4997e4ab367589a0f8b","unresolved":false,"context_lines":[{"line_number":161,"context_line":""},{"line_number":162,"context_line":"None"},{"line_number":163,"context_line":""},{"line_number":164,"context_line":".. list-table:: Revisions"},{"line_number":165,"context_line":"   :header-rows: 1"},{"line_number":166,"context_line":""},{"line_number":167,"context_line":"   * - Release Name"},{"line_number":168,"context_line":"     - Description"},{"line_number":169,"context_line":"   * - Liberty"},{"line_number":170,"context_line":"     - Introduced"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_a26a45eb","line":170,"range":{"start_line":164,"start_character":0,"end_line":170,"end_character":17},"updated":"2016-12-12 01:42:05.000000000","message":"These should be deleted?","commit_id":"33f4d5c049a4f9d0f71f76226e189123002bac45"}],"specs/ocata/approved/noisy_neighbor_strategy.rst":[{"author":{"_account_id":11750,"name":"Antoine Cabot","email":"antoine.cabot@b-com.com","username":"antoinecabot"},"change_message_id":"9e39a7e09a14d5a079b0f0b54842fd474abc1b12","unresolved":false,"context_lines":[{"line_number":40,"context_line":"Proposed change"},{"line_number":41,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"This spec need add one goal and one strategy for its purpose"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"* Adds one new goal, like cache_optimization"},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_bd462b4d","line":43,"range":{"start_line":43,"start_character":14,"end_line":43,"end_character":15},"updated":"2017-01-10 15:01:41.000000000","message":"needs to add","commit_id":"e722595154d0b8d89e0ea2f56aaeef49cdce8942"},{"author":{"_account_id":11750,"name":"Antoine Cabot","email":"antoine.cabot@b-com.com","username":"antoinecabot"},"change_message_id":"9e39a7e09a14d5a079b0f0b54842fd474abc1b12","unresolved":false,"context_lines":[{"line_number":50,"context_line":""},{"line_number":51,"context_line":"  * cpu_l3_cache - occupancy on a VM basis"},{"line_number":52,"context_line":"  * cache_miss - total # of misses, L2 and L3 level correlate to VMs"},{"line_number":53,"context_line":"  * memory.bandwidth - local and total defined per VM"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* An algorithm to detect if cache occupancy goes beyond threshold with system"},{"line_number":56,"context_line":"  level cache starving and then choose the right target node for migration."}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_3d7f9b67","line":53,"range":{"start_line":53,"start_character":3,"end_line":53,"end_character":53},"updated":"2017-01-10 15:01:41.000000000","message":"could you explain why you need memory bandwidth in your strategy ?","commit_id":"e722595154d0b8d89e0ea2f56aaeef49cdce8942"},{"author":{"_account_id":23210,"name":"YumengBao","email":"bao.yumeng@zte.com.cn","username":"YumengBao"},"change_message_id":"324b85ddd3b7e975d0504dcba5cf32385042d0ad","unresolved":false,"context_lines":[{"line_number":132,"context_line":""},{"line_number":133,"context_line":"* https://wiki.openstack.org/wiki/Ceilometer/blueprints/APIv2"},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"* http://docs.openstack.org/admin-guide-cloud/telemetry-measurements.html"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"* http://docs.openstack.org/developer/python-novaclient/api.html"},{"line_number":138,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_abba6d08","line":135,"range":{"start_line":135,"start_character":0,"end_line":135,"end_character":73},"updated":"2017-01-03 11:49:21.000000000","message":"http://docs.openstack.org/admin-guide/telemetry-measurements.html？","commit_id":"e722595154d0b8d89e0ea2f56aaeef49cdce8942"},{"author":{"_account_id":23210,"name":"YumengBao","email":"bao.yumeng@zte.com.cn","username":"YumengBao"},"change_message_id":"324b85ddd3b7e975d0504dcba5cf32385042d0ad","unresolved":false,"context_lines":[{"line_number":140,"context_line":"Testing"},{"line_number":141,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"Unit and funcational test are needed."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":5,"id":"ba5201f7_31a98ae0","line":143,"range":{"start_line":143,"start_character":9,"end_line":143,"end_character":20},"updated":"2017-01-03 11:49:21.000000000","message":"functional","commit_id":"e722595154d0b8d89e0ea2f56aaeef49cdce8942"},{"author":{"_account_id":21361,"name":"Chris Spencer","email":"christopher.m.spencer@intel.com","username":"chrisspencer"},"change_message_id":"0d26a118a9e9ad2f7689684235d4fd2455ee5c05","unresolved":false,"context_lines":[{"line_number":8,"context_line":"Noisy Neighbor Strategy"},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"https://blueprints.launchpad.net/watcher/+spec/cache-occupancy-strategy"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This spec describes a new strategy that migrates a VM consuming large amount"},{"line_number":14,"context_line":"of last level cache (LLC) over time while being co-located with other VMs"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3a461143_df748f37","line":11,"range":{"start_line":11,"start_character":0,"end_line":11,"end_character":71},"updated":"2017-01-27 21:50:12.000000000","message":"Should the be updated to https://blueprints.launchpad.net/watcher/+spec/noisy-neighbor-strategy ?","commit_id":"0bcce2dd7ea29a02885f63df266ebb49cfcdf1e6"}],"specs/pike/approved/noisy_neighbor_strategy.rst":[{"author":{"_account_id":23598,"name":"Zhong Luyao","email":"luyao.zhong@intel.com","username":"ZhongLuyao"},"change_message_id":"8676503eaf5b3ed357c5f5ee112bb058bea52740","unresolved":false,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/watcher/+spec/cache-occupancy-strategy"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This spec describes a new strategy that migrates a VM consuming large amount"},{"line_number":14,"context_line":"of last level cache (LLC) over time while being co-located with other VMs"},{"line_number":15,"context_line":"on a host."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"More details will be provided soon. WIP"}],"source_content_type":"text/x-rst","patch_set":8,"id":"ffe62b97_4780cbc0","line":14,"range":{"start_line":14,"start_character":3,"end_line":14,"end_character":25},"updated":"2017-03-28 09:21:22.000000000","message":"Only LLC?","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":23598,"name":"Zhong Luyao","email":"luyao.zhong@intel.com","username":"ZhongLuyao"},"change_message_id":"b35167881ea2da3f02dcd24e62b184d0b168244d","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"* Use Ceilometer client to get following metrics for detecting noisy neighbor:"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"  * cpu_l3_cache - occupancy on a VM basis"},{"line_number":52,"context_line":"  * cache_miss - total # of misses, L2 and L3 level correlate to VMs"},{"line_number":53,"context_line":"  * memory.bandwidth - local and total defined per VM"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* An algorithm to detect if cache occupancy goes beyond threshold with system"},{"line_number":56,"context_line":"  level cache starving and then choose the right target node for migration."}],"source_content_type":"text/x-rst","patch_set":8,"id":"ba2be162_5107d41b","line":53,"range":{"start_line":51,"start_character":0,"end_line":53,"end_character":53},"updated":"2017-03-02 03:03:54.000000000","message":"probably useful metrics：\n  1.metrics to detect noisy neighbor:\n  * cpu_l3_cache\n  * memory.bandwidth.local \u0026 memory.bandwidth.total \n  2.metrics of detect VMs affcted ,to judge whether the noisy neighbor makes big affects to other VMs \n  * perf.cpu.cycles \u0026 perf.instructions\n  * perf.cache.references ：cache hits\n  * perf.cache.misses：cache miss\n  (use cache hits and miss to compute cache miss rate may be beter)","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"9b98bf3fecb04d46034b920bdd54a3871f5cbff4","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  * cache_miss - total # of misses, L2 and L3 level correlate to VMs"},{"line_number":53,"context_line":"  * memory.bandwidth - local and total defined per VM"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"* An algorithm to detect if cache occupancy goes beyond threshold with system"},{"line_number":56,"context_line":"  level cache starving and then choose the right target node for migration."},{"line_number":57,"context_line":""},{"line_number":58,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"da36d5c6_99929056","line":55,"range":{"start_line":55,"start_character":2,"end_line":55,"end_character":14},"updated":"2017-02-20 08:32:06.000000000","message":"Could you explain the algorithm?","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":23598,"name":"Zhong Luyao","email":"luyao.zhong@intel.com","username":"ZhongLuyao"},"change_message_id":"8676503eaf5b3ed357c5f5ee112bb058bea52740","unresolved":false,"context_lines":[{"line_number":122,"context_line":""},{"line_number":123,"context_line":"2. Define proper threshold for cache occupancy and memory bandwidth"},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"3. Write the execute function to locate the noisy neighbor: both cpu_l3_cache"},{"line_number":126,"context_line":"   and memory bandwidth are high.  Then select the least L3 cache competition"},{"line_number":127,"context_line":"   node as target for live migration. This can be done in similar way as the"},{"line_number":128,"context_line":"   one choosing noisy neighbor."},{"line_number":129,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"ffe62b97_0711a3ac","line":126,"range":{"start_line":125,"start_character":60,"end_line":126,"end_character":23},"updated":"2017-03-28 09:21:22.000000000","message":"If a VM only monopolizes cpu_l3_cache ,it should be detected as a noisy neighbor as well.\nIt maybe better to split cpu_l3_cache and memory bandwidth into two independent strategies.","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"9b98bf3fecb04d46034b920bdd54a3871f5cbff4","unresolved":false,"context_lines":[{"line_number":132,"context_line":""},{"line_number":133,"context_line":"* https://wiki.openstack.org/wiki/Ceilometer/blueprints/APIv2"},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"* http://docs.openstack.org/admin-guide-cloud/telemetry-measurements.html"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"* http://docs.openstack.org/developer/python-novaclient/api.html"},{"line_number":138,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"da36d5c6_390c4494","line":135,"range":{"start_line":135,"start_character":2,"end_line":135,"end_character":73},"updated":"2017-02-20 08:32:06.000000000","message":"Replaced with:\nhttps://docs.openstack.org/admin-guide/telemetry-measurements.html","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":21692,"name":"licanwei","email":"li.canwei2@zte.com.cn","username":"licanwei"},"change_message_id":"9b98bf3fecb04d46034b920bdd54a3871f5cbff4","unresolved":false,"context_lines":[{"line_number":134,"context_line":""},{"line_number":135,"context_line":"* http://docs.openstack.org/admin-guide-cloud/telemetry-measurements.html"},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"* http://docs.openstack.org/developer/python-novaclient/api.html"},{"line_number":138,"context_line":""},{"line_number":139,"context_line":""},{"line_number":140,"context_line":"Testing"}],"source_content_type":"text/x-rst","patch_set":8,"id":"da36d5c6_f9bb8c73","line":137,"range":{"start_line":137,"start_character":2,"end_line":137,"end_character":6},"updated":"2017-02-20 08:32:06.000000000","message":"https","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":23598,"name":"Zhong Luyao","email":"luyao.zhong@intel.com","username":"ZhongLuyao"},"change_message_id":"8676503eaf5b3ed357c5f5ee112bb058bea52740","unresolved":false,"context_lines":[{"line_number":154,"context_line":""},{"line_number":155,"context_line":"http://www.intel.com/content/www/us/en/architecture-and-technology/resource-director-technology.html"},{"line_number":156,"context_line":""},{"line_number":157,"context_line":"https://01.org/zh/packet-processing/cache-monitoring-technology-memory-bandwidth-monitoring-cache-allocation-technology-code-and-data"},{"line_number":158,"context_line":""},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"History"}],"source_content_type":"text/x-rst","patch_set":8,"id":"ffe62b97_075ac328","line":157,"range":{"start_line":157,"start_character":0,"end_line":157,"end_character":133},"updated":"2017-03-28 09:21:22.000000000","message":"404 not found","commit_id":"92ac3d34cad409d2e23a1d03dfb33581af45c5b4"},{"author":{"_account_id":6437,"name":"Susanne Balle","email":"sleipnir012@gmail.com","username":"susanne-balle"},"change_message_id":"4b855964417846330dd8ec3374336d73ed5b595f","unresolved":false,"context_lines":[{"line_number":11,"context_line":"https://blueprints.launchpad.net/watcher/+spec/noisy-neighbor-strategy"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This spec describes a new strategy that identifies and migrates a Noisy"},{"line_number":14,"context_line":"Neighbor, which is a low priority VM that negatively affects Instructions"},{"line_number":15,"context_line":"Per Cycle (IPC) and Last Level Cache (LLC) of a high priority VM when located"},{"line_number":16,"context_line":"on the same host."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dfeb2761_c3456619","line":14,"range":{"start_line":14,"start_character":21,"end_line":14,"end_character":25},"updated":"2017-03-31 13:48:30.000000000","message":"nit: lower","commit_id":"9408435c87fcd79181a9c978a7d32e1950401dbe"},{"author":{"_account_id":6437,"name":"Susanne Balle","email":"sleipnir012@gmail.com","username":"susanne-balle"},"change_message_id":"4b855964417846330dd8ec3374336d73ed5b595f","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This spec describes a new strategy that identifies and migrates a Noisy"},{"line_number":14,"context_line":"Neighbor, which is a low priority VM that negatively affects Instructions"},{"line_number":15,"context_line":"Per Cycle (IPC) and Last Level Cache (LLC) of a high priority VM when located"},{"line_number":16,"context_line":"on the same host."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dfeb2761_e30e2ae4","line":15,"range":{"start_line":15,"start_character":48,"end_line":15,"end_character":52},"updated":"2017-03-31 13:48:30.000000000","message":"nit: higher","commit_id":"9408435c87fcd79181a9c978a7d32e1950401dbe"},{"author":{"_account_id":21361,"name":"Chris Spencer","email":"christopher.m.spencer@intel.com","username":"chrisspencer"},"change_message_id":"e5e106e0ca68a06e27c6e42523b82655ad3464c8","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Problem description"},{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Noisy neighbor is a big problem in multi-tenant clouds. Some low priority VMs"},{"line_number":23,"context_line":"monopolize CPU, I/O and network bandwidth, and negatively affect other high"},{"line_number":24,"context_line":"priority VMs\u0027 performance. There are already strategies to cover some of them,"},{"line_number":25,"context_line":"like CPU utilization. But IPC and LLC are not covered at this point."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"IPC is the average number of instructions executed for each clock cycle. It"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dfeb2761_9f120ab1","line":24,"range":{"start_line":22,"start_character":56,"end_line":24,"end_character":25},"updated":"2017-03-31 18:31:14.000000000","message":"nit:  \"Some lower priority VMs can negatively affect performance on higher priority VMs by monopolizing CPU, I/O, and network bandwidth.\"","commit_id":"9408435c87fcd79181a9c978a7d32e1950401dbe"},{"author":{"_account_id":6437,"name":"Susanne Balle","email":"sleipnir012@gmail.com","username":"susanne-balle"},"change_message_id":"4b855964417846330dd8ec3374336d73ed5b595f","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Noisy neighbor is a big problem in multi-tenant clouds. Some low priority VMs"},{"line_number":23,"context_line":"monopolize CPU, I/O and network bandwidth, and negatively affect other high"},{"line_number":24,"context_line":"priority VMs\u0027 performance. There are already strategies to cover some of them,"},{"line_number":25,"context_line":"like CPU utilization. But IPC and LLC are not covered at this point."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"IPC is the average number of instructions executed for each clock cycle. It"},{"line_number":28,"context_line":"is an aspect of processor\u0027s performance. LLC(Last Level Cache), or L3 cache"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dfeb2761_439b9671","line":25,"range":{"start_line":25,"start_character":0,"end_line":25,"end_character":20},"updated":"2017-03-31 13:48:30.000000000","message":"as well as algorithm using a threadshold for cache occupancy as an indicator to identify a noisy neighbor. There algorithms are too simple and do not take into consideration the interaction between VMs including the performance impact if any as well as the VMs relative priority to each other. For example a VM could use 50% cache occupancy and it could be fine. It all depend on the VM\u0027s priority.","commit_id":"9408435c87fcd79181a9c978a7d32e1950401dbe"},{"author":{"_account_id":21361,"name":"Chris Spencer","email":"christopher.m.spencer@intel.com","username":"chrisspencer"},"change_message_id":"e5e106e0ca68a06e27c6e42523b82655ad3464c8","unresolved":false,"context_lines":[{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Noisy neighbor is a big problem in multi-tenant clouds. Some low priority VMs"},{"line_number":23,"context_line":"monopolize CPU, I/O and network bandwidth, and negatively affect other high"},{"line_number":24,"context_line":"priority VMs\u0027 performance. There are already strategies to cover some of them,"},{"line_number":25,"context_line":"like CPU utilization. But IPC and LLC are not covered at this point."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"IPC is the average number of instructions executed for each clock cycle. It"},{"line_number":28,"context_line":"is an aspect of processor\u0027s performance. LLC(Last Level Cache), or L3 cache"}],"source_content_type":"text/x-rst","patch_set":13,"id":"dfeb2761_9f60ca34","line":25,"range":{"start_line":24,"start_character":27,"end_line":25,"end_character":68},"updated":"2017-03-31 18:31:14.000000000","message":"nit: \"Currently, there are strategies that cover some scenarios like excessive CPU utilization; however, IPC and LLC scenarios are not currently covered.","commit_id":"9408435c87fcd79181a9c978a7d32e1950401dbe"},{"author":{"_account_id":21361,"name":"Chris Spencer","email":"christopher.m.spencer@intel.com","username":"chrisspencer"},"change_message_id":"e5e106e0ca68a06e27c6e42523b82655ad3464c8","unresolved":false,"context_lines":[{"line_number":35,"context_line":"----------"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"As an openstack operator, I need to find noisy neighbor VMs that affect my"},{"line_number":38,"context_line":"high priority VMs, and migrate it to another node that has no noisy negihbor"},{"line_number":39,"context_line":"issues."},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":13,"id":"dfeb2761_7fb1868f","line":38,"range":{"start_line":38,"start_character":31,"end_line":38,"end_character":33},"updated":"2017-03-31 18:31:14.000000000","message":"them","commit_id":"9408435c87fcd79181a9c978a7d32e1950401dbe"},{"author":{"_account_id":11750,"name":"Antoine Cabot","email":"antoine.cabot@b-com.com","username":"antoinecabot"},"change_message_id":"45be61865bd9a4cc087cf811fc661e470e581395","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Noisy neighbor is a big problem in multi-tenant clouds. Some lower priority"},{"line_number":23,"context_line":"VMs can negatively affect performance on higher priority VMs by monopolizing"},{"line_number":24,"context_line":"CPU, I/O, and network bandwidth. There are already strategies to cover some of"},{"line_number":25,"context_line":"them like CPU utilization as well as algorithm using a threadshold for cache"},{"line_number":26,"context_line":"occupancy as an indicator to identify a noisy neighbor. These algorithms are"},{"line_number":27,"context_line":"too simple and do not take into consideration the interaction between VMs"},{"line_number":28,"context_line":"including the performance impact if any as well as the VMs\u0027 relative priority"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3f044301_1b311eed","line":25,"range":{"start_line":25,"start_character":55,"end_line":25,"end_character":66},"updated":"2017-05-09 19:38:56.000000000","message":"s/threadshold/threshold","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":22775,"name":"Prudhvi Rao Shedimbi","email":"prudhvi.rao.shedimbi@intel.com","username":"pshedimb"},"change_message_id":"32ae6393705f010932f042df3c78fba43a3403c0","unresolved":false,"context_lines":[{"line_number":22,"context_line":"Noisy neighbor is a big problem in multi-tenant clouds. Some lower priority"},{"line_number":23,"context_line":"VMs can negatively affect performance on higher priority VMs by monopolizing"},{"line_number":24,"context_line":"CPU, I/O, and network bandwidth. There are already strategies to cover some of"},{"line_number":25,"context_line":"them like CPU utilization as well as algorithm using a threadshold for cache"},{"line_number":26,"context_line":"occupancy as an indicator to identify a noisy neighbor. These algorithms are"},{"line_number":27,"context_line":"too simple and do not take into consideration the interaction between VMs"},{"line_number":28,"context_line":"including the performance impact if any as well as the VMs\u0027 relative priority"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1f013ff3_c821d9fd","line":25,"range":{"start_line":25,"start_character":55,"end_line":25,"end_character":66},"in_reply_to":"3f044301_1b311eed","updated":"2017-05-16 22:12:13.000000000","message":"Done","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":11750,"name":"Antoine Cabot","email":"antoine.cabot@b-com.com","username":"antoinecabot"},"change_message_id":"45be61865bd9a4cc087cf811fc661e470e581395","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"Use Cases"},{"line_number":41,"context_line":"----------"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"As an openstack operator, I need to find noisy neighbor VMs that affect my"},{"line_number":44,"context_line":"high priority VMs, and migrate them to another node that has no noisy negihbor"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3f044301_fb9b12c6","line":41,"range":{"start_line":41,"start_character":9,"end_line":41,"end_character":10},"updated":"2017-05-09 19:38:56.000000000","message":"remove 1 \"-\"","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":22775,"name":"Prudhvi Rao Shedimbi","email":"prudhvi.rao.shedimbi@intel.com","username":"pshedimb"},"change_message_id":"32ae6393705f010932f042df3c78fba43a3403c0","unresolved":false,"context_lines":[{"line_number":38,"context_line":""},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"Use Cases"},{"line_number":41,"context_line":"----------"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"As an openstack operator, I need to find noisy neighbor VMs that affect my"},{"line_number":44,"context_line":"high priority VMs, and migrate them to another node that has no noisy negihbor"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1f013ff3_a81c4dc1","line":41,"range":{"start_line":41,"start_character":9,"end_line":41,"end_character":10},"in_reply_to":"3f044301_fb9b12c6","updated":"2017-05-16 22:12:13.000000000","message":"Done","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":18971,"name":"Vincent Françoise","email":"Vincent.FRANCOISE@b-com.com","username":"v-francoise"},"change_message_id":"b2f59dd24520099133edde598443f42e4aaf68dd","unresolved":false,"context_lines":[{"line_number":80,"context_line":"    \"watcher-priority\") increases by the threshold, then the VM is a noisy"},{"line_number":81,"context_line":"    neighbor."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"  * Look for a node with no Noisy Neighbor issue and migrate the noisy VM"},{"line_number":84,"context_line":"    there."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3f044301_8dd4aaea","line":84,"range":{"start_line":83,"start_character":4,"end_line":84,"end_character":10},"updated":"2017-05-11 18:49:48.000000000","message":"Just as a reminder from the presentation you did. The guy in the audience said that moving the high-priority VM was actually a much better solution and that actually sounds more efficient to me since the live migration will go faster this way since the high-priority VM has lower activity which means lass dirty pages which means less stress on the network.\nAny thoughts?","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":22775,"name":"Prudhvi Rao Shedimbi","email":"prudhvi.rao.shedimbi@intel.com","username":"pshedimb"},"change_message_id":"847390bb661f56c2538cae9b73471319dad7dbe4","unresolved":false,"context_lines":[{"line_number":80,"context_line":"    \"watcher-priority\") increases by the threshold, then the VM is a noisy"},{"line_number":81,"context_line":"    neighbor."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"  * Look for a node with no Noisy Neighbor issue and migrate the noisy VM"},{"line_number":84,"context_line":"    there."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1f013ff3_48f3890b","line":84,"range":{"start_line":83,"start_character":4,"end_line":84,"end_character":10},"in_reply_to":"3f044301_8dd4aaea","updated":"2017-05-16 21:56:42.000000000","message":"I\u0027m still not sure why it is better to move high priority VM. What if a high priority VM is a very heavy application, and moving that heavy application might affect its performance? \nAlso the other issue of moving a high priority VM is that: Once you migrate it to any other node, other VMs on that node can start behaving as noisy neighbors to our high priority VM, and then we might again have to move our high priority instance. This might keep happening for a a few iterations which would lead to performance degradation of our high priority VM.\nWhat do you think?\n\nSusanne, you might want to add something to this?","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":13111,"name":"Hidekazu Nakamura","email":"hidekazuna@gmail.com","username":"hid-nakamura"},"change_message_id":"07b3707f053e87d0a7f4dcd7a63bb6fb27b581bb","unresolved":false,"context_lines":[{"line_number":124,"context_line":"---------------------"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"To enable these IPC and LLC related metrics, latest Intel server with CMT"},{"line_number":127,"context_line":"support is required. Also libvirt 3.0.0 or a later version is required to"},{"line_number":128,"context_line":"gather IPC related metrics."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dfeb2761_4e603702","line":127,"range":{"start_line":127,"start_character":33,"end_line":127,"end_character":50},"updated":"2017-04-04 00:49:02.000000000","message":"Minimum libvirt version in Pike cycle is 1.3.1.\nhttps://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L207\n\nHow can we run tempest test?","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":18971,"name":"Vincent Françoise","email":"Vincent.FRANCOISE@b-com.com","username":"v-francoise"},"change_message_id":"c696037ecbaf2f9aaf439963d7200b092c6bd0e8","unresolved":false,"context_lines":[{"line_number":124,"context_line":"---------------------"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"To enable these IPC and LLC related metrics, latest Intel server with CMT"},{"line_number":127,"context_line":"support is required. Also libvirt 3.0.0 or a later version is required to"},{"line_number":128,"context_line":"gather IPC related metrics."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":14,"id":"bff0334d_29a3f551","line":127,"range":{"start_line":127,"start_character":33,"end_line":127,"end_character":50},"in_reply_to":"dfeb2761_178b3a1f","updated":"2017-04-05 14:11:23.000000000","message":"All strategies should work without metrics. Because it can happen in reality too (new VM is spawned and no measurements were collected). This is the only case we can test within the gate actually, but that\u0027s a good sanity check.","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":22775,"name":"Prudhvi Rao Shedimbi","email":"prudhvi.rao.shedimbi@intel.com","username":"pshedimb"},"change_message_id":"032c386944a637eaeee8847462fead65a91d50f5","unresolved":false,"context_lines":[{"line_number":124,"context_line":"---------------------"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"To enable these IPC and LLC related metrics, latest Intel server with CMT"},{"line_number":127,"context_line":"support is required. Also libvirt 3.0.0 or a later version is required to"},{"line_number":128,"context_line":"gather IPC related metrics."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":14,"id":"dfeb2761_178b3a1f","line":127,"range":{"start_line":127,"start_character":33,"end_line":127,"end_character":50},"in_reply_to":"dfeb2761_4e603702","updated":"2017-04-04 05:37:15.000000000","message":"Yeah, tempest test will be an issue. I\u0027m not sure if there is a workaround for this. We can discuss this on Wednesday team meeting and see what everyone says.","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":11750,"name":"Antoine Cabot","email":"antoine.cabot@b-com.com","username":"antoinecabot"},"change_message_id":"45be61865bd9a4cc087cf811fc661e470e581395","unresolved":false,"context_lines":[{"line_number":160,"context_line":"Testing"},{"line_number":161,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"Unit and funcational test are needed."},{"line_number":164,"context_line":""},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3f044301_fbd2f25b","line":163,"range":{"start_line":163,"start_character":9,"end_line":163,"end_character":20},"updated":"2017-05-09 19:38:56.000000000","message":"s/funcational/functional","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":22775,"name":"Prudhvi Rao Shedimbi","email":"prudhvi.rao.shedimbi@intel.com","username":"pshedimb"},"change_message_id":"32ae6393705f010932f042df3c78fba43a3403c0","unresolved":false,"context_lines":[{"line_number":160,"context_line":"Testing"},{"line_number":161,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":162,"context_line":""},{"line_number":163,"context_line":"Unit and funcational test are needed."},{"line_number":164,"context_line":""},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"Documentation Impact"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1f013ff3_887991fd","line":163,"range":{"start_line":163,"start_character":9,"end_line":163,"end_character":20},"in_reply_to":"3f044301_fbd2f25b","updated":"2017-05-16 22:12:13.000000000","message":"Done","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":11750,"name":"Antoine Cabot","email":"antoine.cabot@b-com.com","username":"antoinecabot"},"change_message_id":"95f77fecf5ee29da0e49a2478d376d75f1e51b08","unresolved":false,"context_lines":[{"line_number":180,"context_line":""},{"line_number":181,"context_line":"None"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":".. list-table:: Revisions"},{"line_number":184,"context_line":"   :header-rows: 1"},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"   * - Release Name"},{"line_number":187,"context_line":"     - Description"},{"line_number":188,"context_line":"   * - Liberty"},{"line_number":189,"context_line":"     - Introduced"}],"source_content_type":"text/x-rst","patch_set":14,"id":"3f044301_dbf3b672","line":189,"range":{"start_line":183,"start_character":0,"end_line":189,"end_character":17},"updated":"2017-05-09 20:35:52.000000000","message":"you don\u0027t need this","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":22775,"name":"Prudhvi Rao Shedimbi","email":"prudhvi.rao.shedimbi@intel.com","username":"pshedimb"},"change_message_id":"32ae6393705f010932f042df3c78fba43a3403c0","unresolved":false,"context_lines":[{"line_number":180,"context_line":""},{"line_number":181,"context_line":"None"},{"line_number":182,"context_line":""},{"line_number":183,"context_line":".. list-table:: Revisions"},{"line_number":184,"context_line":"   :header-rows: 1"},{"line_number":185,"context_line":""},{"line_number":186,"context_line":"   * - Release Name"},{"line_number":187,"context_line":"     - Description"},{"line_number":188,"context_line":"   * - Liberty"},{"line_number":189,"context_line":"     - Introduced"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1f013ff3_687c05eb","line":189,"range":{"start_line":183,"start_character":0,"end_line":189,"end_character":17},"in_reply_to":"3f044301_dbf3b672","updated":"2017-05-16 22:12:13.000000000","message":"Done","commit_id":"fbee8c9d39e11adb61ab74a4894842048a5510ca"},{"author":{"_account_id":6437,"name":"Susanne Balle","email":"sleipnir012@gmail.com","username":"susanne-balle"},"change_message_id":"a7ce0569f786c2339628ef0cb33056f12fa469ad","unresolved":false,"context_lines":[{"line_number":71,"context_line":"    \"watcher-priority\") increases by the threshold, then the VM is a noisy"},{"line_number":72,"context_line":"    neighbor."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"  * Look for a node with no Noisy Neighbor issue and migrate the noisy VM"},{"line_number":75,"context_line":"    there."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"Alternatives"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1f013ff3_4b282333","line":75,"range":{"start_line":74,"start_character":4,"end_line":75,"end_character":10},"updated":"2017-05-16 22:56:39.000000000","message":"Vincent I disagree and I believe it has a lot to do with what metrics and mitigation approaches you have available and the noisy neighbor algorithm you are applying. \n\n* The idea behind using the Intel RDT toolkit is that you can monitor closely the cache allocation and develop an idea for what you define as a victim and an aggressor. The end goal is to eventually be able to isolate the high priority VM on the physical node from aggressor using some of the Cache Allocation tool or other so that aggressors have no impact on the high priority VM. \n\n* Also in many cases I see the high priority VM being a large VM whereas aggressors are smaller dev/batch jobs. Migrating the large VM around will put a lot of use/load on the network and I remember somebody saying that their in-house network couldn\u0027t support that.\n\n* Also in many cases the high priority VMs are not going to be migratable because of the workload they are running. \n\nIn the end this is the strategy that we Intel are interested in for our customers. I hope this help you understand why moving the higher priority VM would not solve our problem.\n\nSusanne\n\nVincent Françoise wrote: May 11 2:49 PM\nJust as a reminder from the presentation you did. The guy in the audience said that moving the high-priority VM was actually a much better solution and that actually sounds more efficient to me since the live migration will go faster this way since the high-priority VM has lower activity which means lass dirty pages which means less stress on the network.\nAny thoughts?","commit_id":"1e8126187ea77b197ec94da3295d098e492dfb3e"},{"author":{"_account_id":6437,"name":"Susanne Balle","email":"sleipnir012@gmail.com","username":"susanne-balle"},"change_message_id":"a7ce0569f786c2339628ef0cb33056f12fa469ad","unresolved":false,"context_lines":[{"line_number":114,"context_line":"Other deployer impact"},{"line_number":115,"context_line":"---------------------"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"To enable these IPC and LLC related metrics, latest Intel server with CMT"},{"line_number":118,"context_line":"support is required. Also libvirt 3.0.0 or a later version is required to"},{"line_number":119,"context_line":"gather IPC related metrics."},{"line_number":120,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"1f013ff3_2b2b9730","line":117,"range":{"start_line":117,"start_character":10,"end_line":117,"end_character":23},"updated":"2017-05-16 22:56:39.000000000","message":"delete since we are only doing ll3 occupancy.","commit_id":"1e8126187ea77b197ec94da3295d098e492dfb3e"},{"author":{"_account_id":13111,"name":"Hidekazu Nakamura","email":"hidekazuna@gmail.com","username":"hid-nakamura"},"change_message_id":"fbf590669b2c90d3637dedfbd7e4d76f4ec6c2d0","unresolved":false,"context_lines":[{"line_number":114,"context_line":"Other deployer impact"},{"line_number":115,"context_line":"---------------------"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"To enable these IPC and LLC related metrics, latest Intel server with CMT"},{"line_number":118,"context_line":"support is required. Also libvirt 3.0.0 or a later version is required to"},{"line_number":119,"context_line":"gather IPC related metrics."},{"line_number":120,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"ff0f0b1f_e98bdabc","line":117,"range":{"start_line":117,"start_character":10,"end_line":117,"end_character":23},"in_reply_to":"1f013ff3_2b2b9730","updated":"2017-05-25 02:45:40.000000000","message":"This comment is still valid.","commit_id":"1e8126187ea77b197ec94da3295d098e492dfb3e"},{"author":{"_account_id":6437,"name":"Susanne Balle","email":"sleipnir012@gmail.com","username":"susanne-balle"},"change_message_id":"a7ce0569f786c2339628ef0cb33056f12fa469ad","unresolved":false,"context_lines":[{"line_number":115,"context_line":"---------------------"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"To enable these IPC and LLC related metrics, latest Intel server with CMT"},{"line_number":118,"context_line":"support is required. Also libvirt 3.0.0 or a later version is required to"},{"line_number":119,"context_line":"gather IPC related metrics."},{"line_number":120,"context_line":""},{"line_number":121,"context_line":"Developer impact"},{"line_number":122,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1f013ff3_4bddc340","line":119,"range":{"start_line":118,"start_character":21,"end_line":119,"end_character":26},"updated":"2017-05-16 22:56:39.000000000","message":"Do we have a dependency on libvirt still? I thought we needed a different version the 3.0.0.","commit_id":"1e8126187ea77b197ec94da3295d098e492dfb3e"}]}