Bug 1014774
| Summary: | packstack configures br-ex to use gateway ip | ||
|---|---|---|---|
| Product: | [Community] RDO | Reporter: | Mohammed Arafa <bugzilla> |
| Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ofer Blaut <oblaut> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | amer.hwaitat, aortega, beagles, bugzilla, derekh, ichavero, oblaut, yeylon |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-puppet-modules-2013.2-9.fc20 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-30 23:07:49 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Mohammed Arafa
2013-10-02 18:32:49 UTC
Actually that documentation indicates that you have to make these modifications manually. I may be misunderstanding your bug report or perhaps I am missing a relevant piece of text. Can you confirm? isnt the objective of packstack to do all the heavy lifting of configuration? this is one of the most important configs; to allow the outside world to communicate with the openstack deployment. note too that the documentation states you have to manually install openstack piecemeal and set up keystone for each component of the installation. packstack does away with all that. it should do away with br-ex configuration i have just learned that rhev at installation does this piece of configuration. perhaps that code can be reused? hi i do not know when this change happened but br-ex is now created with packstack. problem is that the ip is not moved from eth0/em0 to br-ex. ---Device config for /etc/sysconfig/network-scripts/ifcfg-br-ex--- DEVICE=br-ex DEVICETYPE=ovs TYPE=OVSBridge BOOTPROTO=static IPADDR= NETMASK= ONBOOT=yes ---Device config for /etc/sysconfig/network-scripts/ifcfg-eth0--- DEVICE=eth0 HWADDR=18:a9:05:22:2c:5b NM_CONTROLLED="no" ONBOOT=yes IPADDR=192.168.0.30 BOOTPROTO=none NETMASK=255.255.255.0 TYPE=Ethernet GATEWAY=192.168.0.1 DNS1=4.2.2.2 IPV6INIT=no USERCTL=no also means that this is incomplete in its implementation # Whether to configure the ovs external bridge in an all-in-one # deployment CONFIG_PROVISION_ALL_IN_ONE_OVS_BRIDGE=y it seems there is progress with each new version of packstack. but it is _STILL_ not complete. [root@openstack01 openstack]# cat /etc/sysconfig/network-scripts/ifcfg-br-ex DEVICE=br-ex DEVICETYPE=ovs TYPE=OVSBridge BOOTPROTO=static IPADDR=172.24.4.225 NETMASK=255.255.255.240 ONBOOT=yes[root@openstack01 openstack]# issues 1. no gw 2. what is that ip? 3. is the above config accurate or the documentation? 4. ethX/emX left as is this is rather drastic. check out my br-ex config when i stated my demo floating ip range
br-ex Link encap:Ethernet HWaddr 72:98:F4:5E:F1:49
inet addr:192.168.122.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::3ce5:7eff:fe92:bb48/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:684 (684.0 b) TX bytes:468 (468.0 b)
packstack now configures br-ex to take the first ip in the floating ip range give to it. this is normally .1 which is also normally the ip of the gateway and of course this also means that your entire network is now flaky The current version of the provision module in Openstack Puppet Modules set the correct ip for br-ex I have configuered the br-ex before installation and now i get the error when creating External networks that br-ex is unknow for flat networks ... maybe this is a problem ... but how to overcome ... I have allinone installation on VM ... |