Skip to main content

OpenStack Disaster Recovery

Project description

Team and repository tags

https://governance.openstack.org/tc/badges/freezer-dr.svg

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 …

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

freezer-dr-12.0.0.0rc1.tar.gz (305.1 kB view details)

Uploaded Source

Built Distribution

freezer_dr-12.0.0.0rc1-py3-none-any.whl (54.1 kB view details)

Uploaded Python 3

File details

Details for the file freezer-dr-12.0.0.0rc1.tar.gz.

File metadata

  • Download URL: freezer-dr-12.0.0.0rc1.tar.gz
  • Upload date:
  • Size: 305.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.11

File hashes

Hashes for freezer-dr-12.0.0.0rc1.tar.gz
Algorithm Hash digest
SHA256 2b27e15e1bcff13b2da9aef4a70bf7222998430bfe6d6f69f18f3c7fd4794d05
MD5 2209091cb631014dc20b22816fa5358c
BLAKE2b-256 7ba4336318d5ada28187cd68a76abdeade5b97b0af63a5df25de4be95793f603

See more details on using hashes here.

Provenance

File details

Details for the file freezer_dr-12.0.0.0rc1-py3-none-any.whl.

File metadata

  • Download URL: freezer_dr-12.0.0.0rc1-py3-none-any.whl
  • Upload date:
  • Size: 54.1 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.8.0 pkginfo/1.8.2 readme-renderer/33.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.63.0 importlib-metadata/4.11.2 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.8.11

File hashes

Hashes for freezer_dr-12.0.0.0rc1-py3-none-any.whl
Algorithm Hash digest
SHA256 d59da022c012e772f9fba7b9f741eb989592691144299bb0233eb0af038f0b0d
MD5 70127768ebdb9bc3eaeafeedc3b25dda
BLAKE2b-256 29023779d9fe3d74d93669f49bbd2e1fb4f279f410f1061f92115671244e2847

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page