I tried to create subnet resource and connect multiple routers through heat template.
However it is failed, because "OS::Neutron::RouterInterface" doesn't have "port_id" property.
In my understand, when use "subnet_id" for to connect subnet, neutron acquire "gateway_ip" automatically.
The "gateway_ip" is only one property of each subnets.
It means, multiple routers can't connect same subnet in this method.
I think, it can resolve to add "port_id" property to "OS::Neutron::RouterInterface".
The command line example that used neutron is:
========================================================================
$ neutron router-create router1
Created a new router:
+-----------------------+--------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------+
| admin_state_up | True |
| external_gateway_info | |
| id | ae478782-53c0-4434-ab16-49900c88016c |
| name | router1 |
| status | ACTIVE |
| tenant_id | 616ffbe0c00d4cfc8ce6bc5e15de9337 |
+-----------------------+--------------------------------------+
$ neutron router-create router2
Created a new router:
+-----------------------+--------------------------------------+
| Field | Value |
+-----------------------+--------------------------------------+
| admin_state_up | True |
| external_gateway_info | |
| id | a47942c5-9f8f-46d0-a6c4-84624272af11 |
| name | router2 |
| status | ACTIVE |
| tenant_id | 616ffbe0c00d4cfc8ce6bc5e15de9337 |
+-----------------------+--------------------------------------+
$ neutron net-create net
Created a new network:
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 918d2f8c-8c4f-4cc2-acdd-434b68ce6661 |
| name | net |
| provider:network_type | vlan |
| provider:physical_network | default |
| provider:segmentation_id | 1000 |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | 616ffbe0c00d4cfc8ce6bc5e15de9337 |
+---------------------------+--------------------------------------+
$ neutron subnet-create net 192.168.0.0/24
Created a new subnet:
+------------------+--------------------------------------------------+
| Field | Value |
+------------------+--------------------------------------------------+
| allocation_pools | {"start": "192.168.0.2", "end": "192.168.0.254"} |
| cidr | 192.168.0.0/24 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 192.168.0.1 |
| host_routes | |
| id | d6b6108e-0f67-4f48-8cdc-16610d3415b9 |
| ip_version | 4 |
| name | |
| network_id | 918d2f8c-8c4f-4cc2-acdd-434b68ce6661 |
| tenant_id | 616ffbe0c00d4cfc8ce6bc5e15de9337 |
+------------------+--------------------------------------------------+
$ neutron port-create net
Created a new port:
+----------------------+------------------------------------------------------------------------------------+
| Field | Value |
+----------------------+------------------------------------------------------------------------------------+
| admin_state_up | True |
| binding:capabilities | {"port_filter": false} |
| binding:host_id | |
| binding:vif_type | bridge |
| device_id | |
| device_owner | |
| fixed_ips | {"subnet_id": "d6b6108e-0f67-4f48-8cdc-16610d3415b9", "ip_address": "192.168.0.2"} |
| id | e7183085-2f48-4bb7-ae73-8d3e7915cad5 |
| mac_address | fa:16:3e:c0:20:44 |
| name | |
| network_id | 918d2f8c-8c4f-4cc2-acdd-434b68ce6661 |
| status | DOWN |
| tenant_id | 616ffbe0c00d4cfc8ce6bc5e15de9337 |
+----------------------+------------------------------------------------------------------------------------+
$ neutron port-create net
Created a new port:
+----------------------+------------------------------------------------------------------------------------+
| Field | Value |
+----------------------+------------------------------------------------------------------------------------+
| admin_state_up | True |
| binding:capabilities | {"port_filter": false} |
| binding:host_id | |
| binding:vif_type | bridge |
| device_id | |
| device_owner | |
| fixed_ips | {"subnet_id": "d6b6108e-0f67-4f48-8cdc-16610d3415b9", "ip_address": "192.168.0.4"} |
| id | 9577cafd-8e98-4059-a2e6-8a771b4d318e |
| mac_address | fa:16:3e:47:b6:fe |
| name | |
| network_id | 918d2f8c-8c4f-4cc2-acdd-434b68ce6661 |
| status | DOWN |
| tenant_id | 616ffbe0c00d4cfc8ce6bc5e15de9337 |
+----------------------+------------------------------------------------------------------------------------+
$ neutron router-interface-add router1 port=e7183085-2f48-4bb7-ae73-8d3e7915cad5
Added interface e7183085-2f48-4bb7-ae73-8d3e7915cad5 to router router1.
$ neutron router-interface-add router2 port=9577cafd-8e98-4059-a2e6-8a771b4d318e
Added interface 9577cafd-8e98-4059-a2e6-8a771b4d318e to router router2.
========================================================================
From my personal point of view, "port_id" is essential property for general use cases.
Example for, the vm should be connect both Internet and maintainance network via different subnets.
Could you post your heat template to show the usage further?