No migrations yet: this is simply the output of 'alembic init' with some
minor tweaks.
Change-Id: Ib9423c2f751d7ec0a0dec89bdc39f9b6ab043655
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
We also bump the hacking version and remove some unnecessary notes from
the top of the requirements files: these don't apply with the dependency
resolver introduced in pip 20.3.
Change-Id: Ifebaec916264bfd10eec13040295719fd47ae107
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
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
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
Convert all code to not require six library and instead
use python 3.x logic.
We don't need this in a Python 3-only world.
Depends-On: Ibfee28132e102c40d0eb5b8dc73228ec8fb9ce98
Depends-On: Ibe08ffa9072f1f0c1090f2b9e2ab9af59474d6b1
Depends-On: Ic4d00d081699015ccc2d529b872a17565c881c4e
Depends-On: I2995305abf7cb704f0fe4db9634c87ea2ed378b4
Depends-On: Id9192849a78d57ecfefe1dc20f931406884e055e
Depends-On: I0147dc00943e13531ffb5e2701a91c2d2838958b
Change-Id: I764e61b86cdcaa9e74b1281344599f2d3a13d68f
Co-Authored-By: zhoulinhui <df.some@foxmail.com>
Suppress of policy deprecation warnings. oslo.policy logs the
deprecated policy warnings while loading the
policy rules. Flag to suppress the warning was set after load_rule()
was called. We do not need to log warnings for unit test where
every test initializes the policy and logs a warning.
Also use yaml format of policy file in unit test to avoid
more warnings for json file.
Bump a few l-c for Py38 testing, squashing parts of
https://review.opendev.org/744343
Fix unit tests compatibility with Py38, squashing parts of
https://review.opendev.org/748874
Change-Id: Ia54d29975347392cbb93c07969d7e3b48eca5d23
Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
From last couple of months, the functional devstack job is broken.
Fixed the devstack job so that functional tests can run on multi-node
setup.
Note: Need to install SQLAlchemy-Utils explicitly as taskflow library
installs it using extra_requires which somehow is not working on the
devstack CI job setup.
Change-Id: I224b4a5615525862f73ced8ab9f5f396cb00ef0f
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 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
Masakari below test cases are failing due to webob 1.8.x:
..unit.api.openstack.test_wsgi.RequestTest.test_secondary
..unit.api.openstack.test_wsgi.RequestTest.test_asterisk
..unit.api.openstack.test_wsgi.RequestTest.test_from_request
Please see the logs:
http://logs.openstack.org/53/518653/1/check/openstack-tox-py27/76866e9/testr_results.html.gz
This patch is a copy of change:
I2034d30cc8d9354be80d39e05b8488cb99c32ecf which fixes similar
test cases in nova.
This patch also changes the `lower-constraints.txt` to make
the WebOb version same as other services.
Change-Id: Ic5234735267530f3b347126e1f0afa3e25f9e1fe
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: Iff00524bc3eb0fe1070aee7584885465cacd2393
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
oslo.context>=2.19.1 outputs 'project' key in context's to_dict
function.
The value of 'project' key is same as 'project_id' key.
So this patch modifies unit testcases according to the above changs.
And, this patch adds oslo.context to requirements.txt.
oslo.context had been installed related to oslo.versioned object
until now.
But, it is better to describe it explicitly because Masakari uses
the library.
Change-Id: Ibebed8a4e5bfd49f192b1cf876b7538f9c057f97
DbMigrationError is deprecated and will NOT be thrown in oslo.db
since oslo.db >=4.27.0, DBMigrationError will be thrown instead.
Consumers should catch DBMigrationError instead of DbMigrationError
Depends-On: Iab0566cf9f4552e91fa417e64472fa106e8bc86d
Depends-On: I0ebd69c3d778acb5bec9e136627e345e7fcf2bd3
Change-Id: I8e4968d2f2ed90edc22161db60712896f6e9f024
Some configuration options were accepting both IP addresses
and hostnames. Since there was no specific OSLO opt type to
support this, we were using ``StrOpt``. Now the support is
added for ``HostAddressOpt`` type and became available for
use with osloversion 3.22.
This patch changes the opt type of configuration options to use
this more relevant opt type - HostAddressOpt.
Change-Id: Id007b22bb0c43c8a0b4a4e3b9a4da6cc866f0563
oslo.messaging allow dispatcher to restrict endpoint methods since
5.11.0 in d3a8f280ebd6fd12865fd20c4d772774e39aefa2, set with
DefaultRPCAccessPolicy to fix FutureWarning like:
FutureWarning: The access_policy argument is changing its default
value to <class 'oslo_messaging.rpc.dispatcher.DefaultRPCAccessPolicy'>
in version '?', please update the code to explicitly set None as the
value: access_policy defaults to LegacyRPCAccessPolicy which exposes
private methods. Explicitly set access_policy to DefaultRPCAccessPolicy
or ExplicitRPCAccessPolicy.
Closes-Bug: 1662540
Change-Id: I36fdf6f568dc2a10891c9d89f8488038af6c2d00
Added base NotificationDriver and TaskFlowDriver which will implement
NotificationDriver for procesing the notification workflows such as
host-failure, instance-failure and process-failure.
Change-Id: I2d12681bd26b5b1fb2535732d9f3c08ec2409d7a
Add following libraries to requirements.txt because these are
necessary for masakari-api.
* keystoneauth1
* keystonemiddleware
Change-Id: Ib28fbcceabce12dea0d3eeeb2096354ccaa2bb8d
Closes-Bug: #1631732
This patch will add RPC framework to send notification from
masakari-api to masakari-engine service.
Change-Id: I3c514db1a652834a56efb187b754e336580ca7fc
This patch adds a schema layer for validation.
Schemas for failover segment and hosts will be added in their
respective patches.
Change-Id: I9440fb53d6594e5c984be3c94a3681a0e747da15
Added wsgi framework support to create masakari-api
service using oslo_service framework. Similar to core
openstack projects, config items will be kept at centralized
location.
Refer README.rst to cofigure and run masakari-api service.
Change-Id: Idb0120b8cf3b10642c51b286d82cd0944cad5ca3