Ask Your Question
1

Networking Problems integrating Newton & VMWare vCenter

asked 2017-02-09 07:44:35 -0600

gianpietro gravatar image

I have Newton setup with Neutron and linux-bridges, where one of the compute nodes is configured to use VMwareVCDriver, however, when instantiating a VM and preparing the networking part, nova-compute complains about "vif type bridge not supported"

My nova.conf relevant config is, besides the driver and authentication credentials:

[vmware]
 ...
cluster_name = Cluster01
integration_bridge = brqfee5952c-2e
insecure=True

On the VCenter side (v6.5), inside Cluster01, I configured a "DSwitch" (with that name, not sure if relevant) with a Distributed Port Group named "brqfee5952c-2e". That bridge name corresponds to a public external network in my Openstack setup. I may be missing something here.

image description

image description

I'm trying to place a VM in the Openstack "public" network: 

openstack server create   --flavor 1CPU-1GBRAM-3GBDISK --nic net-id=fee5952c-2e90-4ced-8889-14c5cd8de34d --image "xenial-cloud-01" --availability-zone DC01 vm14

This is the nova-compute.log I'm getting:

2017-02-09 03:43:15.797 3898 INFO nova.compute.claims [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Claim successful
2017-02-09 03:43:16.502 3898 INFO os_vif [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] Loaded VIF plugin class '<class 'vif_plug_ovs.ovs.OvsPlugin'>' with name 'ovs'
2017-02-09 03:43:16.504 3898 INFO os_vif [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] Loaded VIF plugin class '<class 'vif_plug_linux_bridge.linux_bridge.LinuxBridgePlugin'>' with name 'linux_bridge'
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Instance failed to spawn
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Traceback (most recent call last):
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2078, in _build_resources
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     yield resources
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1920, in _build_and_run_instance
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     block_device_info=block_device_info)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 316, in spawn
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     admin_password, network_info, block_device_info)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py", line 739, in spawn
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     metadata)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py", line 281, in build_virtual_machine
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     network_info)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vif.py", line 178, in get_vif_info
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     is_neutron, vif))
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vif.py", line 164, in ...
(more)
edit retag flag offensive close merge delete
add a comment

1 answer

Sort by ยป oldest newest most voted
1

answered 2017-02-14 09:19:30 -0600

gianpietro gravatar image

Anyone interested in a testing environment for integrating Newton+Neutron with VMWare ESXi 6.5 in a basic way (with no support for internal networks, for example when there is no NSX to integrate Neutron with) please follow this steps:

  1. Follow Newton's official guide here: http://docs.openstack.org/newton/conf... and/or Jose Rigueras's guide here: https://gist.github.com/jriguera/2725...

  2. [hack] Restore some of the Liberty's code which allowed more than OVS or DVS as VIF types, here:

    ...  
else:
    network_id = vif['network']['bridge']
    network_ref = network_util.get_network_with_the_name(session,network_id, cluster)
    # reason = _('vif type %s not supported') % vif['type']
    # raise exception.InvalidInput(reason=reason)
return network_ref 
...

  3. Enjoy.

edit flag offensive delete link more

Comments

hi gian, if we have a distributed switch already create can use it apart from the brqfee5952c-2e like with name test or TEST can i use it or is there a way we can make use of it I tired making changes in nova-compute.conf to integartion_bridge = test or TEST, but it didn't work

jarvis@openstack gravatar imagejarvis@openstack ( 2017-06-02 01:24:03 -0600 )edit

instead it creates a portgroup with the brqfee5952c-2e name ,which is not connected to any host and spawn vm on that port group ( brqfee5952c-2e)

jarvis@openstack gravatar imagejarvis@openstack ( 2017-06-02 01:38:27 -0600 )edit
add a comment

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

3 followers

subscribe to rss feed

Stats

Asked: 2017-02-09 07:44:35 -0600

Seen: 934 times

Last updated: Feb 14 '17

Related questions

Packstack Newton configuration with VLAN interface

openstack network agent list empty output

Openstack: Could not load neutron.agent.linux.interface.OVSInterfaceDriver

Unable to ping IPs of VMs in provider network

ip netns doesnt show neutron namespaces

No IP address allocated to VM

Floating IP Configuration in Quantum + openvswitch

Neutron Static IP

[Juno] Neutron-metadata-agent can't start

Instance launch error. [closed]