)]}'
{"doc/networking-guide/source/deploy-ovs-provider.rst":[{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"a3fad4d00654ac6119d2e4ecb4b94a4e0e6c6f0f","unresolved":false,"context_lines":[{"line_number":190,"context_line":"   .. note::"},{"line_number":191,"context_line":""},{"line_number":192,"context_line":"      The ``force_metadata`` option forces the DHCP agent to provide"},{"line_number":193,"context_line":"      a host route to the metadata service on ``203.0.113.254``"},{"line_number":194,"context_line":"      regardless of whether the subnet contains an interface on a"},{"line_number":195,"context_line":"      router, thus maintaining similar and predictable metadata behavior"},{"line_number":196,"context_line":"      among subnets."}],"source_content_type":"text/x-rst","patch_set":1,"id":"ba2be162_053ea1d9","line":193,"range":{"start_line":193,"start_character":46,"end_line":193,"end_character":63},"updated":"2017-03-03 13:46:06.000000000","message":"169.254.169.354 is specifically referencing the metadata service.","commit_id":"f168bf637f69059222baa3bfe4ba403a308f3df8"}]}