If the recovery policy uses uppercase, an error will be reported.
This patch modifies these to lowercase.
Closes-Bug: #1914482
Co-Authored-By: zhangyangyang <zhangyangyang@unionpay.com>
Change-Id: Ic4bf5a4b19df07364c09fd46f1a92a809c77b241
Nova services and hypervisor naming can differ, as they retireve node
names in different way.
In the meanwhile we operate with nova.services while enabling/disabling
nodes duringh the incident. So we're supposed to have in database record
matching to what we have in service list, but not in hypervisor list.
Closes-Bug: #1839715
Change-Id: I9c591d33f17a8d5950bdb1fc2d686e2301fc6d95
Switch to openstackdocstheme 2.2.1 and reno 3.1.0 versions. Using
these versions will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
Remove docs requirements from lower-constraints, they are not needed
during install or test but only for docs building.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Ib8c912844becebbfef3bf6579ebea9350676a322
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
Presently, you can update host name with any non-existing host name.
It doesn't check whether this host exists or not in nova. This patch
fixes this issue by checking whether the host name exists in nova or
not before updating it. If it doesn't exists, it will raise 400 error.
APIImpact
BadRequest(400) is returned if host doesn't exists in nova instead of
200 during host update.
Closes-Bug: #1814656
Change-Id: Ibd113f2328deae0f1114544436631bdc434eff92
This patch validates the notification payload at schema level as per
API ref document[1]. Raises BadRequest(400) if payload is incorrect
based on notification type.
APIImpact
BadRequest(400) is returned if payload is incorrect instead of 202
during notification create.
Closes-Bug: #1808513
[1]: https://developer.openstack.org/api-ref/instance-ha/
Change-Id: Iccad15a955be1b11f31d829624d43b6ea915305c
Presently, you can add any hostname to the failover segment. It
doesn't check whether this host exists or not in nova. This patch
fixes this issue by checking whether the hostname exists in nova or
not before adding it to the failover segment. If it doesn't exists,
it will raise 400 error.
APIImpact
BadRequest(400) is returned if host doesn't exists in nova instead
of 200 during host create.
Closes-Bug: #1800073
Change-Id: I0ccc9f3a61e3f17f2cb7c1ad1888947c6fe724c8
Added api specifications for versions, segments, hosts and
notifications as per OpenStack standards.
Change-Id: Iefc83254e22fc31d1f0d13f52e71d42c63e82b7d
suzhengwei