Masakari never sets reason why compute service was disabled.
"disabled reason" was added in config.
Closes-Bug: 1936181
Change-Id: I998f7884195b93927773c7186d61c13670a53662
Previously Masakari enforced a common instance metadata key that
controlled how the HA protection applied to the instance:
"HA_Enabled".
Moreover, it was the same whether considering the instance or host
failure.
There are cases where users (operators) would like to independently
configure it per failure class and in general customize its name.
This patch implements the requested behaviour.
New tests are included.
Change-Id: I9dddf784da422f239ec304a2c0b8f24625914fc5
Implements: blueprint customisable-ha-enabled-instance-metadata-key
This patch uses taskflow's persistence feature to store recovery
workflows details into database.
Added a new microversion to return progress_details of the
notification in `GET /notifications/<notification_uuid>` API.
APIImpact:
GET /notifications/<notification_uuid> API includes details
of recovery workflow
Change-Id: I93c1b7d88823e02d9a02855cabb8b22c9e40a7d5
Implements: bp progress-details-recovery-workflows
This change adds hooks for pulling in plugins for
Interoperable recovery method customization taksflow
by configuring the actions in terms of execution order,
extra parameters to execute commands in action.
Implements: blueprint recovery-method-customization
Change-Id: I8150935ce0a4e592bd0f87bb3c7b3e599cefa033
Currently on master error instances are evacuated from failed
compute host and stopped at the destination host after evacuation.
Some operators may not want to evacuate error instances in some
cases like below:
If user is running 1ACT/n SBY application on instances, launching
error instances will cause unexpected effect.
This patch adds a new config option 'ignore_instances_in_error_state'
under [host_failure] section which makes the recovery of error
instances configurable. If this config option set to True, masakari
will skip the recovery of error instances otherwise it will evacuate
error instances from a failed source compute node along with other
instances. The default value for this config option is set to False.
Change-Id: I24f8282357f28544fd1b56f270da22c7329a9f3d
Reserved hosts can be shared between multiple host_aggregates. So
before evacuating the instances from failed_host to reserved_host,
the target resered_host should be added to the same aggregate in
which the failed_host is.
This patch adds the reserved_host to failed_host's aggregate.
Adding reserved_host to aggregate is optional and can be configured
by operators with the help of new configuration parameter
'add_reserved_host_to_aggregate' which is added under the 'host_failure'
section. This config option defaults to 'False'.
Change-Id: I7478e0f24ecd6fd6385dd67e7f0cad5ca3460526
evacuate_all_instances:
This option will allow operators to decide whether all instances
or only those instances which are "HA_Enabled" should be allowed
for evacuation from a failed source compute node.
process_all_instances:
This option will allow operators to decide whether all instances
or only those instances which are "HA_Enabled" should be taken
into account to recover from instance_failure events.
Implements: blueprint ha-enabled-config-options
Change-Id: I9998295f03e7663f1da79fe5024b1a7553355ac2
Mitya_Eremeev