As per the current release tested runtime, we test
till python 3.11 so updating the same in python
classifier in setup.cfg
Change-Id: I3dc98d4e5e0b4b210d1bbeb4345fe97cbafd17be
Docker has removed external cluster store in latest version.
Therefore, we switch to "local" mode to work around.
Closes-Bug: #2007142
Change-Id: I31d140a75dae2ddd23551e648d0492327a8d8c8e
With latest sqlalchemy there is no alter attribute for the Column object
Thus, zun-db-manage upgrade fails with AttributeError. Instead of trying
to use SQLAlchemy for altering Column we should use alembic instead
for the migration
This also fix py3.11 job by replacing libmysqlclient-dev with
libmariadb-dev-compat which is available for both ubuntu and debian.
Closes-Bug: #2043209
Change-Id: Iaba736d391ad5820de5f481d2c5bac1714dc0809
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: Id19a4cca43e12eef5937706a18c129c6c2cdf994
There is a difference between "openstack appcontainer stats <id>"
and "docker stats <id>" in memory value.
Cache Usage should be removed from the memory usage while calculating
which is present in docker SDK.
This patch contains the Cgroup V1 and V2 handling for Memory stats
Closes-Bug: #1989792
Change-Id: I4f1d9b738ee5de176b6e0ef69593363f2977f07a
The Bulk stats are coming 0 in case we are fetching from zun
However, docker sdk is giving the stats properly in a different
field
Closes-Bug: #2013046
Change-Id: Ia55262f33222f5ca2f041be0b34b96840a47b727
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: I566b07e5f03b5cc305225ec451cd548f877e450e
tox.ini started failing with Tox4 which had some
incompatible changes. One is passenv where we need
to pass each value in newline otherwise, it fails with
error:
failed with pass_env values cannot contain whitespace,
use comma to have multiple values in a single line,
invalid values found.....
Fixing tox.ini for tox4 changes.
Change-Id: I86640fc7ae5565838c701974252a5775d1582eb4
The new git owner check [1] broke zun installation process.
We add an exception to skip the check.
[1] 8959555cee
Change-Id: I5dd1e4057722ddece259c70985b77a3dd1dfd48b
oslo.db 12.1.0 has changed the default value for the 'autocommit'
parameter of 'LegacyEngineFacade' from 'True' to 'False'. This is a
necessary step to ensure compatibility with SQLAlchemy 2.0. However, we
are currently relying on the autocommit behavior and need changes to
explicitly manage sessions. Until that happens, we need to override the
default.
Change-Id: I04b336a42b5cbb458badde3bb04d35363d7834d8
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: I3cf69979f3b29fc199ede35cf6d80b48024528d0
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: I6e4fe6fc8ba53c97d422e5eac8bc46f711dc641a
tools/gen-criapi was used with the latest protobuf dependencies
to generate compatible files. This makes Zun Compute work again
with the current implementation of protobuf.
In addition, fix two issues that causes gate failure.
Depends-On: https://review.opendev.org/c/openstack/kuryr-libnetwork/+/851549
Closes-Bug: #1982924
Change-Id: Id1032709f6e3b11b718b3df6a6ac3531a9c99824
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: Ia2815986812845771527dc8d180968312c6db34b
Some problems were found in the development of enterprise projects:
1.After repairing the container operation, the return parameter does not include the time parameter. It is necessary to judge whether to restart and obtain the running time in the business development. Compared with nova, the return info of the VM also contains the above information.
2.When creating a container, if a custom security group created with neutron is also associated, the expose_ports parameter is also given, which will cause the custom security group parameters to be overwritten, which is very important for the container to increase the exposure range of ports. Important, but it is currently a failure.
Change-Id: I1f5c2ddc835d91c14ae8936c0fb7f79d418ba804
pyroute2 0.6.4 seems to break us due to their packages split. This
commit attempts to fix it by making sure we import modules correctly.
Change-Id: Iaf3571f1b33f99fa4f249aff46b1d89ac2168c8e
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: I3dd79d364b91302234be31333bdfdf5c8c6a00aa
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Icf30f766231f4d5c72488a56131b04093c8ff03e
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: I50d267a7d8cff248ad71dc3fcc6f74374a95db2c
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: I1248c7356e9a22f0281f12afa8faf5f6aa0f5c8b
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I3f72849c88bc122fd0d32d6e564ee4eb862af94a
Tox trying to install latest versions for building releasenotes,
api-ref which may not be supported by stable and lower branches,
so should be restricted by respective version's upper-constraints.txt
Depends-On: Ia2fe3cab71b2efb89d6a4370109ec1abf2d1086f
Change-Id: I13baec09f477fafaabc06f9459549ddb03e2657d