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
For PDFLaTeX, remove the irrelevant parts (contributing,
search) and those that break (full config examples).
Additionally, this replaces fancy quotes as they don't work
in PDFLaTeX either (it handles regular quotes internally).
Change-Id: I60459407e49a88c2231217152fc078346e5f4b4f
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
The "default" section is invalid in masakari.conf
file. This patch changes "default" to "DEFAULT" so
that the configurations under "DEFAULT" section
become effective.
Change-Id: Ibc510653312d82529ea41b555b68f823c02c3078
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
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
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
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
Now we support only python 3.6 and higher versions so we don't need
this condition. Also it will fix the requirements-check job.
Change-Id: I653c98e5dac9b1f094803ff840ccef7b0dac198d
If you query a host passing an existing failover segment but not
the one that is assigned to the host, it still returns the host
successfully. In this case, it should fail with 404 error.
This patch checks if the host belongs to the segment that is
present in the URI. If not, it will return 404 error.
Change-Id: I16256cc2a01696a1d54cb9326aed17b723b87727
Closes-Bug: #1854323
Corrected json data which was indented using tabs instead of spaces.
Also corrected key in response dict of host `create` and `get` to
singular since user can create/update single host in a request.
Change-Id: I19f9c620d348d40fde720557bca06b9fe1f95401
Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
Change-Id: I031feb46aee4e33fab0f96d033a32198a742214e
Updated operator guide documentation for
1. segregated sections appropriately
2. referred masakariclient for CLI section
3. added detailed 'Install and configure for Ubuntu' section
4. added detailed 'Verify operation' section
5. used sphinx-build instead of the pbr sphinx extention for building docs
as instructed by the PTI[1]
6. cleaned up build_sphinx related entries in setup.cfg
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html#documentation
Change-Id: Iec93bebdbc7ffe1ccd27bb11f474384ff06a559c
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>
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I4596e5c35143c0e7757cdf2acabdd6eac98159ea
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 commit adds the functionality of masakari-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.
Change-Id: I17c79af15eca5f6da7e32dbedbdc392c97114d42
Story: 2003657
Task: 26140
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
Adds below things for the implementation of framework for registering and
using default policy rules.
* Policy-in-code
The framework for registering and using default policy rules.
Rules should be defined and returned from a module in
masakari/policies/, and then added to the list in masakari/policies/__init__.py.
A new context.can() method has been added for policy enforcement of
registered rules. It has the same parameters as the enforce() method
currently being used.
* Add policy sample generation
The entry point and config file necessary for using the
oslo.policy sample generation script. It also adds a tox target to
simplify the usage of it.
* Add policy documentation and sample file
Documentation and sample file for default policy in code feature.
* Hacking check for policy registration
It ensures that policy registration happens in the centralized
masakari/policies/ directory.
* Hacking check for _ENFORCER.enforce()
Hacking check in order to ensure that only registered policies
are used for authorization checks _ENFORCER.authorize should be used rather
than _ENFORCER.enforce.
* Add entry_point for oslo policy scripts
There are two helper scripts in oslo.policy to help deployers understand
their policy configuration better. With the setup.cfg entry these can be
called directly from oslo.policy.
Changes done here are with the reference of [1] at NOVA side
which is contributed by Andrew Laski and Claudiu Belu
[1] https://review.openstack.org/#/q/topic:bp/policy-in-code+project:openstack/nova+status:merged
Change-Id: If885a66d92c31be440d27d6780635800a0b12e3e
Added documentation for how to get involved, development qucikstart
and masakari system architecture.
Change-Id: Ie2cbdde7698a79a1b996e485d141eb15dbded4cd
Added api specifications for versions, segments, hosts and
notifications as per OpenStack standards.
Change-Id: Iefc83254e22fc31d1f0d13f52e71d42c63e82b7d
wangkuntian