Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I729ddc3c1f672c2c9840dce2982792154fd8f1ae
This is easier than Cinder, Nova etc. but more difficult than Heat.
Masakari hasn't had many database migrations in recent cycles but it did
have on in Antelope. This means we need to handle people doing
skip-level upgrades and validate which version of the legacy migrations
they are currently on. We support users coming from both Zed and
Antelope and anyone else will need to go through an older version of
Masakari to update their database migrations first. Other than this
difference, the logic is pretty similar: as with other projects, we
simply determine if we're upgrading a deployment that was previously
using sqlalchemy-migrate, upgrading a deployment that has already
migrated to alembic, or deploying a new deployment, and adjust
accordingly.
In addition, we also have to consider Taskflow's migrations. These were
previously being run once as part of the legacy
006_add_persistence_tables migrations. Since Taskflow uses Alembic under
the hood, it's safe to run every time. The presence of Taskflow does
force us to use a different table name in Masakari though.
Note that one curious side-effect of this is that the order than table
rows are purged change. This appears to be happening because the
notification table is now being created in the initial Alembic
migration, which alters the return value of 'MetaData.sorted_tables'.
In any case, the fix is simply a case of adjusting this order in the
tests.
Change-Id: I5285d7cc3c6da0059c0908cedc195b2262cb1fce
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: I9c0c1aebda728918029eb05f307c285581d8f0d7
For instance or process failure workflow, the failure notification
would stuck into running status if timeout.
Closes-Bug: #1996835
Change-Id: I61e941ab9dd831369fcc46a132ae2b11c1dd23ba
If an user sends host notification without host status:
openstack notification create COMPUTE_HOST <host> <date> '{"event": "STOPPED"}'
logging registers silly error like object None has not method 'upper' and
notification gets status 'running', host is set in maintenance status.
It's impossible to set manually host status to non-maintanence
until there are host-related running notifications.
Running notifications are expired in 24 hours by default.
The patch makes engine to set 'ignore' status for such
notifications.
Closes-Bug: 1960619
Change-Id: Id873b3300b6de49082805654c85414a8868dd925
Add file to the reno documentation build to show release notes for
stable/zed.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/zed.
Sem-Ver: feature
Change-Id: I20befc055a4d271bf0dd62434745c6bd4b67fa9d
Nova-compute would periodically sync the instance status. So in the
instance failure recovery workflow,it would stop instance random failed
because of conflict, which will terminate the recovery workflow.
This patch can catch the Confict exception and continue the recovery
workflow if the instance already stopped.
Closes-Bug: 1980736
Change-Id: I59a1f9d7078614c1ddc8f4c362e967a15b8ec5e8
Two concurrent events that host is down
might be accepted by different instances of API
which triggers two evacuation workflows for instances.
Patch introduces distributed lock for creation of
host type notifications. It solves the issue.
Closes-Bug: 1961110
Change-Id: Ie8f10b14f29a8548181560cd8a26b4dc79afc3dc
Add file to the reno documentation build to show release notes for
stable/yoga.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/yoga.
Sem-Ver: feature
Change-Id: I41d60acdaffb3f3c770494914afbd07f77a133b8
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: Id0f01f7d9197e8cdba5fc292aba6ef17b98c96d0
Masakari never sets reason why compute service was disabled.
"disabled reason" was added in config.
Closes-Bug: 1936181
Change-Id: I998f7884195b93927773c7186d61c13670a53662
Add file to the reno documentation build to show release notes for
stable/wallaby.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/wallaby.
Sem-Ver: feature
Change-Id: I1188a0375425fd0b73b7702ecbc93c4d7033e662
This patch fixes the code that assignes aggregates to the reserved_host.
The existing code only assigned a aggregate that first matched failed
compute host name.
By this fix, all aggregates that ware assigned to the failed host can
be assigned to the reserved_host.
Closes-Bug: #1856164
Change-Id: I8a727e3c50b71a5ad52d58d0ba3bde4f09446748
If you request to show details of versions "v1/" API it returns 404
ResourceNotFound.
This patch fixes this issue by updating the v1 version correctly
as "v1.0" in versions controller which helps wsgi layer to find
the resource(controller) correctly. This way it returns the details
of version "v1" correctly instead of ResourceNotFound.
v1 show API response:
{"version": {"status": "CURRENT", "updated": "2016-07-01T11:33:21Z",
"links": [{"href": "http://<host-ip>:15868/v1/", "rel": "self"},
{"href": "http://docs.openstack.org/", "type": "text/html",
"rel": "describedby"}], "min_version": "1.0", "version": "1.0",
"media-types": [{"base": "application/json",
"type": "application/vnd.openstack.masakari+json;version=1"}],
"id": "v1.0"}}
This patch fixes the reported supported microversion as well
to avoid clients failing due to requesting too new version
(LP#1882516). It has to be fixed to pass tests.
APIImpact - versions "v1/" show API will return 200 OK now instead
of 404 ResourceNotFound.
Closes-Bug: #1685145
Closes-Bug: #1882516
Co-Authored-By: Jegor van Opdorp <jegor@leaf.cloud>
Co-Authored-By: suzhengwei <sugar-2008@163.com>
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
Change-Id: If3943060b5d09bd153b6401d34c7d10d3dc864fe
Since Ussuri, nova can be configured with new policy
defaults. These defaults enforce the need to use system-scoped
tokens for admin operations like listing hypervisors.
The new os_system_scope configuration allows masakari to
request a system-scoped token using keystoneauth1 to query nova.
Implements: blueprint support-nova-system-scope-policies
Change-Id: I5f5b3f05358c28d60cfd05bc62a388f9087d75ac
Sometimes, operators want to temporarily close instance-ha function.
This patch add 'enabled' to segment. If the segment 'enabled' value
is set False, all notifications of this segment will be ignored
and no recovery methods will execuate.
Change-Id: I561a2519626fa1beae1e3033a6de510cea8f3fac
Implements: BP enable-to-segment
This should help us write better release notes (or write them
at all in the first place :-) ).
This is an adaptation of the work I have done for Kolla in [1].
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/759254
Change-Id: I60ff41d721117a9e973c02e3e2a2fdf6550960a7
This patch allows user to pass a multiline description for
a failover segment.
Closes-Bug: #1776385
Change-Id: I25afb76aec10a507312b8d99b0c882ca9f6bcd81
Fixes an issue where a failed evacuation could result in a periodic
looping call to run forever. This happened because the periodic call was
not stopped after a timeout occurred.
Change-Id: Id3b9bad4bc617c168200d34d69bbe760a24dfcf9
Closes-Bug: #1897888
As per the community goal of migrating the policy file
the format from JSON to YAML[1], we need to do two things:
1. Change the default value of '[oslo_policy] policy_file''
config option from 'policy.json' to 'policy.yaml' with
upgrade checks.
2. Deprecate the JSON formatted policy file on the project side
via warning in doc and releasenotes.
Also replace policy.json to policy.yaml ref from doc and tests.
[1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html
Change-Id: Iad942530b5d540af3d3c074e9944687b93bcd7f2
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Change-Id: I218cadae63065fb650e1a52ea9ced3c1a27441ed
Sem-Ver: feature
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
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
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
Add file to the reno documentation build to show release notes for
stable/ussuri.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/ussuri.
Change-Id: I8d23a06952a74d7605d78d540e59a03128afebc5
Sem-Ver: feature
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I1a3bd45beb70175765afc8082729047e3f35ef3b
Sem-Ver: feature
The oslosphinx package is not compatible with the current Sphinx 2.0
release. Migration has been happening to openstackdocstheme for some
time. To fix build failures for docs and releasenotes jobs, this
switches masakari jobs to use openstackdocstheme.
Uncapping jsonschema to pass requirements check so it matches global
requirements.
Change-Id: Ic74e8b075aa67d410617dac3346bf1c903995da7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Zuul
OpenStack Release Bot