Calling processutils.execute() other than subprocess to
fix bytes-like and str issue in python3.
Closes-bug: #2029392
Change-Id: I16436aa19da2cf53951c9ad27bca14033194651a
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I29fcb9afa016b1321b0b4c0118a8d7ffbc00b02e
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: I595b8c7cad7bb02486c8f0dd29fdc40789fc8e50
Because autobahn 20.7.1 depends on cryptography>=2.7, we
need to update the version of cryptography.
Change-Id: Ib89beed50f5d6e63fe6d75bdd24a4c879bd4834a
We don't need this in a Python 3-only world.
Remove six in follows:
1. zaqar/common/transport/wsgi/helpers.py
2. zaqar/common/urls.py
3. zaqar/common/utils.py
4. zaqar/notification/notifier.py
5. zaqar/notification/tasks/mailto.py
Change-Id: Iae6d4f415b215b9fdf675a0fcf00282fc98d58b7
As per victoria cycle testing runtime and community goal[1]
we need to migrate upstream CI/CD to Ubuntu Focal(20.04).
Fixing:
- bug#1885825
Fix user creation with GRANT in MySQL 8.0(Ubuntu Focal)
Ubuntu Focal (20.04) has mysql 8.0 and with mysql 8.0 there
is no implicit user creation with GRANT. We need to
create the user first before using GRANT command.
- bug#1886298
Bump the lower constraints for required deps which added python3.8 support
in their later version.
Co-Author: wanghao <sxmatch1986@gmail.com>
Story: #2007865
Task: #40229
Closes-Bug: #1885825
[1] https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-jobs-to-ubuntu-focal>
Change-Id: Ic15dfe480e4d34c3ba102b65153fab1af787bd67
Package msgpack has Removed the encoding option. Please refer to [1].
And the default encoding of python3 is 'utf-8', So there is no need to specify
the encoding as 'utf-8'.
[1] https://github.com/msgpack/msgpack-python/pull/380/files
Change-Id: Ibb92e983a79e5c1608f6a603816e1b88283e34c9
Closes-Bug: #1891008
Signed-off-by: ZijianGuo <guozijn@gmail.com>
The queue in Zaqar will support to encrypt
messages before storing them into storage backends,
also could support to decrypt messages when those
are claimed by consumer. This feature will enhance
the security of messaging service.
Implements: blueprint encrypted-messages-in-queue
Signed-off-by: wanghao <sxmatch1986@gmail.com>
Change-Id: Icecfb9a232cfeefc2f9603934696bb2dcd56bc9c
There are a few issues causing all gate runs to fail that are addressed
in this patch.
Update constraints to match global requirements:
There are a few local requirements that conflict with what is now in
upstream global-requirements. This updates sphinx to match the
constrained versions due to incompatibility with py2 and uncaps
jsonschema.
Update handling for falcon 2.0.0 behavior changes:
The 2.0.0 release of falcon changed the default values for two request
query parsing options that would cause failures due to unexpected
results. This sets those options to their previous defaults to maintain
compatibility across 2.0.0 and pre-2.0.0 versions of the package.
Lower constraint version raised to 1.1.0 where the options were
introduced.
There are additional integration test failures with Falcon 2.0.0 that
were due to changes in the subscription URL path.
Closes-bug: #1830903
Requirements and upper constraints not enforced in some tox targets:
The docs and api-ref tox targets were not setting the right dependencies
or the upper constraints to use for pip installs. Also updates the
constraints to the newer preferred static redirect URL maintained by the
release team.
Co-authored-by: wanghao <sxmatch1986@gmail.com>
Change-Id: I19c5363878c629a04e1be902c865ee7cea92dcd9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This adds basic framework for zaqar-status upgrade
check commands. For now it has only "check_placeholder"
check implemented.
Real checks can be added to this tool in the future.
Change-Id: I855b4b72284df308c3bb250fd3a3f0fc643b4abf
Story: 2003657
Task: 26165
The low-constrainsts is totally wrong, it contains
the upper ones. This patch copy the right ones from
openstack/requirements to fix the issue
Change-Id: Ic4f90ffc609d871a918091d93ee14896dc876be9
The use of plain SQLAlchemy create_engine in Zaqar bypasses
lots of oslo_db features that are associated with its
version of create_engine, some useful and some critical.
Among favorable behaviors that are added:
* The SQLite PRAGMA FOREIGN KEYS call is abstracted into the
sqlite_fk flag
* The engine is given a pessimistic "ping" event, which emits
a "SELECT 1" upon connection checkout which will then recycle
the connection if the backing database is no longer connected.
As we are using a connection pool, if the database has been
restarted, or in the case of MySQL a default timeout of eight
hours idle has passed, existing pooled connections will be stale.
Upcoming SQLAlchemy 1.2 includes this feature as a simple flag
but for now, oslo_db implements the event listener as directed
by SQLA docs
* The errors raised by the DBAPI, and then wrapped by SQLAlchemy,
are further sub-classified. In particular, Zaqar seems to use
a lot of IntegrityError catches to detect duplicate entry and
foreign key constraint conditions. oslo_db parses these out on
a per-database-basis into individual DBDuplicateEntry,
DBReferenceError, and other error classes, allowing Zaqar to
respond specifically to the sub-class of IntegrityError or
allow it to propagate if the condition is unhandled.
* checks for MySQL SQL_MODE and best practice driver (pymysql)
will emit warnings if these conditions are not met.
* Gets Zaqar ready for further oslo.db integration and guides
new features into oslo_db, including a potential "mysql timezone"
setting
Change-Id: I16c3ed89e006e132bbd0295be1dfd0b561b2037c
Resolves-bug: https://bugs.launchpad.net/tripleo/+bug/1691951
Guru is a mechanism whereby developers
and system administrators can generate
a report about the state of a running
Zaqar executable.
This report is called a *Guru Meditation Report*
This mechanism will help developer or operator
to fix issues in (production) deployments without
stopping Zaqar service.
Implements: blueprint introduce-guru-to-zaqar
Change-Id: I72885be396be7eb0a9dd8fd564d706a8351b02c6
Takashi Kajinami
OpenStack Release Bot