abalutoiu's profile - activity

Hello! Could you please try to live migrate a VM manually to see if it works? Are you running the nova-compute service with a user that has admin rights in the domain? Thanks, Alin.

Hello wangzhuo! Could you please give us more details about your environment? Are you using neutron-hyperv-agent or neutron-ovs-agent? What is your OpenStack version? Some logs would be also helpfully. Thanks, Alin.

Hello awestin1! Could you please look inside nova configuration file? You should have the vswitch_name under the hyperv section. That is where the VM will be attached. Could you share your nova config file too? Thanks, Alin.

Hello awestin1! Could you please change in your neutron_ovs_agent config file the option "rpc_backend=neutron.openstack.common.rpc.impl_kombu" to "rpc_backend=rabbit" and then restart the service? The previous blogpost was written for Newton, we will publish soon one for Ocata too. Thanks, Alin.

Hello Laci! Make sure that you are using OVS 2.6.1 on the Windows compute node since that comes with support for the openvswitch firewall_driver from OpenStack. Also please make sure you have in the config file under [ovs] "ovsdb_interface = vsctl" and "of_interface = ovs-ofctl". Thanks, Alin

Hello mario,

You could do the same on Hyper-V as you do on Linux. You have to add in neutronovsagent.conf the bridge_mappings under [ovs] group. Example:

[ovs]
bridge_mappings = public2:br-eth2

, where public2 is the name of the flat network from neutron and br-eth2 is the name of the bridge on the Hyper-V host. The only problem is that you have to use New-NetSwitchTeam to create a switch with the adapters that you'll use for OVS. Example:

New-NetSwitchTeam -Name team -TeamMembers "Ethernet1","Ethernet2"
New-VMSwitch -Name external -NetAdapterName team

After you created the switch in the way described above, you can issue the following (i.e.):

ovs-vsctl add-br br-port1
ovs-vsctl add-br br2
ovs-vsctl add-port br-port1 Ethernet1
ovs-vsctl add-port br2 Ethernet2

An example for bridge mapping for the above configuration is:

[ovs]
bridge_mappings = public2:br2

The bridge br-port1 is used for overlay network (tunneling ip) and br2 is used for flat network.

Thanks, Alin

Hello Loges! I see that you are trying to boot a qcow2 image on Hyper-V. Only vhd/vhdx images are supported on Hyper-V, could you please convert the image to vhd and then boot the VM? (qemu-img image-convert -f qcow2 -O vhdx <qcow2_image_name> <vhd_image_name>) Paste the log here after that. Thanks!

Hello! Unfortunately it seems that you need the enhanced RPC support to use firewall_driver with neutron OVS agent. This was implemented in Mitaka, you can either upgrade your environment, either try to backport to mitaka this patch https://review.openstack.org/#/c/263865 .

The firewall_driver=openvswitch can only be used since the Mitaka release, please upgrade your environment to Mitaka or above to be able to use this option.

Regarding the first issue, I think you're missing this commit https://github.com/openstack/networki... If that's the case, you need to add the commit on your Windows node. Here are the details on how you can achieve that:

git clone https://github.com/openstack/networking-hyperv
cd networking-hyperv
git checkout liberty-eol
net stop neutron-ovs-agent
pip install .
net start neutron-ovs-agent

Hello jrack! One fast solution would be to install rally somewhere else in a virtual environment and copy it where you want to use it. Being a virtualenv it should be self-contained.

Hello jrack, How recent is your rally deployment? There are a few things that have changed recently in the master branch. Our commits need to be rebased on top of the official master and tested. You can try to deploy our branch in a virtual environment to run our scenario tests. Thanks, Alin

There is a localization issue with the installer, we will release soon a fix for this issue. Thanks

OVS 2.4 has support only for a single NIC, 2.5 will have support for multiple NICs. What exactly are you trying to achieve using multiple NICs?

Hello Baptiste! Can you please run the following command in powershell on the Hyper-V host with the issue and put the output in a pastebin and paste a link here? Thanks! "Get-WmiObject -class Msvm_ComputerSystem -namespace root/virtualization/v2"

Hello JohnF,

Can you please try to remove the ports "internal" and "external1" from br-tun and add them inside a new bridge? You can do the following:

ovs-vsctl.exe del-port br-tun internal
ovs-vsctl.exe del-port br-tun external.1
ovs-vsctl.exe add-br br-ex
ovs-vsctl.exe add-port br-ex internal
ovs-vsctl.exe add-port br-ex external.1

Let us know if this fixes your issue.

Alin.