Ask Your Question
0

Failure to obtain private IP by VM booting up on Compute node of Two RealNode IceHouse Neutron OVS&VLAN Cluster F20

asked 2014-05-24 07:35:03 -0500

dbaxps gravatar image

updated 2014-05-24 12:34:36 -0500

Cluster (Controller+NeutronServer)+ Compute successfully setup via answer-file.
Configuration files on Controller && Compute here

Launching Cirros VM on Controller works fine.

Attempt to launch Cirros VM on Compute Node results failure to obtain private IP address from Controller.
During activating  CirrOS VM on I run on Compute Node:-

[root@icehouse2 ]# ovs-vsctl show
bf768fc8-d18b-4762-bdd2-a410fcf88a9b
    Bridge "br-p4p1"
        Port "br-p4p1"
            Interface "br-p4p1"
                type: internal
        Port "phy-br-p4p1"
            Interface "phy-br-p4p1"
        Port "p4p1"
            Interface "p4p1"
    Bridge br-int
        Port br-int
            Interface br-int
                type: internal
        Port "int-br-p4p1"
            Interface "int-br-p4p1"
        Port "qvoe5a82d77-d4"
            tag: 8
            Interface "qvoe5a82d77-d4"
    ovs_version: "2.0.1"

[root@icehouse2 ]# brctl show
bridge name bridge id       STP enabled interfaces
qbre5a82d77-d4      8000.6210e1b10d10 no        qvbe5a82d77-d4

and get

[root@icehouse2 nova]# tcpdump -vv -i qbre5a82d77-d4

tcpdump: WARNING: qbre5a82d77-d4: no IPv4 address assigned
tcpdump: listening on qbre5a82d77-d4, link-type EN10MB (Ethernet), capture size 65535 bytes
16:00:59.716295 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from fa:16:3e:8f:3d:e4 (oui Unknown), length 280, xid 0xc4cb856, secs 60, Flags [none] (0x0000)
      Client-Ethernet-Address fa:16:3e:8f:3d:e4 (oui Unknown)
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        Client-ID Option 61, length 7: ether fa:16:3e:8f:3d:e4
        MSZ Option 57, length 2: 576
        Parameter-Request Option 55, length 7: 
          Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
          Domain-Name, BR, NTP
        Vendor-Class Option 60, length 12: "udhcp 1.20.1"
16:01:59.777118 IP (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 308)
    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from fa:16:3e:8f:3d:e4 (oui Unknown), length 280, xid 0xc4cb856, secs 120, Flags [none] (0x0000)
      Client-Ethernet-Address fa:16:3e:8f:3d:e4 (oui Unknown)
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: Discover
        Client-ID Option 61, length 7: ether fa:16:3e:8f:3d:e4
        MSZ Option 57, length 2: 576
        Parameter-Request Option 55, length 7: 
          Subnet-Mask, Default-Gateway, Domain-Name-Server, Hostname
          Domain-Name, BR, NTP
        Vendor-Class Option 60, length 12: "udhcp 1.20.1"

So VM comes to active state without private IP , no complains regarding 169.254.169.254 during waiting for login.

On Controller
[root@icehouse1 ~(keystone_admin)]# ovs-vsctl show
a675c73e-c707-4f29-af60-57fb7c3f81c4
    Bridge br-int
        Port "int-br-p4p1"
            Interface "int-br-p4p1"
        Port br-int
            Interface br-int
                type: internal
        Port "qr-bbba6fd3-a3"
            tag: 1
            Interface "qr-bbba6fd3-a3"
                type: internal
        Port "qvo61d82a0f-32"
            tag: 1
            Interface "qvo61d82a0f-32"
        Port "tapa7e1ac48-7b"
            tag: 1
            Interface "tapa7e1ac48-7b"
                type: internal
        Port "qvof8c8a1a2-51"
            tag: 1
            Interface "qvof8c8a1a2-51"
    Bridge br-ex
        Port "p37p1"
            Interface "p37p1"
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-3787602d-29"
            Interface "qg-3787602d-29"
                type: internal
    Bridge "br-p4p1"
        Port "p4p1"
            Interface "p4p1"
        Port "phy-br-p4p1"
            Interface "phy-br-p4p1"
        Port "br-p4p1"
            Interface "br-p4p1"
                type: internal
    ovs_version: "2.0.1"
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-05-24 13:50:21 -0500

dbaxps gravatar image

updated 2014-05-25 00:42:54 -0500

      Fixed 
        On Controller and Compute replaced  NAME by DEVICE in ifcfg-p4p1, like I did for ifcfg-p37p1
        [root@icehouse2 network-scripts]# cat ifcfg-p4p1
        TYPE=Ethernet
        BOOTPROTO=none
        DEVICE=p4p1
        ONBOOT=yes
        NM_CONTROLLED=no
        Then
        [root@icehouse2 network-scripts]# ifup p4p1 ( on Controller && Compute).
     Finally:-
    1. NetworkManager should be disabled on both nodes, service network enable.
    2. Syntax of ifcfg-* files  should follow RHEL 6.5 notations rather then F20, in particular, remove zerros at the end of   IPADDRESS,GATEWAY,.. in ifcfg-p37p1 on Compute
    3. Special care should be taken to bring up p4p1 (in my case) 

Specific of answer-file on real F20 boxes :-

CONFIG_NOVA_COMPUTE_PRIVIF=p4p1
CONFIG_NOVA_NETWORK_PUBIF=p37p1
CONFIG_NOVA_NETWORK_PRIVIF=p4p1

CONFIG_NEUTRON_OVS_TENANT_NETWORK_TYPE=vlan
CONFIG_NEUTRON_OVS_VLAN_RANGES=physnet1:100:200
CONFIG_NEUTRON_OVS_BRIDGE_MAPPINGS=physnet1:br-p4p1
CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-p4p1:p4p1
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-05-24 07:35:03 -0500

Seen: 607 times

Last updated: May 25 '14