Dan Smith
ddef9dcfc0
Because we need to allow for a smooth upgrade from Ocata to Pike, we need Pike compute hosts to be tolerant of the bad accounting assumptions that Ocata compute hosts were making. If a user migrates an instance from an Ocata compute host to a Pike compute host, the Ocata compute host will continue essentially re-setting the instance allocation to be an allocation against only the source Ocata host (during the migration operation). We need to have the Pike destination compute host recognize when its in a mixed Ocata/Pike environment and tolerate this incorrect "healing" that the Ocata source host will do. To tolerate this, the Pike destination compute host must continue to behave like an Ocata compute host until all compute hosts are upgraded to Pike or beyond. Note that this adds service version caching for the compute service. We were already doing the lookup for the RPC pin and caching that, so this is not much of a change. Also note that we weren't clearing this caching in tests, so any test that ran code that cached the service version would affect later ones. This clears it as part of the base test setup too. Co-Authored-By: Jay Pipes <jaypipes@gmail.com> Change-Id: Ia93168b1560267178059284186fb2b7096c7e81f
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/badges/nova.svg
:target: https://governance.openstack.org/reference/tags/index.html
.. Change things from this point on
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:
- `Compute API Guide <https://developer.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://developer.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/