 | 1 | initial version |
Hello,
What OpenStack version are you using? If it's Ocata or newer, then it is as awestin says, you will have to execute that command on your OpenStack controller:
nova-manage cell_v2 discover_hosts
Additionally, After running this, you will most likely have to restart your nova services. The newly discovered hosts are not taken into account automatically (unless nova is configured to, but they're only recommending this config option if the compute nodes are expected to join / disconnect often and randomly).
At the very least you should see in the nova-scheduler logs that it takes into account 3 hypervisors after this. If it still fails after this, please check the nova-compute logs on the Hyper-V node (typically found at: C:\OpenStack\Logs).
If you see a PortBindingFailed Exception in the logs: what are your neutron networks' network_types and what L2 agent are you using on the Hyper-V node? (neutron agent-list, or on Hyper-V in powershell: Get-Service neutron*) . Neutron Hyper-V Agent doesn't support vxlan networks, and you'll have to setup and install OVS and the neutron-ovs-agent on the host (starting with Pike, we've included the neutron-ovs-agent installation and configuration in our OpenStack Hyper-V Compute MSI).
https://cloudbase.it/openvswitch/
Best regards,
Claudiu Belu
| | 2 | No.2 Revision |
Hello,
What OpenStack version are you using? If it's Ocata or newer, then it is as awestin says, you will have to execute that command on your OpenStack controller:
nova-manage cell_v2 discover_hosts
Additionally, After running this, you will most likely have to restart your nova services. The newly discovered hosts are not taken into account automatically (unless nova is configured to, but they're only recommending this config option if the compute nodes are expected to join / disconnect often and randomly).
At the very least you should see in the nova-scheduler logs that it takes into account 3 hypervisors after this. If it still fails after this, please check the nova-compute logs on the Hyper-V node (typically found at: C:\OpenStack\Logs).
If you see a PortBindingFailed Exception in the logs: what are your neutron networks' network_types and what L2 agent are you using on the Hyper-V node? (neutron agent-list, or on Hyper-V in powershell: Get-Service neutron*) . Neutron Hyper-V Agent doesn't support vxlan networks, and you'll have to setup and install OVS and the neutron-ovs-agent on the host (starting with Pike, we've included the neutron-ovs-agent installation and configuration in our OpenStack Hyper-V Compute MSI).
https://cloudbase.it/openvswitch/
Best regards,
Claudiu Belu
Update:
We've addressed this issue back when it was opened, but we haven't updated this thread, so I'll just write some updates here, just in case someone has a similar issue.
The Hyper-V driver was initializing properly. The nova-compute service, however, was getting stuck on this line: [1]. Basically, it was trying to reach to the nova-conductor service, but due to some Proxy configurations on the compute node, it was not able to reach it. The interesting thing was that the timeout was not taken into account, it should have timed out after about 10 seconds, and a warning should have been logged. This will probably have to be reported on nova's launchpad as a bug, and investigated further.
[1] https://github.com/openstack/nova/blob/master/nova/conductor/api.py#L66
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.