Add support for custom routes to containers (snet)
Bug #1464639 reported by
Matt Thompson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Medium
|
Matt Thompson | ||
Kilo |
Fix Released
|
Medium
|
Matt Thompson | ||
Trunk |
Fix Released
|
Medium
|
Matt Thompson |
Bug Description
From https:/
<snip>
In case br-snet is configured at the glance or neutron containers, ansible should add a route to the service net over the eth3 interface (br-snet) like:
/etc/network/
post-up ip route add 1.2.3.0/18 via 172.29.248.1
Currently I would like to have the service network to be configured as mandatory option inside the rpc_user_config.yml and probably the host interface. So we can add
iptables -t nat -A POSTROUTING -s 172.29.248.0/22 -o -j MASQUERADE
to the infra nodes. iptables-persistent shoud be installed in that case too
</snip>
no longer affects: | openstack-ansible/next |
Changed in openstack-ansible: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 191020/