Open Stack

Hi Michal,
     Thanks for the detailed explanation. The ODL_LOCAL_IP helped define interfaces as we needed.
Thanks
Badri

From: Michał Skalski [mailto:michal at skalski.org]
Sent: Friday, July 31, 2015 2:41 AM
To: Venkataraghavan, C
Cc: Sabapathy, Ravi; vishal.thapar at ericsson.com; Viswanatha, Badrinath; openstack at lists.openstack.org; <ovsdb-dev at lists.opendaylight.org>
Subject: Re: [ovsdb-dev] DevStack-opendaylight on a multi-node setup

Hi,
The local_ip attribute inside ovs configuration indicate the endpoint of vxlan tunnel on specific node. As you can see here [1]  value of this attribute is save inside $ODL_LOCAL_IP which is by default equal to HOST_IP: [2]. So when you define HOST_IP it will be used as a vxlan endpoint which cause that tunnel traffic will go through interface with this IP address assigned. You can overwrite this by explicit defining ODL_LOCAL_IP in your local.conf.
Here is an example of mine local.conf file: [3]

[1] https://github.com/openstack/networking-odl/blob/master/devstack/plugin.sh#L341
[2] https://github.com/openstack/networking-odl/blob/master/devstack/plugin.sh#L333
[3]https://gist.github.com/michalskalski/b6f12b318e279ebf3deb
Regards,
Michal

2015-07-30 20:37 GMT+02:00 <C_Venkataraghavan at dell.com<mailto:C_Venkataraghavan at dell.com>>:
Resending  Ravi’s mail with watermark removed.

Hi Vishal,

                (Resending the mail by removing “Internal use” tag)

                We forgot to mention a detail in our multi-node setup i.e., the overlay used is VxLan (Q_ML2_TENANT_NETWORK_TYPE=vxlan) . When I checked about ODL_PROVIDER_MAPPINGS, it works only with VLAN type of tenant network.
                How do we attach a physical  interface for a vxlan type of tenant network?


Regards,
Ravi


-----Original Message-----
From: ovsdb-dev-bounces at lists.opendaylight.org<mailto:ovsdb-dev-bounces at lists.opendaylight.org> [mailto:ovsdb-dev-bounces at lists.opendaylight.org] On Behalf Of Vishal Thapar
Sent: Thursday, July 30, 2015 1:54 AM
To: Viswanatha, Badrinath; openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>; ovsdb-dev at lists.opendaylight.org<mailto:ovsdb-dev at lists.opendaylight.org>
Cc: Venkataraghavan, C
Subject: Re: [ovsdb-dev] DevStack-opendaylight on a multi-node setup

Hi Badri,

Try this: `ODL_PROVIDER_MAPPINGS=physnet1:eth1`

Regards,
Vishal.


From: ovsdb-dev-bounces at lists.opendaylight.org<mailto:ovsdb-dev-bounces at lists.opendaylight.org> [mailto:ovsdb-dev-bounces at lists.opendaylight.org] On Behalf Of Badrinath_Viswanatha at Dell.com<mailto:Badrinath_Viswanatha at Dell.com>
Sent: 29 July 2015 11:29
To: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>; ovsdb-dev at lists.opendaylight.org<mailto:ovsdb-dev at lists.opendaylight.org>
Cc: C_Venkataraghavan at DELL.com<mailto:C_Venkataraghavan at DELL.com>
Subject: [ovsdb-dev] DevStack-opendaylight on a multi-node setup


Hi All,
   We are trying to setup a multi-node devstack setup with opendaylight ML2 plugin.

The local.conf, we use with devstack does not have an option  to specify the tenant physical interfaces. It only has options for specifying the management IP address ( and by extension the eth0 ) and the external network ( eth2 ).

Can you please help
1)      How to specify tenant network ( VM data network) to be setup only on eth1 of the compute nodes. ?
2)      If possible, share the local.conf, that you might have used with your devstack on a similar topology, specifying the physical interfaces.

Thanks
Badri

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev at lists.opendaylight.org<mailto:ovsdb-dev at lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

_______________________________________________
ovsdb-dev mailing list
ovsdb-dev at lists.opendaylight.org<mailto:ovsdb-dev at lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150731/5d0b1fe5/attachment.html>