)]}'
{"doc/source/admin/cpu-topologies.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"9cb36dafd8c63af802b7c6020c8e0cc101356b47","unresolved":false,"context_lines":[{"line_number":298,"context_line":""},{"line_number":299,"context_line":"   $ openstack flavor set [FLAVOR_ID] \\"},{"line_number":300,"context_line":"     --property resources:PCPU\u003dN \\"},{"line_number":301,"context_line":"     --property trait:HW_CPU_HYPERTHREADING\u003drequired"},{"line_number":302,"context_line":""},{"line_number":303,"context_line":"For other workloads where performance is impacted by contention for resources,"},{"line_number":304,"context_line":"you can request hosts **without** SMT. To configure this, run:"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3fa7e38b_41f4915b","line":301,"range":{"start_line":301,"start_character":4,"end_line":301,"end_character":52},"updated":"2019-09-23 01:30:55.000000000","message":"do we want to all out that unlike the hw:cpu_treads_policy approch the traits based approch will work for non pinned instance too. the cpu_treads_policy was original intened to work without pinning anyway so this is a good thing but people object to it as it would add complexity. in this case its more complext to not support it for both so i think it makes sense to document that you can use the HW_CPU_HYPERTHREADING trait to avoid or select SMT hosts in general.","commit_id":"2e7bcbe16acaee3dbb5da0d1cce4651496a4c61e"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"9cb36dafd8c63af802b7c6020c8e0cc101356b47","unresolved":false,"context_lines":[{"line_number":329,"context_line":"     --property hw:cpu_policy\u003ddedicated \\"},{"line_number":330,"context_line":"     --property hw:cpu_thread_policy\u003dprefer"},{"line_number":331,"context_line":""},{"line_number":332,"context_line":"This does not utilize traits and, as such, there is no trait-based equivalent."},{"line_number":333,"context_line":""},{"line_number":334,"context_line":".. note::"},{"line_number":335,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3fa7e38b_61e50da8","line":332,"range":{"start_line":332,"start_character":0,"end_line":332,"end_character":78},"updated":"2019-09-23 01:30:55.000000000","message":"well this is exeactly equivalent to not specifying a trait and requesting a resouces","commit_id":"2e7bcbe16acaee3dbb5da0d1cce4651496a4c61e"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"a23029aa8b1cda5f6084bee21d2d8e15432523c0","unresolved":false,"context_lines":[{"line_number":527,"context_line":"Configuring libvirt compute nodes for CPU pinning"},{"line_number":528,"context_line":"-------------------------------------------------"},{"line_number":529,"context_line":""},{"line_number":530,"context_line":".. versionchanged:: 20.0.0"},{"line_number":531,"context_line":""},{"line_number":532,"context_line":"   Prior to 20.0.0 (Train), it was not necessary to explicitly configure hosts"},{"line_number":533,"context_line":"   for pinned instances. However, it was not possible to place pinned instances"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_6d5ce9ec","line":530,"updated":"2019-09-25 13:45:29.000000000","message":"*nods*","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"22c68a2a315c3f1d71649333e5771a3bfc4d6fd7","unresolved":false,"context_lines":[{"line_number":531,"context_line":""},{"line_number":532,"context_line":"   Prior to 20.0.0 (Train), it was not necessary to explicitly configure hosts"},{"line_number":533,"context_line":"   for pinned instances. However, it was not possible to place pinned instances"},{"line_number":534,"context_line":"   on the same host as unpinned CPUs, which typically meant hosts had to be"},{"line_number":535,"context_line":"   grouped into host aggregates. If this was not done, unpinned instances would"},{"line_number":536,"context_line":"   continue floating across all enabled host CPUs, even those that some"},{"line_number":537,"context_line":"   instance CPUs were pinned to. Starting in 20.0.0, it is necessary to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_42ba176e","line":534,"range":{"start_line":534,"start_character":32,"end_line":534,"end_character":36},"updated":"2019-09-25 15:09:48.000000000","message":"instances","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"22c68a2a315c3f1d71649333e5771a3bfc4d6fd7","unresolved":false,"context_lines":[{"line_number":539,"context_line":""},{"line_number":540,"context_line":"Nova treats host CPUs used for unpinned instances differently from those used"},{"line_number":541,"context_line":"by pinned instances. The former are tracked in placement using the ``VCPU``"},{"line_number":542,"context_line":"resource type and can be overallocated, while the latter are tracked using the"},{"line_number":543,"context_line":"``PCPU`` resource type. By default, nova will report all host CPUs as ``VCPU``"},{"line_number":544,"context_line":"inventory, however, this can be configured using the"},{"line_number":545,"context_line":":oslo.config:option:`compute.cpu_shared_set` config option, to specify which"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_a2a8ab1f","line":542,"range":{"start_line":542,"start_character":9,"end_line":542,"end_character":13},"updated":"2019-09-25 15:09:48.000000000","message":"class","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"22c68a2a315c3f1d71649333e5771a3bfc4d6fd7","unresolved":false,"context_lines":[{"line_number":540,"context_line":"Nova treats host CPUs used for unpinned instances differently from those used"},{"line_number":541,"context_line":"by pinned instances. The former are tracked in placement using the ``VCPU``"},{"line_number":542,"context_line":"resource type and can be overallocated, while the latter are tracked using the"},{"line_number":543,"context_line":"``PCPU`` resource type. By default, nova will report all host CPUs as ``VCPU``"},{"line_number":544,"context_line":"inventory, however, this can be configured using the"},{"line_number":545,"context_line":":oslo.config:option:`compute.cpu_shared_set` config option, to specify which"},{"line_number":546,"context_line":"host CPUs should be used for ``VCPU`` inventory, and the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_8269eff9","line":543,"range":{"start_line":543,"start_character":18,"end_line":543,"end_character":22},"updated":"2019-09-25 15:09:48.000000000","message":"class","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"22c68a2a315c3f1d71649333e5771a3bfc4d6fd7","unresolved":false,"context_lines":[{"line_number":541,"context_line":"by pinned instances. The former are tracked in placement using the ``VCPU``"},{"line_number":542,"context_line":"resource type and can be overallocated, while the latter are tracked using the"},{"line_number":543,"context_line":"``PCPU`` resource type. By default, nova will report all host CPUs as ``VCPU``"},{"line_number":544,"context_line":"inventory, however, this can be configured using the"},{"line_number":545,"context_line":":oslo.config:option:`compute.cpu_shared_set` config option, to specify which"},{"line_number":546,"context_line":"host CPUs should be used for ``VCPU`` inventory, and the"},{"line_number":547,"context_line":":oslo.config:option:`compute.cpu_dedicated_set` config option, to specify which"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_426f77fb","line":544,"range":{"start_line":544,"start_character":9,"end_line":544,"end_character":12},"updated":"2019-09-25 15:09:48.000000000","message":"; h\n\nor\n\n. H","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"a23029aa8b1cda5f6084bee21d2d8e15432523c0","unresolved":false,"context_lines":[{"line_number":548,"context_line":"host CPUs should be used for ``PCPU`` inventory."},{"line_number":549,"context_line":""},{"line_number":550,"context_line":"Consider a compute node with a total of 24 host physical CPU cores with"},{"line_number":551,"context_line":"hyperthreading enabled. The operator wishes to reserve 1 physical CPU core and"},{"line_number":552,"context_line":"its thread sibling for host processing (not for guest instance use)."},{"line_number":553,"context_line":"Furthermore, the operator wishes to use 8 host physical CPU cores and their"},{"line_number":554,"context_line":"thread siblings for dedicated guest CPU resources. The remaining 15 host"},{"line_number":555,"context_line":"physical CPU cores and their thread siblings will be used for shared guest vCPU"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_eded39b7","line":552,"range":{"start_line":551,"start_character":25,"end_line":552,"end_character":68},"updated":"2019-09-25 13:45:29.000000000","message":"all good, you should maybe say that the operator wants to reserve the #0 pCPU.","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"22c68a2a315c3f1d71649333e5771a3bfc4d6fd7","unresolved":false,"context_lines":[{"line_number":562,"context_line":"    cpu_allocation_ratio\u003d8.0"},{"line_number":563,"context_line":""},{"line_number":564,"context_line":"    [compute]"},{"line_number":565,"context_line":"    cpu_dedicated_set\u003d2-17"},{"line_number":566,"context_line":"    cpu_shared_set\u003d18-47"},{"line_number":567,"context_line":""},{"line_number":568,"context_line":"The virt driver will construct a provider tree containing a single resource"},{"line_number":569,"context_line":"provider representing the compute node and report inventory of ``PCPU`` and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_020c1f3f","line":566,"range":{"start_line":565,"start_character":0,"end_line":566,"end_character":24},"updated":"2019-09-25 15:09:48.000000000","message":"worth pointing out somewhere below that this means 0,1 are the \"reserved\" ones","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"22c68a2a315c3f1d71649333e5771a3bfc4d6fd7","unresolved":false,"context_lines":[{"line_number":586,"context_line":"            allocation_ratio: 8.0"},{"line_number":587,"context_line":""},{"line_number":588,"context_line":"Instances using the ``dedicated`` CPU policy or an explicit ``PCPU`` resource"},{"line_number":589,"context_line":"request, ``PCPU`` inventory will be consumed. Instances using the ``shared``"},{"line_number":590,"context_line":"CPU policy, meanwhile, will consume ``VCPU`` inventory."},{"line_number":591,"context_line":""},{"line_number":592,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_22111b5e","line":589,"range":{"start_line":589,"start_character":7,"end_line":589,"end_character":44},"updated":"2019-09-25 15:09:48.000000000","message":"will consume ``PCPU`` inventory","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"}],"doc/source/user/flavors.rst":[{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"a23029aa8b1cda5f6084bee21d2d8e15432523c0","unresolved":false,"context_lines":[{"line_number":563,"context_line":""},{"line_number":564,"context_line":"     Document the required steps to configure hosts and guests. There are a lot"},{"line_number":565,"context_line":"     of things necessary, from isolating hosts and configuring the"},{"line_number":566,"context_line":"     ``[compute] cpu_dedicated_set`` nova configuration option on the host, to"},{"line_number":567,"context_line":"     choosing a correctly configured guest image."},{"line_number":568,"context_line":""},{"line_number":569,"context_line":"  .. important::"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3fa7e38b_cd515ddb","line":566,"updated":"2019-09-25 13:45:29.000000000","message":"maybe you should tell that the option is only there by Train","commit_id":"50e60401edb03b967519f9d8e063e9e75bf3e2f8"}]}