)]}'
{"doc/networking-guide/source/deploy_scenario4b.rst":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"c7390c636f9462b86a99a2124a1b4708248fc064","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"Scenario 4b: Provider networks with Linux Bridge"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"This scenario describes a provider networks implementation of the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_268c787e","line":2,"updated":"2015-04-24 07:17:09.000000000","message":"Linux bridge - everywhere","commit_id":"c7d88e17109bf7f7715a2199cd3166a59a363472"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"c7390c636f9462b86a99a2124a1b4708248fc064","unresolved":false,"context_lines":[{"line_number":31,"context_line":"that run inside the OpenStack deployment might require direct layer-2"},{"line_number":32,"context_line":"access, typically using VLANs, to applications outside of the deployment."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Infrastructure Recommendations"},{"line_number":35,"context_line":"------------------------------"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"#. One controller node with two network interfaces: management and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_a629a839","line":34,"updated":"2015-04-24 07:17:09.000000000","message":"lowercase recommandations","commit_id":"c7d88e17109bf7f7715a2199cd3166a59a363472"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"c7390c636f9462b86a99a2124a1b4708248fc064","unresolved":false,"context_lines":[{"line_number":32,"context_line":"access, typically using VLANs, to applications outside of the deployment."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Infrastructure Recommendations"},{"line_number":35,"context_line":"------------------------------"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"#. One controller node with two network interfaces: management and"},{"line_number":38,"context_line":"   external (typically the Internet)."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_e6ec402b","line":35,"updated":"2015-04-24 07:17:09.000000000","message":"Second level header should be ~~~~ - see our markup conventions","commit_id":"c7d88e17109bf7f7715a2199cd3166a59a363472"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"c7390c636f9462b86a99a2124a1b4708248fc064","unresolved":false,"context_lines":[{"line_number":462,"context_line":"      | tenant_id                 | e0bddbc9210d409795887175341b7098     |"},{"line_number":463,"context_line":"      +---------------------------+--------------------------------------+"},{"line_number":464,"context_line":""},{"line_number":465,"context_line":".. note:: The ``shared`` option allows any project to use this network."},{"line_number":466,"context_line":""},{"line_number":467,"context_line":"#. Create a subnet on the provider network:"},{"line_number":468,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_26a9187c","line":465,"updated":"2015-04-24 07:17:09.000000000","message":"This note needs to be intented so that numbering of the steps works","commit_id":"c7d88e17109bf7f7715a2199cd3166a59a363472"},{"author":{"_account_id":10705,"name":"Darren Chan","email":"dazzachan@yahoo.com.au","username":"daz"},"change_message_id":"a3816f35061812290850f7907cfe0f1e214af339","unresolved":false,"context_lines":[{"line_number":371,"context_line":"   ::"},{"line_number":372,"context_line":""},{"line_number":373,"context_line":"      net.ipv4.conf.default.rp_filter\u003d0"},{"line_number":374,"context_line":"      net.ipv4.conf.all.rp_filter\u003d0"},{"line_number":375,"context_line":""},{"line_number":376,"context_line":"#. Load the new kernel configuration:"},{"line_number":377,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"bab921fb_91d0b5f7","line":374,"updated":"2015-04-27 02:54:23.000000000","message":"FYI, for code snippets, you can remove the \"::\" and add an extra semicolon at the end of the sentence. For example:\n\n :file:`/etc/sysctl.conf` file::\n\n      net.ipv4.conf.default.rp_filter\u003d0\t373\n\t\t\t      net.ipv4.conf.all.rp_filter\u003d0","commit_id":"6d102cf9face15b9c6fecdbcad2cf309d11fcfa2"}]}