Tools and automation to achieve Disaster Recovery of OpenStack Cloud Platforms
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul ba060b277d Merge "Updating python testing classifier as per Yoga testing runtime" 7 months ago
config-generator freezer-dr big bang 7 years ago
doc [ussuri][goal] Update contributor documentation 2 years ago
etc Set default notifier endpoint 4 years ago
freezer_dr Remove the __future__ modulue 3 years ago
releasenotes/notes [ussuri][goal] Drop python 2.7 support and testing 3 years ago
tests Adding pep8, pylint, coverage, sphinx testing 7 years ago
.coveragerc Adding pep8, pylint, coverage, sphinx testing 7 years ago
.gitignore Update .gitignore 4 years ago
.gitreview OpenDev Migration Patch 4 years ago
.pylintrc Fix pylint error 1 year ago
.stestr.conf Switch to stestr 4 years ago
.zuul.yaml Drop lower-constraints.txt and its testing 7 months ago
CONTRIBUTING.rst [ussuri][goal] Update contributor documentation 2 years ago
CREDITS.rst Adding CREDITS.rst 7 years ago
HACKING.rst Sync Sphinx requirement 3 years ago
LICENSE Add LICENSE file 6 years ago
README.rst Sync Sphinx requirement 3 years ago
bindep.txt Add bindep to fix py37 tests 3 years ago
requirements.txt Update CI jobs for wallaby 2 years ago
setup.cfg Updating python testing classifier as per Yoga testing runtime 12 months ago Cleanup py27 support 3 years ago
test-requirements.txt Fix hacking min version to 3.0.1 2 years ago
tox.ini Merge "Updating python testing classifier as per Yoga testing runtime" 7 months ago


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:

  1. Any monitoring system to monitor the compute nodes (currently we support only native OpenStack services status)
  2. Any fencing driver (currently supports IPMI, libvirt, ...)
  3. Any evacuation driver (currently supports evacuate api call, may be migrate ??)
  4. 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:

  1. freezer-dr Monitoring manager is going to load the required monitoring driver according to the configuration
  2. freezer-dr will query the monitoring system to check if it considers any compute nodes to be down ?
  3. if no, freezer-dr will exit displaying No failed nodes
  4. if yes, freezer-dr will call the fencing manager to fence the failed compute node
  5. Fencing manager will load the correct fencer according to the configuration
  6. once the compute node is fenced and is powered off now we will start the evacuation process
  7. freezer-dr will load the correct evacuation driver
  8. freezer-dr will evacuate all instances to another computes
  9. Once the evacuation process completed, freezer-dr will call the notification manager
  10. The notification manager will load the correct driver based on the configurations
  11. freezer-dr will start the notification process ...