Created attachment 870305 [details] answer file Description of problem: I have configured packstack to deploy TENANT_NETWORK_TYPE=gre the GRE is created ,as well as BR-EX , but the interface map to br-ex is not being added , i needed to do it manually . attached answer file Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.configure packstack with TENANT_NETWORK_TYPE=gre 2. configure map to br-ex 3. make sure attached interface to br-ex ( in my case eth3.195 ) is up and running before running packstack 4. run packstack and check ovs-vsctl on host contain L3 doesn't map the interface Actual results: Expected results: Additional info:
The plan for Packstack is to support only two network options: Neutron with VXLAN and Nova-network (as long it is around), and therefore this feature would be out of scope.
I See this issue reproduced both with GRE and VXLAN (at least when using ML2): ML2 VXLAN Bug #1066519 Comment #11 ML2 GRE Bug #1068962 Comment #12 In both cases I had to manually add the interface port to the br-ex: # ovs-vsctl add-port br-ex ethX.<VLAN_ID> NVR: openstack-packstack-2013.2.1-0.28.dev989.el6ost
Connecting your instances to external network is IMHO far across the border of PoC installer and it is intended to leave this step on administrator nevertheless which network architecture is supported.
Martin, One can actually argue that having external connectivity for instances is a pretty decent POC request. The external bridge has its own unique settings and I can't see why it's tied to any specific tenant network configuration (i.e., it should be working regardless of what technology is being used for tenant segregation) . As I see it, we do have all the info we need prperly link the correct interface to the external bridge, so why just not run the 'ovs-vsctl add-port' and save it from the user?
Same issue with VXLAN as well
Verified on /OpenStack/5.0-RHEL-7/2014-06-25.5/RH7-RHOS-5.0.repo Step to reproduce: 1.ovc-vsctl show that br-ex mapping has been configured as expected after Packstack installation. 2.The Router has been created. 3.Ping from Router namespace to 8.8.8.8 succeeded.
Packstack changes physical NIC ifcfg file, which results in no-connectivity to external network (even though br-ex is shown as connected in ovs) On RHEL7, RHOS5 neutorn ml2-vxlan nodes: 1controller, 1networker, 2compute [root@puma45 ~]# rpm -aq | grep "packstack\|neutron" openstack-neutron-2014.1-35.el7ost.noarch openstack-packstack-2014.1.1-0.28.dev1194.el7ost.noarch openstack-packstack-puppet-2014.1.1-0.28.dev1194.el7ost.noarch openstack-neutron-openvswitch-2014.1-35.el7ost.noarch python-neutronclient-2.3.4-2.el7ost.noarch python-neutron-2014.1-35.el7ost.noarch ifcfg file before packstack: VLAN=yes TYPE=Vlan PHYSDEV=enp3s0f1 VLAN_ID=181 REORDER_HDR=0 BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_PEERDNS=yes IPV6_PEERROUTES=yes IPV6_FAILURE_FATAL=no NAME=enp3s0f1.181 UUID=f82ac46a-f8a4-4588-b1ee-ad1e21eee6fa ONBOOT=yes Post packstack [root@puma46 ~]# cat /etc/sysconfig/network-scripts/ifcfg-enp3s0f1.181 DEVICE=enp3s0f1.181 DEVICETYPE=ovs TYPE=OVSPort ONBOOT=yes OVSBOOTPROTO=none OVS_BRIDGE=br-ex
Blocks bare-metal automation
Problem in RHEL7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0846.html