I believe in meantime Tripleo Quickstat (minimal configuration) is working this way
http://bderzhavets.blogspot.com/2016/05/triple0-quickstart-first-impressions.html

If my understanding is wrong, please, correct me.

Thank you.
Boris.


From: rdo-list-bounces@redhat.com <rdo-list-bounces@redhat.com> on behalf of Boris Derzhavets <bderzhavets@hotmail.com>
Sent: Thursday, May 26, 2016 10:36 AM
To: rdo-list
Subject: Re: [rdo-list] Tripleo Quickstart External Netbork OVS Bridge on Controller seems to have wrong IP
 

Looking at http://blog.oddbit.com/2016/05/19/connecting-another-vm-to-your-tripleo-qu/

I see  2 interfaces: -   eth0 attached to brext and eth1, which is responsible for VTEP.


But doing standard steps I am getting only one interface eth0 on overcloud controller




From: rdo-list-bounces@redhat.com <rdo-list-bounces@redhat.com> on behalf of Boris Derzhavets <bderzhavets@hotmail.com>
Sent: Thursday, May 26, 2016 10:21 AM
To: rdo-list
Subject: [rdo-list] Tripleo Quickstart External Netbork OVS Bridge on Controller seems to have wrong IP
 

I follow https://simplenfv.wordpress.com/2016/05/16/deploying-openstack-on-just-one-hosted-server/

on 32 GB box . Everything goes fine. Finally I get :-


[stack@undercloud ~]$ heat stack-list
+--------------------------------------+------------+-----------------+---------------------+--------------+
| id                                   | stack_name | stack_status    | creation_time       | updated_time |
+--------------------------------------+------------+-----------------+---------------------+--------------+
| 7002392b-cd2d-439f-b3cd-024979f153a5 | overcloud  | CREATE_COMPLETE | 2016-05-26T13:35:17 | None         |
+--------------------------------------+------------+-----------------+---------------------+--------------+
[stack@undercloud ~]$ nova list
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
| ID                                   | Name                    | Status | Task State | Power State | Networks            |
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+
| 88f841ac-1ca0-4339-ba8a-c2895c0dc57c | overcloud-controller-0  | ACTIVE | -          | Running     | ctlplane=192.0.2.13 |
| f12a1086-7e23-4acb-80a7-8b2efe1e4ef2 | overcloud-novacompute-0 | ACTIVE | -          | Running     | ctlplane=192.0.2.12 |
+--------------------------------------+-------------------------+--------+------------+-------------+---------------------+

[stack@undercloud ~]$  ssh heat-admin@192.0.2.13
The authenticity of host '192.0.2.13 (192.0.2.13)' can't be established.
ECDSA key fingerprint is 24:91:50:95:63:b1:5b:ed:2f:fc:ad:ee:91:21:65:68.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.0.2.13' (ECDSA) to the list of known hosts.
Last login: Thu May 26 13:53:48 2016 from gateway

[heat-admin@overcloud-controller-0 ~]$ sudo su -
[root@overcloud-controller-0 ~]# ifconfig

br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.0.2.13  netmask 255.255.255.0  broadcast 192.0.2.255  <=====  br-ex IP on Controller
        inet6 fe80::2f7:7fff:fe1a:ca59  prefixlen 64  scopeid 0x20<link>
        ether 00:f7:7f:1a:ca:59  txqueuelen 0  (Ethernet)
        RX packets 12577  bytes 31512490 (30.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16487  bytes 19403543 (18.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::2f7:7fff:fe1a:ca59  prefixlen 64  scopeid 0x20<link>
        ether 00:f7:7f:1a:ca:59  txqueuelen 1000  (Ethernet)
        RX packets 12875  bytes 31598896 (30.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16857  bytes 19469403 (18.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 243023  bytes 258934061 (246.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 243023  bytes 258934061 (246.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@overcloud-controller-0 ~]# ovs-vsctl show
cc8be4fb-f96f-4679-b85d-d0afc7dd7f72
    Bridge br-int
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
    Bridge br-tun
        fail_mode: secure
        Port "vxlan-c000020c"
            Interface "vxlan-c000020c"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="192.0.2.13", out_key=flow, remote_ip="192.0.2.12"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port br-tun
            Interface br-tun
                type: internal
    Bridge br-ex
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth0"
            Interface "eth0"
    ovs_version: "2.5.0"


I would expect br-ex on Controller belong   192.168.23.0/24


Due to on VIRTHOST :-


[root@ServerCentOS72 ~]# virsh net-dumpxml external
<network>
  <name>external</name>
  <uuid>d585615b-c1c5-4e30-bf2d-ea247591c2b0</uuid>
  <forward mode='nat'>
    <nat>
      <port start='1024' end='65535'/>
    </nat>
  </forward>
  <bridge name='brext' stp='off' delay='0'/>
  <mac address='52:54:00:9d:b4:1d'/>
  <ip address='192.168.23.1' netmask='255.255.255.0'>
    <dhcp>
      <range start='192.168.23.10' end='192.168.23.50'/>
    </dhcp>
  </ip>
</network>

I am missing something here external network is the same as VTEPs network between Controller && Compute.

Please, advise.   I just followed instructions . Zero manual intervention from my side.


Thanks.

Boris.