aee87c8e14
flake8 new release 3.8.0 added new checks and gate pep8 job start failing. hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new version with new checks. Though it is fixed in latest hacking but 2.0 and 3.0 has cap for flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also break the pep8 job if new check are added. To avoid similar gate break in future, we need to bump the hacking min version. Also removing the hacking and other related dep from lower-constraints file as theose are blacklisted requirements and does not need to be present there. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: Id693765fa9216f880d7105bbac3cd60f2db8500c |
||
|---|---|---|
| config-generator | ||
| doc | ||
| etc | ||
| freezer_dr | ||
| releasenotes/notes | ||
| tests | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .pylintrc | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CREDITS.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
Freezer Disaster Recovery
freezer-dr, OpenStack Compute node High Available provides compute node high availability for OpenStack. Simply freezer-dr monitors all compute nodes running in a cloud deployment and if there is any failure in one of the compute nodes freezer-dr will fence this compute node then freezer-dr will try to evacuate all running instances on this compute node, finally freezer-dr will notify all users who have workload/instances running on this compute node as well as will notify the cloud administrators.
freezer-dr has a pluggable architecture so it can be used with:
- Any monitoring system to monitor the compute nodes (currently we support only native OpenStack services status)
- Any fencing driver (currently supports IPMI, libvirt, ...)
- Any evacuation driver (currently supports evacuate api call, may be migrate ??)
- Any notification system (currently supports email based notifications, ...)
just by adding a simple plugin and adjust the configuration file to use this plugin or in future a combination of plugins if required
freezer-dr should run in the control plane, however the architecture supports different scenarios. For running freezer-dr under high availability mode, it should run with active passive mode.
How it works
Starting freezer-dr:
- freezer-dr Monitoring manager is going to load the required monitoring driver according to the configuration
- freezer-dr will query the monitoring system to check if it considers any compute nodes to be down ?
- if no, freezer-dr will exit displaying No failed nodes
- if yes, freezer-dr will call the fencing manager to fence the failed compute node
- Fencing manager will load the correct fencer according to the configuration
- once the compute node is fenced and is powered off now we will start the evacuation process
- freezer-dr will load the correct evacuation driver
- freezer-dr will evacuate all instances to another computes
- Once the evacuation process completed, freezer-dr will call the notification manager
- The notification manager will load the correct driver based on the configurations
- freezer-dr will start the notification process ...