Ghanshyam Maan
82fd8ffdce
For the compute service graceful shutdown, we need two RPC servers. 1st RPC server will used for the new requests and 2nd for completing the in-progress tasks. The 2nd RPC server will use the same transport bus and same endpoint (compute manager instance) but listen to the different topic then 1st RPC server. By having two different topics, other service (API, conductor, or compute) can make difference on which topic they want to send the RPC request to the compute service. That will be done via RPC client sending the request to specific topic. This change stop both RPC servers but later in this series we will keep the 2nd RPC server active so that compute service can listen to the in-progress tasks required communication coming from other services. The next change in this series will use this 2nd RPC server. The tasks (compute RPC client methods) who needs to be using this 2nd RPC server will be modified in the next change. Partial implement blueprint nova-services-graceful-shutdown-part1 Change-Id: I26656869f00efe6d89d993000dcf2e91683a217e Signed-off-by: Ghanshyam Maan <gmaan@ghanshyammann.com>
============== OpenStack Nova ============== OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), VMware and OpenStack Ironic. 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. To understand better the processes that the team is using, please refer to the `Process document <https://docs.openstack.org/nova/latest/contributor/process.html>`__. 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/