[Openstack] vm unable to get ip neutron with vmware nsx plugin

Gary Kotton gkotton at vmware.com
Sun Jul 31 11:08:48 UTC 2016


Hi,
I have posted the following patches upstream to make this a little more easily consumed:

1.       Neutron - https://review.openstack.org/349241

2.       Vmware_nsx - https://review.openstack.org/349248
If you are running devstack you need the following services:

q-svc and q-dhcp to be running

You will see that when you configure the network the OVS will be populate with the tag:

For example:

neutron net-create private --tenant-id private --provider:network_type vlan --provider:physical_network dvs --provider:segmentation_id 7

nicira at upstream:~$ sudo ovs-vsctl show
65a7111a-fb70-4527-9d99-d0da33e98f5d
    Manager "ptcp:6640:127.0.0.1"
        is_connected: true
    Bridge br-dvs
        Port "tap26942af0-9f"
            tag: 7
            Interface "tap26942af0-9f"
                type: internal
        Port "eth1"
            Interface "eth1"
        Port br-dvs
            Interface br-dvs
                type: internal
    ovs_version: "2.0.2"

Please note there are a few limitations to this plugin:

1.       The network creation can only be done by an admin user for tenants

2.       There are no security groups

3.       There is no l3 support

The purpose of the plugin was to enable a user to get the look and feel of Neutron with the VC. A more complete, robust and production grade plugin would be one of the NSX plugins.

Thanks
Gary

From: Vaidyanath Manogaran <vaidyanath.m at gmail.com>
Date: Thursday, July 28, 2016 at 8:25 PM
To: Gary Kotton <gkotton at vmware.com>
Cc: Scott Lowe <scott.lowe at scottlowe.org>, "openstack at lists.openstack.org" <openstack at lists.openstack.org>, "community at lists.openstack.org" <community at lists.openstack.org>
Subject: Re: [Openstack] vm unable to get ip neutron with vmware nsx plugin

its just simple DVS.

core_plugin = vmware_nsx.plugin.NsxDvsPlugin


On Thu, Jul 28, 2016 at 10:54 PM, Gary Kotton <gkotton at vmware.com<mailto:gkotton at vmware.com>> wrote:
Hi,
Which backend NSX version are you using? Is this NSX|V, NSX|MH or simple DVS?
Thanks
Gary

From: Vaidyanath Manogaran <vaidyanath.m at gmail.com<mailto:vaidyanath.m at gmail.com>>
Date: Thursday, July 28, 2016 at 8:04 PM
To: Scott Lowe <scott.lowe at scottlowe.org<mailto:scott.lowe at scottlowe.org>>
Cc: "openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>" <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>, "community at lists.openstack.org<mailto:community at lists.openstack.org>" <community at lists.openstack.org<mailto:community at lists.openstack.org>>
Subject: Re: [Openstack] vm unable to get ip neutron with vmware nsx plugin

Hi Scott,
Thank you for the reply. my replies inline[MV]

On Thu, Jul 28, 2016 at 8:29 PM, Scott Lowe <scott.lowe at scottlowe.org<mailto:scott.lowe at scottlowe.org>> wrote:
Please see my responses inline, prefixed by [SL].


On Jul 28, 2016, at 2:43 AM, Vaidyanath Manogaran <vaidyanath.m at gmail.com<mailto:vaidyanath.m at gmail.com>> wrote:
>
> 1- Controller node Services - keystone, glance, neutron, nova neutron plugins used - vmware-nsx - https://github.com/openstack/vmware-nsx/<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_vmware-2Dnsx_&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=P9nqTtbpb0cd3RCGTLZ2FVIXDztbr46L6s8pM3ulswk&s=sHANOvMVbB4vailvn1AO1bxWfs6epyOTAAcuDkWKSEE&e=> neutron agents - openvswitch agent 2- compute node Services - nova-compute


[SL] May I ask what version of NSX you're running?
[MV] I have installed it from source picked up from github stable/mitaka - https://github.com/openstack/vmware-nsx/tree/stable/mitaka<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_vmware-2Dnsx_tree_stable_mitaka&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=P9nqTtbpb0cd3RCGTLZ2FVIXDztbr46L6s8pM3ulswk&s=1y5-WQ8XAnjDMxyPqes3I2h6E9TfJzwPlTu70EJpTfY&e=>

> I have all the services up and running. but when i provision the vm the vm is not assigning the IP address which is offered from DHCP server


[SL] NSX doesn't currently handle DHCP on its own, so you'll need the Neutron DHCP agent running somewhere. Wherever it's running will need to have OVS installed and be registered into NSX as a "hypervisor" so that the DHCP agent can be plumbed into the overlay networks.

One common arrangement is to build a Neutron "network node" that is running the DHCP agent and metadata agent, and register that into NSX.
 [MV] I have setup only controller with neutron metadata and neutron dhcp

root at controller:~# neutron agent-list
+--------------------------------------+----------------+------------+-------+----------------+------------------------+
| id                                   | agent_type     | host       | alive | admin_state_up | binary                 |
+--------------------------------------+----------------+------------+-------+----------------+------------------------+
| 5555dbd8-14d0-4a47-83bd-890737bcfe08 | DHCP agent     | controller | :-)   | True           | neutron-dhcp-agent     |
| f183a3b6-b065-4b90-b5b7-b3d819c30f5b | Metadata agent | controller | :-)   | True           | neutron-metadata-agent |
+--------------------------------------+----------------+------------+-------+----------------+------------------------+
root at controller:~#



> here are the config details:-
>
> root at controller:~# neutron net-show test +---------------------------+--------------------------------------+ | Field | Value | +---------------------------+--------------------------------------+ | admin_state_up | True | | created_at | 2016-07-28T13:35:22 | | description | | | id | be2178a3-a268-47f4-809e-8e0024c6f054 | | name | test | | port_security_enabled | True | | provider:network_type | vlan | | provider:physical_network | dvs | | provider:segmentation_id | 110 | | router:external | False | | shared | True | | status | ACTIVE | | subnets | 5009ec57-4ca7-4e2b-962e-549e6bbee408 | | tags | | | tenant_id | ce581005def94bb1947eac9ac15f15ea | | updated_at | 2016-07-28T13:35:22 | +---------------------------+--------------------------------------+
>
> root at controller:~# neutron subnet-show testsubnet +-------------------+------------------------------------------------------+ | Field | Value | +-------------------+------------------------------------------------------+ | allocation_pools | {"start": "192.168.18.246", "end": "192.168.18.248"} | | cidr | 192.168.18.0/24<https://urldefense.proofpoint.com/v2/url?u=http-3A__192.168.18.0_24&d=CwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=VlZxHpZBmzzkWT5jqz9JYBk8YTeq9N3-diTlNj4GyNc&m=P9nqTtbpb0cd3RCGTLZ2FVIXDztbr46L6s8pM3ulswk&s=nky7Szid45D670NmpZ_3U5oQEt2c9uGU6boDOAH5YdY&e=> | | created_at | 2016-07-28T14:56:54 | | description | | | dns_nameservers | 192.168.13.12<tel:192.168.13.12> | | enable_dhcp | True | | gateway_ip | 192.168.18.1 | | host_routes | | | id | 5009ec57-4ca7-4e2b-962e-549e6bbee408 | | ip_version | 4 | | ipv6_address_mode | | | ipv6_ra_mode | | | name | testsubnet | | network_id | be2178a3-a268-47f4-809e-8e0024c6f054 | | subnetpool_id | | | tenant_id | ce581005def94bb1947eac9ac15f15ea | | updated_at | 2016-07-28T14:56:54 | +-------------------+------------------------------------------------------+
>
> root at controller:~# ovs-vsctl show d516b5b1-db3f-4acd-856c-10d530c58c23 Bridge br-dvs Port br-dvs Interface br-dvs type: internal Port "eth1" Interface "eth1" Bridge br-int Port br-int Interface br-int type: internal Port "tap91d8accd-6d" Interface "tap91d8accd-6d" type: internal ovs_version: "2.5.0"
>
> root at controller:~# ip netns qdhcp-be2178a3-a268-47f4-809e-8e0024c6f054
>
> root at controller:~# ip netns exec qdhcp-be2178a3-a268-47f4-809e-8e0024c6f054 ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
>
> tap91d8accd-6d Link encap:Ethernet HWaddr fa:16:3e:7f:5e:03 inet addr:192.168.18.246 Bcast:192.168.18.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe7f:5e03/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:648 (648.0 B)
>
> root at controller:~# ping 192.168.18.246 PING 192.168.18.246 (192.168.18.246) 56(84) bytes of data. ^C --- 192.168.18.246 ping statistics --- 20 packets transmitted, 0 received, 100% packet loss, time 18999ms
>
> I dont have any agents running. because vmware_nsx should be taking care of the communication with openvswitch.
>
> Commandline: apt install openvswitch-switch Install: openvswitch-switch:amd64 (2.5.0-0ubuntu1~cloud0), openvswitch-common:amd64 (2.5.0-0ubuntu1~cloud0, automatic)
>

[SL] You need to ensure you are using the version of OVS that is matched against your version of NSX. At this time, I don't believe it's OVS 2.5.0 (as noted in your command-line installation of OVS).
how to I ensure the supported version is installed. is there a support matrix? if so could you please share it?
--
Scott



--
Regards,

Vaidyanath
+91-9483465528<tel:%2B91-9483465528>(M)



--
Regards,

Vaidyanath
+91-9483465528(M)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160731/0d2db3aa/attachment.html>


More information about the Openstack mailing list