)]}'
{"security-guide/ch_security-services-for-instances.xml":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"f8d3f7ec2cb0e0873ba58f0ce50266ef52d52e95","unresolved":false,"context_lines":[{"line_number":221,"context_line":"        \u003csection xml:id\u003d\"security-services-for-instances-idp191072\"\u003e"},{"line_number":222,"context_line":"          \u003ctitle\u003eEncrypted live migration\u003c/title\u003e"},{"line_number":223,"context_line":"          \u003cpara\u003eIf there is a sufficient business case for keeping live migration enabled, then libvirtd can provide encrypted tunnels for the live migrations. However, this feature is not currently exposed in either the OpenStack Dashboard or nova-client commands, and can only be accessed through manual configuration of libvirtd. The live migration process then changes to the following high-level steps:"},{"line_number":224,"context_line":"1) Instance data is copied from the hypervisor to libvirtd."},{"line_number":225,"context_line":"2) An encrypted tunnel is created between libvirtd processes on both source and destination hosts."},{"line_number":226,"context_line":"3) Destination libvirtd host copies the instances back to an underlying hypervisor.\u003c/para\u003e"},{"line_number":227,"context_line":"        \u003c/section\u003e"}],"source_content_type":"application/xml","patch_set":2,"id":"baada198_665bc955","line":224,"updated":"2014-07-23 05:31:32.000000000","message":"Please use proper markup here, this could be a procedure or a list.","commit_id":"cec4a60fb2933290d71e2a455aada7741a2b062d"},{"author":{"_account_id":167,"name":"Christian Berendt","email":"berendt@osism.tech","username":"berendt"},"change_message_id":"fa2fc9f7811ccfa0dcf831692f608ee6a1b758e0","unresolved":false,"context_lines":[{"line_number":221,"context_line":"        \u003csection xml:id\u003d\"security-services-for-instances-idp191072\"\u003e"},{"line_number":222,"context_line":"          \u003ctitle\u003eEncrypted live migration\u003c/title\u003e"},{"line_number":223,"context_line":"          \u003cpara\u003eIf there is a sufficient business case for keeping live migration enabled, then libvirtd can provide encrypted tunnels for the live migrations. However, this feature is not currently exposed in either the OpenStack Dashboard or nova-client commands, and can only be accessed through manual configuration of libvirtd. The live migration process then changes to the following high-level steps:"},{"line_number":224,"context_line":"1) Instance data is copied from the hypervisor to libvirtd."},{"line_number":225,"context_line":"2) An encrypted tunnel is created between libvirtd processes on both source and destination hosts."},{"line_number":226,"context_line":"3) Destination libvirtd host copies the instances back to an underlying hypervisor.\u003c/para\u003e"},{"line_number":227,"context_line":"        \u003c/section\u003e"}],"source_content_type":"application/xml","patch_set":2,"id":"baada198_06ecd891","line":224,"updated":"2014-07-22 22:32:55.000000000","message":"This should be converted to a docbook listing.","commit_id":"cec4a60fb2933290d71e2a455aada7741a2b062d"}]}