)]}'
{"doc/source/user/flavors.rst":[{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"1b591e8630d13a44bd4c6234bbf355da27ae9e02","unresolved":false,"context_lines":[{"line_number":606,"context_line":""},{"line_number":607,"context_line":"  Valid PCI-NUMA-POLICY values are:"},{"line_number":608,"context_line":""},{"line_number":609,"context_line":"  - ``required``: Enforce NUMA affinity for devices. Devices with the wrong"},{"line_number":610,"context_line":"    NUMA affinity or with no NUMA affinity will not be used."},{"line_number":611,"context_line":"  - ``legacy``: (default) Enforce NUMA affinity for devices that provide it. If"},{"line_number":612,"context_line":"    strict NUMA affinity is not possible, fallback to devices that do not"},{"line_number":613,"context_line":"    provide NUMA affinity information."}],"source_content_type":"text/x-rst","patch_set":2,"id":"df87a7cf_33cf8080","line":610,"range":{"start_line":609,"start_character":66,"end_line":610,"end_character":17},"updated":"2017-12-15 00:18:25.000000000","message":"nit: Does readers understand what the `wrong` NUMA affinity is? I prefer `different NUMA affinity` if this `wrong` means `different`.","commit_id":"9dc23789d35093f8ba1c4a8c2262ca70f3055f28"},{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"1b591e8630d13a44bd4c6234bbf355da27ae9e02","unresolved":false,"context_lines":[{"line_number":613,"context_line":"    provide NUMA affinity information."},{"line_number":614,"context_line":"  - ``preferred``: Enforce NUMA affinity on a best-effort basis. If strict NUMA"},{"line_number":615,"context_line":"    affinity is not possible, fallback to devices that do not provide NUMA"},{"line_number":616,"context_line":"    affinity information. If this is still not possible, fallback to to devices"},{"line_number":617,"context_line":"    with different NUMA affinity as required."},{"line_number":618,"context_line":""},{"line_number":619,"context_line":"Secure Boot"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df87a7cf_93868c13","line":616,"range":{"start_line":616,"start_character":69,"end_line":616,"end_character":71},"updated":"2017-12-15 00:18:25.000000000","message":"duplication","commit_id":"9dc23789d35093f8ba1c4a8c2262ca70f3055f28"},{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"1b591e8630d13a44bd4c6234bbf355da27ae9e02","unresolved":false,"context_lines":[{"line_number":614,"context_line":"  - ``preferred``: Enforce NUMA affinity on a best-effort basis. If strict NUMA"},{"line_number":615,"context_line":"    affinity is not possible, fallback to devices that do not provide NUMA"},{"line_number":616,"context_line":"    affinity information. If this is still not possible, fallback to to devices"},{"line_number":617,"context_line":"    with different NUMA affinity as required."},{"line_number":618,"context_line":""},{"line_number":619,"context_line":"Secure Boot"},{"line_number":620,"context_line":"  When your Compute services use the Hyper-V hypervisor, you can enable secure"}],"source_content_type":"text/x-rst","patch_set":2,"id":"df87a7cf_b3895027","line":617,"range":{"start_line":617,"start_character":9,"end_line":617,"end_character":32},"updated":"2017-12-15 00:18:25.000000000","message":"Yup, this makes sense.","commit_id":"9dc23789d35093f8ba1c4a8c2262ca70f3055f28"}]}