Artom Lifshitz
0b0f40d1b3
This reverts commit7a7a223602. That commit was added because - tl'dr - upon revert resize, Neutron with the OVS backend and the iptables security group driver would send us the network-vif-plugged event as soon as we updated the port binding. That behaviour has changed with commit66c7f00e1d. With that commit, we started unplugging the vifs on the source compute host when doing a resize. When reverting the resize, the vifs had to be re-plugged again, regarldess of the networking backend in use. This renders commit7a7a223602. pointless, and it can be reverted. Conflicts - most have to do with context around this commit's code: nova/compute/manager.pya2984b647aadded provider_mappings to _finish_revert_resize_network_migrate_finish()'s signature750aef54b1started using _finish_revert_resize_network_migrate_finish() in _finish_revert_snapshot_based_resize_at_source() nova/network/model.py8b33ac0644added get_live_migration_plug_time_events() and has_live_migration_plug_time_event()7da94440dbadded has_port_with_allocation() nova/objects/migration.pyf203da3838added is_resize() and is_live_migration() nova/tests/unit/compute/test_compute.pya0e60feb3eadded request_spec to the test nova/tests/unit/compute/test_compute_mgr.pybe278006a5added unit tests below ours nova/tests/unit/network/test_network_info.py7da94440db(again) added tests for has_port_with_allocation() nova/tests/unit/virt/libvirt/test_driver.py and nova/virt/libvirt/driver.py are different in that attempting to identify individual conflicts is a pointless exercise, as so much has changed (mdev, vtmp, the recent wait for events during hard reboot workaround config option, etc). They can be treated as manual removal of any code that had to do with the bind-time events logic (though guided by the conflict markers in git). TODO(artom) There was a follow up commit,78a08d44ea, that added the migration parameter to finish_revert_migration(). This is no longer needed, as the migration was only used to obtain plug-time events. We'll have to undo that as well. Closes-bug: 1952003 Change-Id: I3cb39a9ec2c260f422b3c48122b9db512cdd799b
==============
OpenStack Nova
==============
.. image:: https://governance.openstack.org/tc/badges/nova.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
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, 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:
- `Compute API Guide <https://docs.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://docs.openstack.org/api-ref/compute/>`__
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
- `OpenStack for App Developers <https://www.openstack.org/appdev/>`__
- `Development resources for OpenStack clouds
<https://developer.openstack.org/>`__
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the documentation
available online at:
- `OpenStack Nova <https://docs.openstack.org/nova/>`__
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:
- `Bug Tracker <https://bugs.launchpad.net/nova>`__
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:
- `Official Nova Documentation <https://docs.openstack.org/nova/>`__
- `Official Client Documentation
<https://docs.openstack.org/python-novaclient/>`__
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:
- `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__
.. _Summit: https://www.openstack.org/summit/
.. _Project Team Gathering: https://www.openstack.org/ptg/