[Openstack-operators] Help - Trying to install OpenStack - Network issues

Rafael Azevedo raffus at gmail.com
Mon Nov 7 20:10:03 UTC 2016


In time:

I've commented those lines and it finally worked.
Still don't know though the real effect of it.

auto br-vxlan
iface br-vxlan inet manual
    bridge_stp off
    bridge_waitport 0
    bridge_fd 0
    bridge_ports bond0.30

# OpenStack Networking VLAN bridge
auto br-vlan
iface br-vlan inet manual
    bridge_stp off
    bridge_waitport 0
    bridge_fd 0
    bridge_ports bond0

auto br-storage
iface br-storage inet manual
    bridge_stp off
    bridge_waitport 0
    bridge_fd 0
    bridge_ports bond0.20

BR,

R

2016-11-07 17:48 GMT-02:00 Rafael Azevedo <raffus at gmail.com>:
> Hi Melvin,
>
> Yes I do.
>
> If I disable the bridge infos everything works smoothly.
>
> Also, when bridge configs are set, I have this message on boot:
>
> "Waiting 60 more seconds for network configuration.."
>
> I understand that this problem is not related to openstack, but any
> help would be appreciated.
>
> I'm running on Ubuntu 14 TLS.
>
> Thanks a lot.
>
> R
>
> 2016-11-07 17:26 GMT-02:00 Melvin Hillsman <mrhillsman at gmail.com>:
>> Hey Rafael,
>>
>> Do you have bonding and 8021q kernel modules loading as well as bridge-utils
>> and if-enslave packages.
>>
>> --
>> Melvin Hillsman
>> Ops Technical Lead
>> OpenStack Innovation Center
>> mrhillsman at gmail.com
>> phone: (210) 312-1267
>> mobile: (210) 413-1659
>> Learner | Ideation | Belief | Responsibility | Command
>> http://osic.org
>>
>> On Nov 7, 2016, at 12:17, Rafael Azevedo <raffus at gmail.com> wrote:
>>
>> Hello guys,
>>
>> Im new to OpenStack and am following instructions from Ansible [1] in
>> order to get it installed.
>>
>> I've added the following config into my network init script:
>>
>> ===================================
>>
>> # This file describes the network interfaces available on your system
>> # and how to activate them. For more information, see interfaces(5).
>>
>> # The loopback network interface
>> auto lo
>> iface lo inet loopback
>>
>> auto em1
>> iface em1 inet manual
>> bond-master bond0
>>
>> auto em2
>> iface em2 inet manual
>> bond-master bond0
>>
>> auto em3
>> iface em3 inet manual
>> bond-master bond0
>>
>> auto em4
>> iface em4 inet manual
>> bond-master bond0
>>
>>
>> auto bond0
>> iface bond0 inet static
>>        address A.B.C.D
>>        netmask 255.255.255.240
>>        network X.X.X.X
>> #       broadcast 200.49.47.175
>>        gateway X.X.X.X
>>        # dns-* options are implemented by the resolvconf package, if
>> installed
>>        dns-nameservers 8.8.8.8
>>        dns-search iagente.net.br
>>    bond-mode 4
>>    bond-miimon 100
>>    bond-lacp-rate 1
>>    bond-slaves all
>>
>>
>> auto bond0.5
>> iface bond0.5 inet static
>>    address 10.196.188.2
>>    netmask 255.255.252.0
>>    vlan-raw-device bond0
>>
>> # Container/Host management VLAN interface
>> auto bond0.10
>> iface bond0.10 inet manual
>>    vlan-raw-device bond0
>>
>> # OpenStack Networking VXLAN (tunnel/overlay) VLAN interface
>> auto bond0.30
>> iface bond0.30 inet manual
>>    vlan-raw-device bond0
>>
>> # Storage network VLAN interface (optional)
>> auto bond0.20
>> iface bond0.20 inet manual
>>    vlan-raw-device bond0
>>
>> # Container/Host management bridge
>> auto br-mgmt
>> iface br-mgmt inet static
>>    bridge_stp off
>>    bridge_waitport 0
>>    bridge_fd 0
>>    bridge_ports bond0.10
>>    address 172.29.236.11
>>    netmask 255.255.252.0
>>    gateway 172.29.236.1
>>    dns-nameservers 8.8.8.8 8.8.4.4
>>
>> # OpenStack Networking VXLAN (tunnel/overlay) bridge
>> #
>> # Only the COMPUTE and NETWORK nodes must have an IP address
>> # on this bridge. When used by infrastructure nodes, the
>> # IP addresses are assigned to containers which use this
>> # bridge.
>> #
>> auto br-vxlan
>> iface br-vxlan inet manual
>>    bridge_stp off
>>    bridge_waitport 0
>>    bridge_fd 0
>>    bridge_ports bond0.30
>>
>> # compute1 VXLAN (tunnel/overlay) bridge config
>> #auto br-vxlan
>> #iface br-vxlan inet static
>> #    bridge_stp off
>> #    bridge_waitport 0
>> #    bridge_fd 0
>> #    bridge_ports bond0.30
>> #    address 172.29.240.12
>> #    netmask 255.255.252.0
>>
>> # OpenStack Networking VLAN bridge
>> auto br-vlan
>> iface br-vlan inet manual
>>    bridge_stp off
>>    bridge_waitport 0
>>    bridge_fd 0
>>    bridge_ports bond0
>>
>> # Storage bridge (optional)
>> #
>> # Only the COMPUTE and STORAGE nodes must have an IP address
>> # on this bridge. When used by infrastructure nodes, the
>> # IP addresses are assigned to containers which use this
>> # bridge.
>> #
>> auto br-storage
>> iface br-storage inet manual
>>    bridge_stp off
>>    bridge_waitport 0
>>    bridge_fd 0
>>    bridge_ports bond0.20
>>
>> # compute1 Storage bridge
>> #auto br-storage
>> #iface br-storage inet static
>> #    bridge_stp off
>> #    bridge_waitport 0
>> #    bridge_fd 0
>> #    bridge_ports bond0.20
>> #    address 172.29.244.12
>> #    netmask 255.255.252.0
>>
>> ===================================
>>
>> But after I reboot the server, I lost connectivity and the server's
>> network wont work.
>>
>> Can anybody please help me out?
>>
>> What am I doing wrong?
>>
>> Thanks in advance.
>>
>> BR,
>>
>> R
>>
>> --
>> [1]:
>> http://docs.openstack.org/developer/openstack-ansible/install-guide/app-config-test.html#test-environment-config
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



More information about the OpenStack-operators mailing list