When using karbor to restore server to another openstack
cluster(cross keystone), and if the another cluster do not
have the same flavor id, the restore will fail. We should
add support for adding flavor id as a parameter to rewrite
the flavor id in checkpoint metadata.
Change-Id: Ie5c7a1adf07b7f9b1225ee4a5e16000a3453a7cc
Closes-Bug: #1811090
Currently, server restore can only use the networks
in checkpoint metadata. When the network was deleted
or rebuilded, the restore will fail. So this patch
add a new restore parameter to specify the restore
network id.
Change-Id: I003c68de094b8d11bbdd7dd07bec0c1d1e580652
Closes-Bug: #1713887
Use a dict to store the new restored resources, and parent
resource can get the new resource id of child resources from
that dict.
Change-Id: I4a3fbe009793d16514de89b520bd68581be401af
Implements: blueprint remove-heat
Object store interface has no difference between create and update.
Remove create_object from any Bank or BankSection. update_object can be
used instead in order to create and/or update objects.
Change-Id: I70bf5b7b4ffcc5ac43281d1be7f8ff10e5451b39
Protection plugin now needs to implement methods for each operation
(protect, delete, restore). Each protection plugin is created in the
context of the flow, while each operation is created in the context of
the resource.
A protection plugin is responsible for returning an Operation class for
each operation. Such Operation class defines the behavior of the
protection plugin by implementing these optional hooks:
- on_prepare_begin hook is invoked before any hook of this resource and
dependent resources has begun
- on_prepare_finish hook is invoked after any prepare hooks of dependent
resources are complete.
- on_main hook is invoked after the resource prepare hooks are complete
- on_complete hook is invoked once the resource's main hook is
complete, and the dependent resources' on_complete hooks are complete
HeatTemplate is now created and supplied from a task instead of being
created and passed to resource tasks before the restore operation began.
Change-Id: I847eec6990b2d24a66a12542d242fbfb682272fe
Co-Authored-By: Saggi Mizrahi <saggi.mizrahi@huawei.com>
Implements: blueprint protection-plugin-is-design
There were a few log strings that were not using the appropriate
translation marker for their given log level.
Also fixed a couple cases of passing in an exception to a LOG.exception
call. LOG.exception will automatically log whatever exception is in
scope, so switched these to be the equivalent LOG.error levels so the
exceptions do not get logged twice.
Change-Id: If1be4661174dfcf30567b5093bd5373c2c275cf5