New Question
0

nova-compute not attaching VM to a Hypver-V vSwitch

asked 2015-02-06 11:52:26 +0200

Aaron Johnson gravatar image

Running Cloudbase Nova Compute (and Open vSwich) on a Windows Server 2012R2 compute node. Instances launch, but looking at the VMs in the Hyper-V manager shows network adpaters not connected to a virtual switch. Looking up the VMs ports in The neutron cli looking at the VM's port shows me that virtual interface binding has failed (binding:viftype is bindingfailed) and its status is DOWN.

I think I followed the directions for the Open vSwitch setup correctly. But I haven't had much luck deciphering the logs. Could someone give me a hint as to what I should be looking for in the nova-compute log? Much obliged...

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2015-02-10 19:12:02 +0200

aserdean gravatar image

Hi Aaron,

Can you please tell me what you have installed and maybe tell me some pointers on what are you trying to achieve?

Open vSwitch integration with Nova is still undergo and only a POC is available.

Thanks, Alin.

edit flag offensive delete link more

Comments

Installed are: * Cloudbase HyperVNovaCompute_Juno_2014_2_1 revision {A66D13E0-CE61-47E0-8692-CD1DEA3AC082} dated 12/12/2014 4:10AM. * Cloudbase Open vSwitch for Hyper-V revision {901E9957-BDE3-4140-9750-93919011F52B} dated 1/26/2015 12:15AM (rev number and content date pulled from the MSI file's properties in Windows Explorer) * Running on Windows Server 2012r2 with the Hyper-V role. Up to date as far as Windows Update is concerned) I can create and launch an instance. It runs. However, the Hyper-V VM's virtual NIC is not attached to a Hyper-V virtual switch when it is created. (Virtual switch is set to "Not connected" in the Hyper-V manager.) I have checked nova.conf file's hyperv vswitch_name setting. It matches the name of the Hyper-V virtual switch. neutron_hyperv_agent.conf's physical_network_vswitch_mappings setting matches the name of the Hyper-V virtual switch as well. At this point, all I want to acheive is nova-compute attaching the VMs it created to a Hyper

Aaron Johnson gravatar imageAaron Johnson ( 2015-02-10 20:53:01 +0200 )edit

Grrr. Where are my line breaks? What I want to achieve is Nova-compute creating a VM and attaching it to a Hyper-V virtual switch instead of "not connected" From there, I want to create a port on my Open vSwitch config and attach the VM to that. And from that point, talking to the rest of my Neutron networks would be stupendous. One step at a time, though...

Aaron Johnson gravatar imageAaron Johnson ( 2015-02-10 20:55:51 +0200 )edit

The Nova Compute installer does not contain the integration with Open vSwitch because the POC has not been integrated upstream yet. I will post some links tomorrow and hints on how to integrate it and setup the environment. It will require some hacks :).

aserdean gravatar imageaserdean ( 2015-02-11 00:19:04 +0200 )edit

Thank you, Alin. Can you offer any info on why the Hyper-V VM is not being attached to the Hyper-V virtual switch when it is created?

Aaron Johnson gravatar imageAaron Johnson ( 2015-02-11 02:03:58 +0200 )edit

Any updates on this? I'm in the same situation, vm launch and everythings works great if I attach the switch manually after launch. I need this to happen in an automated fashion. -randy

pthornton gravatar imagepthornton ( 2015-03-27 17:46:11 +0200 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2015-02-06 11:52:26 +0200

Seen: 405 times

Last updated: Feb 10 '15