RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1202961 - Packstack --allinone should configure NAT for floating ip network
Summary: Packstack --allinone should configure NAT for floating ip network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: Juno
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: Kilo
Assignee: Martin Magr
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On: 1202958
Blocks: 1034476
TreeView+ depends on / blocked
 
Reported: 2015-03-17 19:25 UTC by Lars Kellogg-Stedman
Modified: 2015-03-18 17:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-18 17:45:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Lars Kellogg-Stedman 2015-03-17 19:25:02 UTC
Running `packstack --allinone` should result in an environment with at least outbound external connectivity.  Currently, packstack creates a floating ip network and sets up br-ex as the gateway for this network:

7: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 3a:18:bb:22:71:4e brd ff:ff:ff:ff:ff:ff
    inet 172.24.4.225/28 scope global br-ex
       valid_lft forever preferred_lft forever
    inet6 fe80::3818:bbff:fe22:714e/64 scope link 
       valid_lft forever preferred_lft forever

Adding a NAT rule to the system would permit instances with access to the floating ip network to have outbound network access.  Something like:

    iptables -A POSTROUTING -s 172.24.4.224/28 -j MASQUERADE

Comment 1 Lars Kellogg-Stedman 2015-03-18 17:45:30 UTC
With an install on F21 using openstack-packstack-2014.2-0.18.dev1462.gbb05296.fc22.noarch, this (using the NAT solution) actually did the right thing:

-P POSTROUTING ACCEPT
-A POSTROUTING -j neutron-openvswi-POSTROUTING
-A POSTROUTING -j neutron-postrouting-bottom
-A POSTROUTING -s 172.24.4.224/28 -o eth0 -m comment --comment "000 nat" -j MASQUERADE
-A POSTROUTING -j nova-api-POSTROUTING
-A POSTROUTING -j nova-postrouting-bottom

So I'm going to call this resolved.


Note You need to log in before you can comment on or make changes to this bug.