Add support for custom routes to containers (snet)

Bug #1464639 reported by Matt Thompson
6
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://github.com/rcbops/rpc-openstack/issues/14:

<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/interfaces.d/provider_networks.cfg for eth3:
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>

Revision history for this message
Matt Thompson (mattt416) wrote :
no longer affects: openstack-ansible/next
Changed in openstack-ansible:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-ansible-deployment (kilo)

Reviewed: https://review.openstack.org/197335
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=8d54c86396cb01cdcdfbf8bf42d258041b3aef1d
Submitter: Jenkins
Branch: kilo

commit 8d54c86396cb01cdcdfbf8bf42d258041b3aef1d
Author: Matt Thompson <email address hidden>
Date: Fri Jun 12 13:47:12 2015 +0100

    Add support for specifying custom static routes

    This change allows you to specify static routes for a given network in
    your openstack_user_config.yml file:

      global_overrides:
        provider_networks:
          - network:
              group_binds:
                - glance_api
                - nova_compute
                - neutron_linuxbridge_agent
              type: "raw"
              container_bridge: "br-snet"
              container_interface: "eth3"
              container_type: "veth"
              ip_from_q: "snet"
              static_routes:
                - cidr: 10.176.0.0/12
                  gateway: 172.29.248.1

    This will result in the following being written to
    /etc/network/interfaces.d/eth3.cfg for the affected containers:

      post-up ip route add 10.176.0.0/12 via 172.29.248.1 || true

    Change-Id: Id5a74db2399166af2d6ac289b71ebb0de04f5679
    Closes-Bug: #1464639
    (cherry picked from commit 21a8f1ff04ac6aeb3c54ddd61bc3b37318e9ed4e)

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.11

This issue was fixed in the openstack/openstack-ansible 11.2.11 release.

Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/openstack-ansible 11.2.12

This issue was fixed in the openstack/openstack-ansible 11.2.12 release.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/openstack-ansible 11.2.14

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.