)]}'
{"security-guide/ch_security-services-for-instances.xml":[{"author":{"_account_id":167,"name":"Christian Berendt","email":"berendt@osism.tech","username":"berendt"},"change_message_id":"128fe2087fdc5d012dbcf99dec3c4fbaf171c448","unresolved":false,"context_lines":[{"line_number":216,"context_line":"        \u003c/section\u003e"},{"line_number":217,"context_line":"        \u003csection xml:id\u003d\"security-services-for-instances-idp189488\"\u003e"},{"line_number":218,"context_line":"          \u003ctitle\u003eMigration network\u003c/title\u003e"},{"line_number":219,"context_line":"          \u003cpara\u003eAs a general practice, live migration traffic should be restricted to the \u003clink xlink:href\u003d\"http://docs.openstack.org/security-guide/content/security-boundaries-and-threats.html\"\u003emanagement security domain\u003c/link\u003e. With live migration traffic, due to its plain text nature and the fact that you are transferring the contents of disk and memory of a running instance, it is recommended you further separate live migration traffic onto a dedicated network. Isolating the traffic to a dedicated network can reduce the risk of exposure.\u003c/para\u003e"},{"line_number":220,"context_line":"        \u003c/section\u003e"},{"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"}],"source_content_type":"application/xml","patch_set":4,"id":"baada198_86d8e8f1","line":219,"updated":"2014-07-22 22:32:15.000000000","message":"I don\u0027t know how to reference inside a guide at the moment. But I think using absolute URLs is not correct.","commit_id":"1d598892ab6353ad539cd748085b930815a31ea6"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"5d3c1c570e28cccb50ed3a488547b9c68d5d395e","unresolved":false,"context_lines":[{"line_number":216,"context_line":"        \u003c/section\u003e"},{"line_number":217,"context_line":"        \u003csection xml:id\u003d\"security-services-for-instances-idp189488\"\u003e"},{"line_number":218,"context_line":"          \u003ctitle\u003eMigration network\u003c/title\u003e"},{"line_number":219,"context_line":"          \u003cpara\u003eAs a general practice, live migration traffic should be restricted to the \u003clink xlink:href\u003d\"http://docs.openstack.org/security-guide/content/security-boundaries-and-threats.html\"\u003emanagement security domain\u003c/link\u003e. With live migration traffic, due to its plain text nature and the fact that you are transferring the contents of disk and memory of a running instance, it is recommended you further separate live migration traffic onto a dedicated network. Isolating the traffic to a dedicated network can reduce the risk of exposure.\u003c/para\u003e"},{"line_number":220,"context_line":"        \u003c/section\u003e"},{"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"}],"source_content_type":"application/xml","patch_set":4,"id":"baada198_269d510b","line":219,"in_reply_to":"baada198_86d8e8f1","updated":"2014-07-23 05:29:50.000000000","message":"Use:\n to the management security domain, see \u003cxref linkend\u003d\"security-boundaries-and-threats\" /\u003e","commit_id":"1d598892ab6353ad539cd748085b930815a31ea6"}]}