)]}'
{"doc/source/admin/configuration/schedulers.rst":[{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"4362c4c9a1cdb74d7ebaf31c4b4d53724627a193","unresolved":false,"context_lines":[{"line_number":1465,"context_line":"by configuring flavors with"},{"line_number":1466,"context_line":":ref:`Required traits \u003cextra-specs-required-traits\u003e` or"},{"line_number":1467,"context_line":":ref:`Forbidden traits \u003cextra-specs-forbidden-traits\u003e`. For example, if you"},{"line_number":1468,"context_line":"have a host aggregate with a set of compute nodes that support multi-attach"},{"line_number":1469,"context_line":"volumes, you can restrict a flavor to that aggregate by adding the"},{"line_number":1470,"context_line":"``trait:COMPUTE_VOLUME_MULTI_ATTACH\u003drequired`` extra spec to the flavor and"},{"line_number":1471,"context_line":"then restrict the flavor to the aggregate"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_a1f12698","line":1468,"range":{"start_line":1468,"start_character":5,"end_line":1468,"end_character":21},"updated":"2019-03-19 07:29:12.000000000","message":"Can I ask why this case related to host aggregate? without aggregate, we also can choice correct host, right?","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"eddbe17257e26b7650d02920f00eb55e1679c3ac","unresolved":false,"context_lines":[{"line_number":1465,"context_line":"by configuring flavors with"},{"line_number":1466,"context_line":":ref:`Required traits \u003cextra-specs-required-traits\u003e` or"},{"line_number":1467,"context_line":":ref:`Forbidden traits \u003cextra-specs-forbidden-traits\u003e`. For example, if you"},{"line_number":1468,"context_line":"have a host aggregate with a set of compute nodes that support multi-attach"},{"line_number":1469,"context_line":"volumes, you can restrict a flavor to that aggregate by adding the"},{"line_number":1470,"context_line":"``trait:COMPUTE_VOLUME_MULTI_ATTACH\u003drequired`` extra spec to the flavor and"},{"line_number":1471,"context_line":"then restrict the flavor to the aggregate"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_d366712a","line":1468,"range":{"start_line":1468,"start_character":5,"end_line":1468,"end_character":21},"in_reply_to":"5fc1f717_4055d3f9","updated":"2019-03-20 02:48:44.000000000","message":"ok, I see now, you want to show this is another option for that usecase.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a91c3809be459b8e874540ac89193ba7ae144283","unresolved":false,"context_lines":[{"line_number":1465,"context_line":"by configuring flavors with"},{"line_number":1466,"context_line":":ref:`Required traits \u003cextra-specs-required-traits\u003e` or"},{"line_number":1467,"context_line":":ref:`Forbidden traits \u003cextra-specs-forbidden-traits\u003e`. For example, if you"},{"line_number":1468,"context_line":"have a host aggregate with a set of compute nodes that support multi-attach"},{"line_number":1469,"context_line":"volumes, you can restrict a flavor to that aggregate by adding the"},{"line_number":1470,"context_line":"``trait:COMPUTE_VOLUME_MULTI_ATTACH\u003drequired`` extra spec to the flavor and"},{"line_number":1471,"context_line":"then restrict the flavor to the aggregate"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_4055d3f9","line":1468,"range":{"start_line":1468,"start_character":5,"end_line":1468,"end_character":21},"in_reply_to":"5fc1f717_a1f12698","updated":"2019-03-19 14:05:10.000000000","message":"Let\u0027s say you have a mixed hypervisor deployment, or a set of computes that are not yet upgraded, so they don\u0027t support multiattach volumes. You could roll out the multiattach volume support feature on a subset of the deployment by creating an aggregate and then restricting flavors which are advertised as working for multiattach volumes to that aggregate. It\u0027s a bit of a stretch but it is a use case, along with any other use case for the AggregateInstanceExtraSpecsFilter. But as you say, it can also be used without aggregates, which is why I referenced this from the ComputeCapabilitiesFilter section.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":2394,"name":"Adam Spiers","email":"aspiers@suse.com","username":"adam.spiers"},"change_message_id":"8043c2d448b8b3cc17d2e291ab2190e5ffa66711","unresolved":false,"context_lines":[{"line_number":1496,"context_line":"  | HW_CPU_X86_SVM                        |"},{"line_number":1497,"context_line":"  +---------------------------------------+"},{"line_number":1498,"context_line":""},{"line_number":1499,"context_line":"**Rules**"},{"line_number":1500,"context_line":""},{"line_number":1501,"context_line":"There are some rules associated with capability-defined traits."},{"line_number":1502,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_c4a4894d","line":1499,"updated":"2019-03-18 20:13:24.000000000","message":"I suggest making this an \u003ch3\u003e for consistency with the rest of the file, by underlining with hyphens.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":2394,"name":"Adam Spiers","email":"aspiers@suse.com","username":"adam.spiers"},"change_message_id":"935f65192249beb55d29be642b4b96a9e10a6a62","unresolved":false,"context_lines":[{"line_number":1496,"context_line":"  | HW_CPU_X86_SVM                        |"},{"line_number":1497,"context_line":"  +---------------------------------------+"},{"line_number":1498,"context_line":""},{"line_number":1499,"context_line":"**Rules**"},{"line_number":1500,"context_line":""},{"line_number":1501,"context_line":"There are some rules associated with capability-defined traits."},{"line_number":1502,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_dfb0d445","line":1499,"in_reply_to":"5fc1f717_c4a4894d","updated":"2019-03-18 20:14:14.000000000","message":"FWIW, here is the official guidance:\n\nhttps://docs.openstack.org/doc-contrib-guide/rst-conv/titles.html#cg-titles","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a91c3809be459b8e874540ac89193ba7ae144283","unresolved":false,"context_lines":[{"line_number":1496,"context_line":"  | HW_CPU_X86_SVM                        |"},{"line_number":1497,"context_line":"  +---------------------------------------+"},{"line_number":1498,"context_line":""},{"line_number":1499,"context_line":"**Rules**"},{"line_number":1500,"context_line":""},{"line_number":1501,"context_line":"There are some rules associated with capability-defined traits."},{"line_number":1502,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_6081ef4a","line":1499,"in_reply_to":"5fc1f717_dfb0d445","updated":"2019-03-19 14:05:10.000000000","message":"I intentionally didn\u0027t make this a sub-section since I didn\u0027t really think nesting that far was necessary and it\u0027s such a generic title that it would be kind of weird to show up as the only sub-section in here with the name \"Rules\".","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":2394,"name":"Adam Spiers","email":"aspiers@suse.com","username":"adam.spiers"},"change_message_id":"8043c2d448b8b3cc17d2e291ab2190e5ffa66711","unresolved":false,"context_lines":[{"line_number":1506,"context_line":"   :oslo.config:option:`update_resources_interval`."},{"line_number":1507,"context_line":""},{"line_number":1508,"context_line":"2. The compute service will not remove any custom traits set on the resource"},{"line_number":1509,"context_line":"   provider externally. This would be the ``CUSTOM_IMAGE_TYPE_RBD`` trait in"},{"line_number":1510,"context_line":"   the example above."},{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_df3d34c4","line":1509,"range":{"start_line":1509,"start_character":22,"end_line":1509,"end_character":37},"updated":"2019-03-18 20:13:24.000000000","message":"Very small nit: this wording could perhaps be misconstrued as implying that CUSTOM_IMAGE_TYPE_RBD is the *only* such custom trait.  Hopefully the \"any\" in the previous sentence would preempt such a misinterpretation; however to be safe I think it would be a *tiny* bit clearer to write something like:\n\n\u003e [...] provider externally, such as the ``CUSTOM_IMAGE_TYPE_RBD`` trait in the example above.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"ad4b303f5935ca76f40dccc830886a3ffa32c037","unresolved":false,"context_lines":[{"line_number":1506,"context_line":"   :oslo.config:option:`update_resources_interval`."},{"line_number":1507,"context_line":""},{"line_number":1508,"context_line":"2. The compute service will not remove any custom traits set on the resource"},{"line_number":1509,"context_line":"   provider externally. This would be the ``CUSTOM_IMAGE_TYPE_RBD`` trait in"},{"line_number":1510,"context_line":"   the example above."},{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_c0aa2370","line":1509,"range":{"start_line":1509,"start_character":22,"end_line":1509,"end_character":37},"in_reply_to":"5fc1f717_20d8c77d","updated":"2019-03-19 14:13:12.000000000","message":"Done","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a91c3809be459b8e874540ac89193ba7ae144283","unresolved":false,"context_lines":[{"line_number":1506,"context_line":"   :oslo.config:option:`update_resources_interval`."},{"line_number":1507,"context_line":""},{"line_number":1508,"context_line":"2. The compute service will not remove any custom traits set on the resource"},{"line_number":1509,"context_line":"   provider externally. This would be the ``CUSTOM_IMAGE_TYPE_RBD`` trait in"},{"line_number":1510,"context_line":"   the example above."},{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_20d8c77d","line":1509,"range":{"start_line":1509,"start_character":22,"end_line":1509,"end_character":37},"in_reply_to":"5fc1f717_df3d34c4","updated":"2019-03-19 14:05:10.000000000","message":"Thanks, I\u0027ll either follow up or respin with that suggested wording if I have a reason to respin.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"4362c4c9a1cdb74d7ebaf31c4b4d53724627a193","unresolved":false,"context_lines":[{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"},{"line_number":1513,"context_line":"   for example by running ``openstack resource provider trait delete \u003crp_uuid\u003e``,"},{"line_number":1514,"context_line":"   the compute service will add its traits again on restart or SIGHUP."},{"line_number":1515,"context_line":""},{"line_number":1516,"context_line":"4. If a compute trait is set on the resource provider externally which is not"},{"line_number":1517,"context_line":"   supported by the driver, for example by adding the ``COMPUTE_VOLUME_EXTEND``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_01f59a83","line":1514,"range":{"start_line":1514,"start_character":52,"end_line":1514,"end_character":69},"updated":"2019-03-19 07:29:12.000000000","message":"also periodic task?","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"5d575fb30a324113e3940170b77d48fc38f47e07","unresolved":false,"context_lines":[{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"},{"line_number":1513,"context_line":"   for example by running ``openstack resource provider trait delete \u003crp_uuid\u003e``,"},{"line_number":1514,"context_line":"   the compute service will add its traits again on restart or SIGHUP."},{"line_number":1515,"context_line":""},{"line_number":1516,"context_line":"4. If a compute trait is set on the resource provider externally which is not"},{"line_number":1517,"context_line":"   supported by the driver, for example by adding the ``COMPUTE_VOLUME_EXTEND``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_2079a72e","line":1514,"range":{"start_line":1514,"start_character":52,"end_line":1514,"end_character":69},"in_reply_to":"5fc1f717_00490b31","updated":"2019-03-19 14:12:03.000000000","message":"I updated the commit message to note this.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a91c3809be459b8e874540ac89193ba7ae144283","unresolved":false,"context_lines":[{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"},{"line_number":1513,"context_line":"   for example by running ``openstack resource provider trait delete \u003crp_uuid\u003e``,"},{"line_number":1514,"context_line":"   the compute service will add its traits again on restart or SIGHUP."},{"line_number":1515,"context_line":""},{"line_number":1516,"context_line":"4. If a compute trait is set on the resource provider externally which is not"},{"line_number":1517,"context_line":"   supported by the driver, for example by adding the ``COMPUTE_VOLUME_EXTEND``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_00490b31","line":1514,"range":{"start_line":1514,"start_character":52,"end_line":1514,"end_character":69},"in_reply_to":"5fc1f717_01f59a83","updated":"2019-03-19 14:05:10.000000000","message":"I found out yesterday that it depends on the [compute]/resource_provider_association_refresh configuration option. If that is set to 0 it is effectively disabled and the periodic task will not update the traits removed externally. Eric said that long-term he thinks we\u0027ll be deprecating the resource_provider_association_refresh option so I opted to not mention here to avoid confusion about \"well it works this way if you have this configuration set otherwise it works some other way\". It\u0027s easiest to just say \"restart or SIGHUP\" which will catch both cases regardless of resource_provider_association_refresh configuration.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":5754,"name":"Alex Xu","email":"hejie.xu@intel.com","username":"xuhj"},"change_message_id":"eddbe17257e26b7650d02920f00eb55e1679c3ac","unresolved":false,"context_lines":[{"line_number":1511,"context_line":""},{"line_number":1512,"context_line":"3. If compute-owned traits are removed from the resource provider externally,"},{"line_number":1513,"context_line":"   for example by running ``openstack resource provider trait delete \u003crp_uuid\u003e``,"},{"line_number":1514,"context_line":"   the compute service will add its traits again on restart or SIGHUP."},{"line_number":1515,"context_line":""},{"line_number":1516,"context_line":"4. If a compute trait is set on the resource provider externally which is not"},{"line_number":1517,"context_line":"   supported by the driver, for example by adding the ``COMPUTE_VOLUME_EXTEND``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_137cf9b3","line":1514,"range":{"start_line":1514,"start_character":52,"end_line":1514,"end_character":69},"in_reply_to":"5fc1f717_2079a72e","updated":"2019-03-20 02:48:44.000000000","message":"Thanks, I got it.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":2394,"name":"Adam Spiers","email":"aspiers@suse.com","username":"adam.spiers"},"change_message_id":"8043c2d448b8b3cc17d2e291ab2190e5ffa66711","unresolved":false,"context_lines":[{"line_number":1520,"context_line":""},{"line_number":1521,"context_line":"5. Compute capability traits are standard traits defined in the `os-traits`_"},{"line_number":1522,"context_line":"   library."},{"line_number":1523,"context_line":""},{"line_number":1524,"context_line":".. _os-traits: http://git.openstack.org/cgit/openstack/os-traits/tree/os_traits/compute"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_042291b9","line":1523,"updated":"2019-03-18 20:13:24.000000000","message":"Is it worth embedding the Venn diagram here, or adding it somewhere else and linking from here?\n\nhttps://pasteboard.co/I3iqqNm.jpg\n\nIf so I will happily provide the original SVG.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"a91c3809be459b8e874540ac89193ba7ae144283","unresolved":false,"context_lines":[{"line_number":1520,"context_line":""},{"line_number":1521,"context_line":"5. Compute capability traits are standard traits defined in the `os-traits`_"},{"line_number":1522,"context_line":"   library."},{"line_number":1523,"context_line":""},{"line_number":1524,"context_line":".. _os-traits: http://git.openstack.org/cgit/openstack/os-traits/tree/os_traits/compute"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5fc1f717_405873f9","line":1523,"in_reply_to":"5fc1f717_042291b9","updated":"2019-03-19 14:05:10.000000000","message":"I thought about it, but figured it might be more confusing than it\u0027s worth for people that are not intimately familiar with the code.","commit_id":"3d08a746847bf99bdbdbb4d184101810cc51af1a"}]}