)]}'
{"security-guide/section_hardening-the-virtualization-layers.xml":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"fe6e82adaadf88bc5be20300a6866df68acb43f9","unresolved":false,"context_lines":[{"line_number":354,"context_line":"          identifies image files on disk, allowing for the SELinux"},{"line_number":355,"context_line":"          policy to restrict access. When a KVM-based Compute image is"},{"line_number":356,"context_line":"          powered on, sVirt appends a random numerical identifier to"},{"line_number":357,"context_line":"          the image. sVirt is capable of assigning numeric identifiers "},{"line_number":358,"context_line":"          to a maximum of 524,288 virtual machines per hypervisor node, "},{"line_number":359,"context_line":"          however most OpenStack deployments are highly unlikely to encounter "},{"line_number":360,"context_line":"          this limitation.\u003c/para\u003e"}],"source_content_type":"application/xml","patch_set":2,"id":"fa98f980_13584389","line":357,"updated":"2014-09-11 12:30:42.000000000","message":"Looks like you have end-of-line whitespace here and in the other lines - this breaks the niceness gate.","commit_id":"1a57e2fb461976f12f66b3a1b259d5d951190d4e"}]}