<div dir="auto"><div>Not really. Just bring some stuff up. Even if the routers are messed up the compute instances won't get hurt. </div><div dir="auto"><br></div><div dir="auto">The snat stuff sounds right. <br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On Sep 25, 2017 2:45 PM, "Turbo Fredriksson" <<a href="mailto:turbo@bayour.com">turbo@bayour.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">On 21 Sep 2017, at 04:45, Kevin Benton <kevin@benton.pub> wrote:<br>
<br>
> If you wanted to do it purely with an SQL hack you might be able to set distributed to False in the router_extra_attributes table. Additionally you would need to delete any entries from the routerports table with the type 'network:router_centralized_<wbr>snat' and update any with the type 'network:router_interface_<wbr>distributed' to 'network:router_interface’.<br>
<br>
</div>Thanx! That seems to have done the trick. I think:<br>
<br>
bladeA01:~# neutron router-list<br>
+-----------------------------<wbr>---------+----------------+---<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-----------------------------+<wbr>-------------+-------+<br>
| id                                   | name           | external_gateway_info                                                                                                                                                                | distributed | ha    |<br>
+-----------------------------<wbr>---------+----------------+---<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-----------------------------+<wbr>-------------+-------+<br>
| d9c39638-51b5-481a-a60d-<wbr>df79b6a06f9d | infrastructure | {"network_id": "b74570c9-f40f-4c64-9e4c-<wbr>9bf0c9978d2e", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "7bc73f7a-f07e-4ad7-bcd8-<wbr>1fd77f46c888", "ip_address": "10.0.5.1"}]} | False       | False |<br>
| dac1e4f4-dd02-4f97-bc77-<wbr>952906e8daa7 | tenant         | {"network_id": "b74570c9-f40f-4c64-9e4c-<wbr>9bf0c9978d2e", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "ab4da704-0ed2-4e54-89e4-<wbr>afc98b8bb631", "ip_address": "10.0.6.1"}]} | False       | False |<br>
+-----------------------------<wbr>---------+----------------+---<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-----------------------------+<wbr>-------------+———+<br>
<br>
The “external_gateway_info” still say “enable_snat=true” on both of them…<br>
Is that correct?<br>
<br>
But at least both “distributed” and “ha” is “False” now, so there’s a lot<br>
of progress! :). Million thanx.<br>
<br>
<br>
All my compute nodes are still down, haven’t dared start them up yet.<br>
Any way I can know for sure that this actually worked, without spinning<br>
up everything?<br>
<br>______________________________<wbr>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
Post to     : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack</a><br>
<br></blockquote></div><br></div></div></div>