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 …
1 maintainer
Metadata
1 maintainer
Release files for freezer-dr 15.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| freezer-dr-15.0.0.tar.gz | 304.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| freezer_dr-15.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 358.0 kB
Release files / freezer-dr-15.0.0.tar.gz
| Download URL | freezer-dr-15.0.0.tar.gz |
|---|---|
| Size | 304.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf451618f9d1bf179bdf1e411ea681319f6c7ddc6fd93d39a4c04687a97e458f
|
|
BLAKE2b-256 checksum How to use checksums |
7bdb9c3abff3f0a602e0aa853c987f437ff56f1e63dcbfa7cc2c1a6b4a9892e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / freezer_dr-15.0.0-py3-none-any.whl
| Download URL | freezer_dr-15.0.0-py3-none-any.whl |
|---|---|
| Size | 54.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f865d199c6f8bb03e57310ca8553bc3d6cbd6b660115b2c81a2d624ffe606da0
|
|
BLAKE2b-256 checksum How to use checksums |
bf6898e5797a5e7ea3bf58dfc3edfdfba2f4e497cfc30b21373e4d10ab63bff3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for freezer-dr 15.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
