081cd5fae9788756bd37398fd2ed7fef62af4622
The decision engine process was built based on 2 services: a service that handle rpc requests and a scheduler to trigger watcher periodic tasks. With the new version of oslo.service, a new threading backend was added, based on cotyledon service manager, which starts a new process for each service tha it manages. These two services can't run in different process since they need access to a shared in-memory representation of the cluster (cluster data models) This patch proposes creating a Decision Engine Service which includes everything in a single main service. Change-Id: I335a97ca14b6e023fef055978a56aefebf22d433 Signed-off-by: Douglas Viroel <viroel@gmail.com>
=======
Watcher
=======
.. image:: https://governance.openstack.org/tc/badges/watcher.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
..
Except where otherwise noted, this document is licensed under Creative
Commons Attribution 3.0 License. You can view the license at:
https://creativecommons.org/licenses/by/3.0/
OpenStack Watcher provides a flexible and scalable resource optimization
service for multi-tenant OpenStack-based clouds.
Watcher provides a robust framework to realize a wide range of cloud
optimization goals, including the reduction of data center
operating costs, increased system performance via intelligent virtual machine
migration, increased energy efficiency and more!
* Free software: Apache license
* Wiki: https://wiki.openstack.org/wiki/Watcher
* Source: https://opendev.org/openstack/watcher
* Bugs: https://bugs.launchpad.net/watcher
* Documentation: https://docs.openstack.org/watcher/latest/
* Release notes: https://docs.openstack.org/releasenotes/watcher/
* Design specifications: https://specs.openstack.org/openstack/watcher-specs/
Description
Languages
Python
99.7%
Shell
0.3%