The original design is to save instance evacuations information
for host failure notification. For later new features, there will
be instance migrations information for host restored notification.
It is more compatible to use vm move (vmove) object, wihch
include 'type' filed to show it is one evacuation or migration.
Blueprint: vm-evacuations-for-host-recovery
Change-Id: Ic0d1283bebbc562cfd20e004cb9b6ed309d0fd28
This spec introduces a new host monitor by consul. It monitors host
heartbeat via management, tenant and storage connectivity. Only in the
case of defined HA strategy, it will trigger host recovery, for example,
storage interface disconnected.
Change-Id: If81a6a9543513acf199afe6a17dceb1544657272
Implements: bp host-monitor-by-consul
When large scale hosts failed in the same time, there would be
not enough resources to recovery all the instances. So it needs
a priority to determine which one to evacuate firstly. Moreover,
the user even wants to recall the instances to the original host
after host recovery. So it needs to keep some necessary information
aboud evacuations for new features.
Change-Id: I7c87c8d4a2ab5898d1b0d046a1377fe1ed7c79ee
Blueprint: vm-evacuations-for-host-recovery
If the platform has a bad network stability, judging from pacemaker and
corosync, the host status would swing between up and down. It would
result in host recovery, which is not expected.
Repeated check is more reliable than once check to determine host
status.
Change-Id: I61a4a05f912c764d77bca87f5a297b6da42b9ae7
Implements: bp retry-check-when-host-failure
If 'enable' of one failover segment is set False, all notifications
which belong to this failover segment will be ignored, so that
no recovery flow executes.
Change-Id: I418aaa9c34826dd908363d91e0df718f55721536
Implements: bp enable-to-segment
Add the sphinx-build for this project, remove 'oslosphinx' and add
'penstackdocstheme' to support python3.
Closes-Bug: #1836551
Change-Id: I0aac32c27436671841becada6e6da238c0913631
Taskflow supports persistence of task which helps to persist each
task details in the database. Using this functionality, Masakari
will store task details for recovery failures.
Change-Id: I4fe394f473a93aedc9e167bbde3dd196cfc89559
Implements: bp progress-details-recovery-workflows
Typical openstack services have event notification feature[1].
This spec adds the such feature for masakari.
[1]: https://docs.openstack.org/developer/nova/notifications.html
Change-Id: I4fc551d82fa0a0531676cfd7fbc787c493e2839b
Implements: bp notifications-in-masakari
Implements the spec recovery method customization by
configuring the actions in terms of execution order,
extra parameters to execute commands in action etc.
blueprint: recovery-method-customization
Change-Id: Ibc80ae0a749bd0a53a432a600ca9f0aaa16d5973
This patch adds rocky specs repo.
In addition to that it also fixes below issues:
1. Adds a single template.rst for all branches in
doc/source/specs repo.
2. Fixes incorrect references in history section.
3. Creates missing symbolic links to specs templates.
4. Moves implemented specs from 'approved' to 'implemented'
directory.
In future we should have a tox script similar to [1] for
moving implemented specs from approved to implemented directory.
[1] dad9782fc1/tox.ini (L32)
Change-Id: I4499facd28b1cc48d425a8fe15930ebaa4ac24d9
Add db purge support to masakari-manage command which will purge
the deleted/unused records from the database.
Implements: blueprint db-purge-support
Change-Id: Ie2df29bf459dcfab98dfbbf979d4334b35ec4275