Open Stack

Hi Sławek Kapłoński,

Thank you for your response.

1. In br-provider bridge I don't see any interface through which packets
should be send. Is this bridge used as "external bridge"?
Yes, it is used as "External Bridge". i added the interface eth12 within
the *node01_neutron_agents container* to br-brovider bridge. I can now ping
the gateway IP address on the provider network but still unable to ping the
the floating IP of the VM:
root at node01-utility-container-edc0f67a:~# *neutron router-port-list
core-router*
+--------------------------------------+------+-------------------+------------------------------------------------------+
| id                                   | name | mac_address       |
fixed_ips                                            |
+--------------------------------------+------+-------------------+------------------------------------------------------+
| 19ab7b32-198b-4392-a5b3-dc2d323d69a4 |      | fa:16:3e:dd:c9:02 |
{"subnet_id": "63acfd17-55d7-4147-926e-              |
|                                      |      |                   |
6ee75c9e7f55", "ip_address": "*10.1.4.107*"}           |
| 3c527c3c-5e51-489c-80a0-02a3eeba679d |      | fa:16:3e:6c:b5:72 |
{"subnet_id": "b42b5af9-efcf-42df-bb0f-              |
|                                      |      |                   |
e080d606fdf0", "ip_address": "192.168.3.1"}          |
| f67e4a28-f7c5-480b-8343-ff80d8ef4753 |      | fa:16:3e:8d:db:fc |
{"subnet_id": "b42b5af9-efcf-42df-bb0f-              |
|                                      |      |                   |
e080d606fdf0", "ip_address": "192.168.3.5"}          |
+--------------------------------------+------+-------------------+------------------------------------------------------+
maas-user at ubuntu:~$* ping 10.1.4.107*
PING 10.1.4.107 (10.1.4.107) 56(84) bytes of data.
64 bytes from 10.1.4.107: icmp_seq=1 ttl=64 time=0.996 ms
64 bytes from 10.1.4.107: icmp_seq=2 ttl=64 time=0.715 ms
64 bytes from 10.1.4.107: icmp_seq=3 ttl=64 time=0.699 ms
64 bytes from 10.1.4.107: icmp_seq=4 ttl=64 time=0.730 ms

root at node01-utility-container-edc0f67a:~# *openstack server list*
WARNING: openstackclient.common.utils is deprecated and will be removed
after Jun 2017. Please use osc_lib.utils
+--------------------------------------+----------------------+--------+---------------------------------+------------+
| ID                                   | Name                 | Status |
Networks                        | Image Name |
+--------------------------------------+----------------------+--------+---------------------------------+------------+
| b6684532-c1b2-4e18-89bd-28fc7d2d6efb | selfservice-instance | ACTIVE |
project=192.168.3.9, *10.1.4.111* | cirros     |
+--------------------------------------+----------------------+--------+---------------------------------+------------+

root at node01:~# *ping 10.1.4.111*
PING 10.1.4.111 (10.1.4.111) 56(84) bytes of data.
>From 10.1.200.25 icmp_seq=1 Destination Host Unreachable
>From 10.1.200.25 icmp_seq=2 Destination Host Unreachable
>From 10.1.200.25 icmp_seq=3 Destination Host Unreachable


3. From where You are trying to ping this vm? Is it the same host or
another one? Is it connected to same vlan?
Yes, it is the same host and the same VLAN. I forgot to mention that i used
DVR setup.

The problem i have is that i don't know which interface should i add to
br-provider on the compute node. br-vlan bridge is already attached to my
external interface, that is why i got confused.

Can you please advice on this.

Thanks,
Hamza


On 26 November 2016 at 22:48, Sławek Kapłoński <slawek at kaplonski.pl> wrote:

> Hello,
>
> 1. In br-provider bridge I don't see any interface through which packets
> should be send. Is this bridge used as "external bridge"?
> 2. Please check also Openflow rules in bridges - it's important to have
> proper rules on bridges
> 3. From where You are trying to ping this vm? Is it the same host or
> another one? Is it connected to same vlan?
> 4. When You are trying to ping Your vm what You see on interfaces on
> Your host?
>
> --
> Best regards / Pozdrawiam
> Sławek Kapłoński
> slawek at kaplonski.pl
>
> On Sat, 26 Nov 2016, Achi Hamza wrote:
>
> > Hi All,
> >
> > Context:
> >   openstack-ansible tag:   14.0.1
> >   ML2 plug-in:   OpenvSwitch
> >   Project / External networks:   VLAN
> >   OS:  Ubuntu 16.0.4
> >
> > I would like to implement OVS with VLANs following these 2 docs [1][2]
> but
> > things didn't work for me. I cannot ping my provider network:
> >
> > root at node01-utility-container-edc0f67a:~# *openstack server list*
> > WARNING: openstackclient.common.utils is deprecated and will be removed
> > after Jun 2017. Please use osc_lib.utils
> > +--------------------------------------+-------------------+
> --------+---------------------+------------+
> > | ID                                   | Name              | Status |
> > Networks            | Image Name |
> > +--------------------------------------+-------------------+
> --------+---------------------+------------+
> > | ed7e7c76-dcf2-431e-8bb1-0541391f64ed | provider-instance | ACTIVE |
> > physnet1=10.1.4.103 | cirros     |
> > +--------------------------------------+-------------------+
> --------+---------------------+------------+
> >
> > root at node01-utility-container-edc0f67a:~# *ping 10.1.4.103*
> > PING 10.1.4.103 (10.1.4.103) 56(84) bytes of data.
> > From 10.1.200.25 icmp_seq=1 Destination Host Unreachable
> > From 10.1.200.25 icmp_seq=2 Destination Host Unreachable
> > From 10.1.200.25 icmp_seq=3 Destination Host Unreachable
> >
> >
> > This is how my OpenvSwitch configuration looks:
> > root at node01:~# *ovs-vsctl show*
> > 29613dde-944b-4449-ab09-af906a6f74c6
> >     Manager "ptcp:6640:127.0.0.1"
> >         is_connected: true
> >     Bridge br-int
> >         Controller "tcp:127.0.0.1:6633"
> >             is_connected: true
> >         fail_mode: secure
> >         Port int-br-provider
> >             Interface int-br-provider
> >                 type: patch
> >                 options: {peer=phy-br-provider}
> >         Port br-int
> >             Interface br-int
> >                 type: internal
> >         Port "qvobb7afbfb-18"
> >             tag: 1
> >             Interface "qvobb7afbfb-18"
> >     Bridge br-provider
> >         Controller "tcp:127.0.0.1:6633"
> >             is_connected: true
> >         fail_mode: secure
> >         Port phy-br-provider
> >             Interface phy-br-provider
> >                 type: patch
> >                 options: {peer=int-br-provider}
> >         Port br-provider
> >             Interface br-provider
> >                 type: internal
> >     ovs_version: "2.6.0"
> >
> >
> > Please advice on what might be wrong on my setup.
> >
> > Thank you,
> > Hamza
> >
> > [1]
> > http://docs.openstack.org/developer/openstack-ansible-
> os_neutron/app-openvswitch.html
> > [2]
> > https://medium.com/@travistruman/configuring-openstack-ansible-for-open-
> vswitch-b7e70e26009d#.wylhu7pqh
>
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161127/a4fbc056/attachment.html>