)]}'
{"neutron/services/auto_allocate/db.py":[{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"06cdad88aedfb49f6ff2b198ecd86939f834df9c","unresolved":false,"context_lines":[{"line_number":40,"context_line":"LOG \u003d logging.getLogger(__name__)"},{"line_number":41,"context_line":"IS_DEFAULT \u003d \u0027is_default\u0027"},{"line_number":42,"context_line":"CHECK_REQUIREMENTS \u003d \u0027dry-run\u0027"},{"line_number":43,"context_line":"DISABLE_SNAT \u003d \u0027disable-snat\u0027"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"def _extend_external_network_default(core_plugin, net_res, net_db):"}],"source_content_type":"text/x-python","patch_set":5,"id":"5ff73747_e3dcd475","line":43,"updated":"2017-04-25 03:37:32.000000000","message":"The way you coded this, the network will never have an uplink to the external domain and thus the user VMs can only access their local network. Is that what you really wanted to do? To control SNAT behavior you should look at the gateway attribute [1]. That said, and as Kevin pointed out, customizing the behavior of this plugin cannot be done this easily, as the topology model is currently hard-coded and it should stay that way (in that modifying it in place like you did may lead to usability issues). There are a number of discussions proposed on this topic at the coming summit, where we should consider a number of design alternatives on how to extend the current model in a way that is discoverable by users.\n\n[1] https://specs.openstack.org/openstack/neutron-specs/specs/api/configurable_external_gateway_modes.html","commit_id":"ff7e42f3c81955512a47c76b1dad1fd6c58d5e39"}]}