091aa32896
In case of a baremetal instance, the instance's port binding:host_id gets updated during instance reboot to the nova compute host id by the periodic task: _heal_instance_info_cache. This regression was introduced in commit: I75fd15ac2a29e420c09499f2c41d11259ca811ae This is an un-desirable change as ironic virt driver did the original port binding, nova should not update the value. In case of a baremetal port, the binding:host_id represents the ironic node_uuid. In case of a SmartNIC(baremetal) port[1] the binding:host_id represent the SmartNIC hostname and it MUST not change since ironic relies on that information as well as the Neutron agent that runs on the SmartNIC. A new API method was added, "manages_port_bindings()", to ComputeDriver that defaults to False, and overriden in IronicDriver to True. A call to this API method is now made in _heal_instance_info_cache() to prevent port update for instance ports in case the underlying ComputeDriver manages the port binding. [1] I658754f7f8c74087b0aabfdef222a2c0b5698541 Change-Id: I47d1aba17cd2e9fff67846cc243c8fbd9ac21659 Closes-Bug: #1822801 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: