Turning on HyperV support disables tunneling for entire environments
Bug #1725417 reported by
JPBD
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
High
|
Dan Ardelean |
Bug Description
When enabling HyperV support, tunneling is disabled for every environment which is unwanted. In an hybrid KVM/HyperV environment, Tunneling is required for the KVM part.
We do not know if it has to be explicitly disabled for HyperV. If it is the case, then tunneling should only be disabled for the HyperV part.
{% if neutron_
{% if not enable_hyperv | bool %}
[agent]
tunnel_types = vxlan
l2_population = true
arp_responder = true
{% endif %}
description: | updated |
description: | updated |
description: | updated |
Changed in kolla-ansible: | |
assignee: | nobody → Dan Ardelean (danardelean) |
Changed in kolla-ansible: | |
status: | New → Triaged |
milestone: | none → queens-1 |
importance: | Undecided → High |
To post a comment you must log in.
Hi,
The nova on HyperV supports two scenarios for networking/neutron: hyperv- agent which can NOT use tunneling (flat/vlan only)
1. neutron-
2. neutron-ovs-agent which CAN use tunneling
If you do a "Get-Service neutron*" in powershell you should see service.
In the current implementation, kolla nova-hyperv is only deploying neutron- hyperv- agent. However, vxlan can still be used for mix envs on KVM. So you are right, HyperV should not explicitly disable the vxlan bits. The ONLY limitation is that HyperV VMs can only use flat/vlan network types. So if you want your HyperV VMs to communicate with the KVM VMs, you'll need some routing, neutron-l3-agent for example, or floating IPs.
I will send a patch that removes the "if not enable_hyperv" restrictions.