Change tox.ini so that all jobs are python3, and add explicit
unit/functional testenvs for the two ussuri python runtimes
(3.6 and 3.7).
Remove py2 jobs from .zuul.yaml and redefine the periodic "tips"
jobs so that they are testing with the ussuri python runtimes.
Added nodeset: ubuntu-bionic to the abstract base jobs so that
py3.7 is available.
Co-authored-by: Ghanshyam Mann <gmann@ghanshyammann.com>
Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
Closes-bug: #1853693
Change-Id: I15467c34fc8466fa1724c5401dc879ae77c1922d
This job is still running python 2.7 and failing continuously. As we
are dropping py2 support in Ussuri cycle, lets drop this job now.
There is same job called "grenade-py3" which runs on python 3 already
and this is still used in project's CI.
Change-Id: I3e62c9ebc3e8673603b26acb9bacc543670bdf99
As eventlet ssl termination is broken with python 3 and
we won't be supporting python 2.7 anymore we will just
remove ssl termination to glance-api and expect the
termination being handled by something else, like HAProxy.
This patch also removes the broken ssl test job as the
non-existing feature is not broken anymore.
Change-Id: Iaf16dfcfdb3a2c93312dcad1ea1229e6b3c8caaa
Glance isn't explicitly installing requirements, so add requirements
as tox deps in such a way that they'll be properly constrained by the
current openstack upper-constraints.
This change also bumps the version of psycopg to that of the current
upper-constraints in test-requirements and lower-constraints. (The
version in our current lower-constraints is subject to the "could not
determine PostgreSQL version from '10.x'" error, which causes the
lower-constraints job to fail.)
Change-Id: I1bb5759e6b1e3f8545ab417617072a61323b59a7
Closes-bug: #1852356
Now that we are using gitea the contents of our README.rst are
more prominently displayed. Starting it with a "Team and repository
tags" title is a bit confusing. This change makes it start with the
name of the project instead.
Change-Id: I538c8db4b45eb3f65dfe48f0c3ce006a8dfee4df
The tasks unit tests that test the RequestDeserializer
are using the real policy engine. They should be using
a mock because we're testing the deserialization, not the
policies.
Closes-bug: #1852354
Change-Id: I35bdacd154b2c8d18ce268a5e6e8aba710e41108
opensuse-150 nodeset is referring to openSUSE 15.0, which is still in
maintenance but openSUSE 15.1 has been released already. "opensuse-15"
is going to refer to the "latest openSUSE 15.x" build released and
working for OpenStack going forward, so add this nodeset and use
it by default going forward.
The new job tempest-full-py3-opensuse15 use the opensuse-15 nodeset,
change tempest-full-py3-opensuse150 to tempest-full-py3-opensuse15.
Change-Id: Ia76b107a137a39716253631e5a8d294f7ee9614e
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: I6ed9645bebb9a63a1e70d8f6630c7d53fba4e35e
Sem-Ver: feature
This change removes experimental status from Api versions
>2.7 setting 2.8 (multi-store support) to SUPPORTED and
2.9 (caching) to CURRENT.
NOTE: 2.8 will show up in list only if the glance-api service
is configured with multi-store. The API versions list can be
used to determine if the multi-store functionality is availabe
in the endpoint.
Change-Id: I37350fc46191074d42edc73c2451eae73261957d
In Rocky multiple backend support is added as experimental feature. In
order to take advantage of this feature it is decided to deprecate
work_dir and node_staging_uri configuration options
and reserve two filesystem stores 'os_glance_tasks_store' and
'os_glance_staging_store', which can be used to get rid of initializing
store via internal functions.
These internal stores are considered "reserved stores" by Glance.
For the time being, these are hard-coded as filesystem stores. The
store prefix 'os_glance_' is reserved for internal Glance use and
the glance-api service will refuse to start if a store with this
prefix is included in the enabled_backends config option in
glance-api.conf.
NOTE: Because there are no sensible default values for the location
of the datadir for each of these stores, the operator must define
'os_glance_tasks_store' and 'os_glance_staging_store' in
glance-api.conf configuration file as shown below.
[os_glance_tasks_store]
filesystem_store_datadir = /var/lib/glance/tasks_work_dir/
[os_glance_staging_store]
filesystem_store_datadir = /var/lib/glance/staging/
Each filesystem store must have a unique datadir.
Depends-On: https://review.openstack.org/#/c/639765/
Implements: blueprint rethinking-filesystem-access
Change-Id: I86ec513c5fc653dbb97b79d953d8430f014e684f
This patch also removes casual suggestion to turn on show multiple
locations. This feature has been idetified as vulnerability and
we should not advise turning it on without explaining the specific
use cases where it might be necessary.
Co-authored-by: Erno Kuvaja <jokke@usr.fi>
Co-authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com>
Change-Id: I65952f70f0216d227ca14d1098d264208913e4e5
Commit a2cb3cd286637c86fdd1d92d9396f3e0c6a08ca2 was skipping some
multiple stores related functional tests to allow the release of
glance_store V1.0.
Now store library is released so it safe to enabled these tests now.
Change-Id: I5189c97320d97d5eb4c330580a9bec14815bff03
Oslo Reports enables OpenStack projects to dump Guru Meditation
Reports with useful debugging information on live services
to files or stderr.
Change-Id: I33b6e52870b583c70aa8141ab55d8738beaf5c59
Replace seconds with milliseconds
in the description of hw_rng:rate_period[1].
[1]https://libvirt.org/formatdomain.html#elementsRng
Change-Id: I53848359704d68dd84c5be8106f4e259937b8092
Related-Bug:#1843542
This patch introduced double registering of the same
config option groups which fails glance-api start
if reserved stores are actually defined.
The code utilizing these config options has not been
merged which prevented testing to catch this.
Closes-Bug: #1844108
This reverts commit 4265e61bc84ce9bd085a95d8734647f4875af740.
Change-Id: Iaf338d29673e68a15d37fdda81add552e4175634
this is not needed as 4265e61bc84ce9bd085a95d8734647f4875af740
is being reverted also.
This reverts commit b639ed080d5b74fcc3081a09bd64dd4703dea5a4.
Change-Id: I3c1b86e73a25935f2a2ffd43731e2db36fbffa97
When running "tox -e pep8", "DeprecationWarning: invalid escape sequence"
are shown. This is because a normal string contains escape sequences.
Escape sequences need to be placed in raw strings.
TrivialFix
Change-Id: I34f63d90f53b721e9afdeb99ac53ef0c24857b17
This change contains minor version bump to Images API to
indicate latest changes to the API.
Also has config file sync for for M3 release.
These two are combined for saving some gating time due to
busy infra at Train milestone 3 deadline.
Change-Id: I13133c32734751d43cc3afed9b68d015cebd5b6b
The deprecation messages of node_staging_uri and work_dir
were claiming that local directory is not needed after moving
to multistore. This is not exactly true and gave false
expectations of the current capabilities.
For now only the way to configure those needed folder and
how they are internally accessed is changing.
This change corrects the deprecation message to reflect
current state.
Change-Id: I39c170903c64181841a22c7b9bdaa3b5a1346caa
Closes-Bug: #1843891
For ARMv7 and AArch64, Nova uses the 'virt' machine type as the default.
Update the docs to reflect that.
Refer to this commit in Nova:
https://opendev.org/openstack/nova/commit/e155baefb0
(libvirt: Use 'virt' as the default machine type for ARMv7,
2018-09-14)
Change-Id: I13793dded976fdf872ca0ea779a7f6cbee98118f
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
The AMD SEV support recently introduced to nova[0] depends on certain
metadata properties for flavors and images which were either missing
or only partially covered by existing glance metadata, so fill the
missing gaps:
- Add the hw:mem_encryption flavor extra spec and corresponding
hw_mem_encryption image property.
- hw_firmware_type has been supported by nova for quite a while,
so register it as an official metadata property.
- Add hw_cdrom_bus which was missing as per
https://bugs.launchpad.net/glance/+bug/1808868. This shares
values with hw_disk_bus, so document that too.
[0] https://docs.openstack.org/nova/latest/admin/configuration/hypervisor-kvm.html#amd-sev-secure-encrypted-virtualization
Closes-Bug: 1808868
Change-Id: I8116565ad0326d0125b320d840d787edcb086aa9
