)]}'
{"doc/source/deploy/security.rst":[{"author":{"_account_id":12356,"name":"Vladyslav Drok","email":"vdrok@mirantis.com","username":"vdrok"},"change_message_id":"d1b670d8022de8b78eccf4b59a2645e61f095810","unresolved":false,"context_lines":[{"line_number":55,"context_line":"  - By default, the Bare Metal service provisions all nodes on a \"flat\""},{"line_number":56,"context_line":"    network, and does not take any precautions to avoid or prevent interaction"},{"line_number":57,"context_line":"    between tenants."},{"line_number":58,"context_line":"  - This can be addressed by integration with the OpenStack Identity, Compute,"},{"line_number":59,"context_line":"    and Networking services, so as to provide tenant-network isolation."},{"line_number":60,"context_line":"* Interactions between tenants placed sequentially on the same server, for"},{"line_number":61,"context_line":"  example, changes in BIOS settings, modifications to firmware, or files left"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ac06dbe_d50d763f","line":58,"updated":"2016-08-22 15:16:53.000000000","message":"Some blank lines in between paragraphs are needed to satisfy doc8.","commit_id":"167fe714f1974bdd886d0f9df284289a864f7b30"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"069aeb7b822434eb8536143067589a8a060787bb","unresolved":false,"context_lines":[{"line_number":56,"context_line":"    network, and does not take any precautions to avoid or prevent interaction"},{"line_number":57,"context_line":"    between tenants."},{"line_number":58,"context_line":"  - This can be addressed by integration with the OpenStack Identity, Compute,"},{"line_number":59,"context_line":"    and Networking services, so as to provide tenant-network isolation."},{"line_number":60,"context_line":"* Interactions between tenants placed sequentially on the same server, for"},{"line_number":61,"context_line":"  example, changes in BIOS settings, modifications to firmware, or files left"},{"line_number":62,"context_line":"  on disk or peripheral storage devices."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ac06dbe_a9c87523","line":59,"updated":"2016-08-22 11:54:00.000000000","message":"Can we link to http://docs.openstack.org/developer/ironic/deploy/multitenancy.html here?","commit_id":"167fe714f1974bdd886d0f9df284289a864f7b30"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"13e3835819fc6edab21823f31941abe13468a54c","unresolved":false,"context_lines":[{"line_number":56,"context_line":"    network, and does not take any precautions to avoid or prevent interaction"},{"line_number":57,"context_line":"    between tenants."},{"line_number":58,"context_line":"  - This can be addressed by integration with the OpenStack Identity, Compute,"},{"line_number":59,"context_line":"    and Networking services, so as to provide tenant-network isolation."},{"line_number":60,"context_line":"* Interactions between tenants placed sequentially on the same server, for"},{"line_number":61,"context_line":"  example, changes in BIOS settings, modifications to firmware, or files left"},{"line_number":62,"context_line":"  on disk or peripheral storage devices."}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ac06dbe_1bbbca0f","line":59,"in_reply_to":"1ac06dbe_a9c87523","updated":"2016-08-22 12:40:48.000000000","message":"+1 to add a link","commit_id":"167fe714f1974bdd886d0f9df284289a864f7b30"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"13e3835819fc6edab21823f31941abe13468a54c","unresolved":false,"context_lines":[{"line_number":64,"context_line":"    during the \"cleaning\" phase, after deleting an instance. It *does not*"},{"line_number":65,"context_line":"    reset BIOS or reflash firmware or peripheral devices."},{"line_number":66,"context_line":"  - This can be addressed through customizing the utility ramdisk used during"},{"line_number":67,"context_line":"    the \"cleaning\" phase. See details in the :ref:`Firmware security` section."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Firmware security"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ac06dbe_bba0b644","line":67,"range":{"start_line":67,"start_character":45,"end_line":67,"end_character":68},"updated":"2016-08-22 12:40:48.000000000","message":"is not rendered properly.","commit_id":"167fe714f1974bdd886d0f9df284289a864f7b30"},{"author":{"_account_id":12356,"name":"Vladyslav Drok","email":"vdrok@mirantis.com","username":"vdrok"},"change_message_id":"d1b670d8022de8b78eccf4b59a2645e61f095810","unresolved":false,"context_lines":[{"line_number":64,"context_line":"    during the \"cleaning\" phase, after deleting an instance. It *does not*"},{"line_number":65,"context_line":"    reset BIOS or reflash firmware or peripheral devices."},{"line_number":66,"context_line":"  - This can be addressed through customizing the utility ramdisk used during"},{"line_number":67,"context_line":"    the \"cleaning\" phase. See details in the :ref:`Firmware security` section."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"Firmware security"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ac06dbe_d596164b","line":67,"range":{"start_line":67,"start_character":45,"end_line":67,"end_character":68},"in_reply_to":"1ac06dbe_bba0b644","updated":"2016-08-22 15:16:53.000000000","message":"yeah it should be just `Firmware security`_ I think.","commit_id":"167fe714f1974bdd886d0f9df284289a864f7b30"}]}