)]}'
{"doc/source/admin/useful-image-properties.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"f10a3b474ae7df3fcbfb941c2b83b8e72c306605","unresolved":false,"context_lines":[{"line_number":347,"context_line":"     - ``virtio``, or other supported device."},{"line_number":348,"context_line":"   * - libvirt API driver"},{"line_number":349,"context_line":"     - ``hw_time_hpet``"},{"line_number":350,"context_line":"     - Adds support for the High Precision Event Timer (HPET) for x86 guests"},{"line_number":351,"context_line":"       in the libvirt driver when hypervisor_type is qemu. The timer can be"},{"line_number":352,"context_line":"       set by setting ``hw_time_hpet\u003dtrue``. By default HPET remains turned"},{"line_number":353,"context_line":"       off. When it is turned on the HPET is activated in libvirt."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_3c1400ea","line":350,"range":{"start_line":350,"start_character":66,"end_line":350,"end_character":76},"updated":"2018-11-20 22:42:49.000000000","message":"Would probably be best to explicitly mention the ``architecture`` property for this.","commit_id":"be72b4f06a054e01174601017c8e5ec2d2659a62"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"f10a3b474ae7df3fcbfb941c2b83b8e72c306605","unresolved":false,"context_lines":[{"line_number":348,"context_line":"   * - libvirt API driver"},{"line_number":349,"context_line":"     - ``hw_time_hpet``"},{"line_number":350,"context_line":"     - Adds support for the High Precision Event Timer (HPET) for x86 guests"},{"line_number":351,"context_line":"       in the libvirt driver when hypervisor_type is qemu. The timer can be"},{"line_number":352,"context_line":"       set by setting ``hw_time_hpet\u003dtrue``. By default HPET remains turned"},{"line_number":353,"context_line":"       off. When it is turned on the HPET is activated in libvirt."},{"line_number":354,"context_line":"     - ``true`` or ``false``"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_dc238c56","line":351,"range":{"start_line":351,"start_character":34,"end_line":351,"end_character":57},"updated":"2018-11-20 22:42:49.000000000","message":"``hypervisor_type\u003dqemu``","commit_id":"be72b4f06a054e01174601017c8e5ec2d2659a62"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"0e5ef4f8e80715a4f5d2751adc350012182c3cd5","unresolved":false,"context_lines":[{"line_number":348,"context_line":"   * - libvirt API driver"},{"line_number":349,"context_line":"     - ``hw_time_hpet``"},{"line_number":350,"context_line":"     - Adds support for the High Precision Event Timer (HPET) for x86 guests"},{"line_number":351,"context_line":"       in the libvirt driver when ``hypervisor_type\u003dqemu`` and"},{"line_number":352,"context_line":"       ``architecture\u003di686`` or ``architecture\u003dx86_64``. The timer can be"},{"line_number":353,"context_line":"       enabled by setting ``hw_time_hpet\u003dtrue``. By default HPET remains"},{"line_number":354,"context_line":"       disabled."},{"line_number":355,"context_line":"     - ``true`` or ``false`` (default)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_9cbf54ab","line":352,"range":{"start_line":351,"start_character":35,"end_line":352,"end_character":55},"updated":"2018-11-20 22:57:08.000000000","message":"This is (at least) the second image property that is functional only when specific other properties are present with particular values.  Do we need to add a \u0027Dependencies\u0027 column to this chart?  (The other property I\u0027m thinking of is hw_cpu_thread_policy.)","commit_id":"59a5994a18100c271fd49d0fcf9c18b3c0ad9d21"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b5a8f5e0926104ca241361ffa7a59fc1897174c3","unresolved":false,"context_lines":[{"line_number":348,"context_line":"   * - libvirt API driver"},{"line_number":349,"context_line":"     - ``hw_time_hpet``"},{"line_number":350,"context_line":"     - Adds support for the High Precision Event Timer (HPET) for x86 guests"},{"line_number":351,"context_line":"       in the libvirt driver when ``hypervisor_type\u003dqemu`` and"},{"line_number":352,"context_line":"       ``architecture\u003di686`` or ``architecture\u003dx86_64``. The timer can be"},{"line_number":353,"context_line":"       enabled by setting ``hw_time_hpet\u003dtrue``. By default HPET remains"},{"line_number":354,"context_line":"       disabled."},{"line_number":355,"context_line":"     - ``true`` or ``false`` (default)"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_0fcea8b5","line":352,"range":{"start_line":351,"start_character":35,"end_line":352,"end_character":55},"in_reply_to":"3f79a3b5_9cbf54ab","updated":"2018-11-21 00:01:17.000000000","message":"That might be useful, but up to you guys. I know in discussing the nova spec for this, there was initially some talk of having the compute API validate that if creating a sever with this hw_time_hpet image property that hypervisor_type and architecture would also need to be set, but I argued that\u0027s a bit clunky by the time you get to the compute API, and really it\u0027s the image API that should be validating stuff like that, sort of like with metadefs, but at the same time, that\u0027s likely not going to be something that is going to get encoded in the image API and would be hard to maintain, so we\u0027re just kind of doing what we\u0027ve always done and validate it in the compute driver when we get there to check the property. In this case, it\u0027s a property that will be seldom used so I didn\u0027t feel the need to bend over backward in validating it in the API.","commit_id":"59a5994a18100c271fd49d0fcf9c18b3c0ad9d21"}]}