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.
OpenDev Sysadmins bfc94b0706 OpenDev Migration Patch 4 weeks ago
config-generator freezer-dr big bang 3 years ago
doc Update .gitignore 6 months ago
etc Set default notifier endpoint 7 months ago
freezer_dr Update tox.ini and fix pep8 errors 6 months ago
tests Adding pep8, pylint, coverage, sphinx testing 3 years ago
.coveragerc Adding pep8, pylint, coverage, sphinx testing 3 years ago
.gitignore Update .gitignore 6 months ago
.gitreview OpenDev Migration Patch 4 weeks ago
.pylintrc update pylint 9 months ago
.stestr.conf Switch to stestr 10 months ago
.zuul.yaml Dropping the py35 testing 1 month ago
CREDITS.rst Adding CREDITS.rst 3 years ago
HACKING.rst Fix wrong links 1 year ago
LICENSE Add LICENSE file 2 years ago
README.rst Change according to preferred word choice 2 years ago
lower-constraints.txt Update tox.ini and fix pep8 errors 6 months ago
requirements.txt Update tox.ini and fix pep8 errors 6 months ago
setup.cfg Dropping the py35 testing 1 month ago
setup.py Update pbr version 6 months ago
test-requirements.txt Update tox.ini and fix pep8 errors 6 months ago
tox.ini Dropping the py35 testing 1 month ago

README.rst

Team and repository tags

image

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 ...