* Update devstack from branch 'master'
to e2aeab1bc1deae8d147508ae0d1f752588d03fd3
- Merge "Fix neutron empty string check"
- Fix neutron empty string check
The variable should be in quotes for the check to work
Testing the behavior in bash:
current behavior:
$ config_file=""
$ if [ -n ${config_file} ]; then echo a; fi
a
$ config_file="abc"
$ if [ -n ${config_file} ]; then echo a; fi
a
behavior with quotes:
$ config_file=""
$ if [ -n "$config_file" ]; then echo a; fi
$ config_file="abc"
$ if [ -n "$config_file" ]; then echo a; fi
a
Change-Id: Iba956d9d4f43b925848174a632aabe58999be74b
* Update devstack from branch 'master'
to 1abf3598fa6e6587354d973c59306dbe6a130bd7
- Merge "lib/apache: Rename variable"
- lib/apache: Rename variable
This is a little more meaningful, IMO.
Change-Id: Ib9d3fdc54b1cdbd822c2a4eca0a3310ca3f6324c
Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
* Update devstack from branch 'master'
to fca44cc375657da3d1a20f16c5c04574c6234376
- Merge "Do not configure system-scope admin for keystone"
- Do not configure system-scope admin for keystone
This patch removes a couple of tempest.conf settings that are being
overwrriten when Keystone is set to enforce scope.
These settings are already being set by the keystone devstack plugin [1]
and do not need to be overwritten here.
Keystone is changing the default admin credentials to be project-admin
instead of system-admin to address some failing tests in services that
require project-scoped admin for their admin APIs. [2] These overrides
are preventing that change from taking effect.
[1] https://opendev.org/openstack/keystone/src/branch/stable/2024.1/devstack/lib/scope.sh#L24-L25
[2] https://review.opendev.org/c/openstack/keystone/+/913999
Change-Id: I48edbcbaa993f2d1f35160c415986d21a15a4999
* Update devstack from branch 'master'
to 99a96288eb14e66723d85e6ca24ff51babac7ec8
- Update DEVSTACK_SERIES to 2024.2
stable/2024.1 branch has been created now and
current master is for 2024.2.
Change-Id: I4af9e87318ef9cbfede7df7c23872a1a7e38c820
* Update devstack from branch 'master'
to f4f09416ca8de09820b52599c7bcd2911b407466
- Merge "Drop unused environments for TripleO and heat agents"
- Drop unused environments for TripleO and heat agents
TripleO was already retired. These environments are not actually used
by heat jobs.
Change-Id: I63b7413a1575a620f9d2cbd56e93be78816639e0
* Update devstack from branch 'master'
to 5f5255bc011ef885f254c659009662870499de5a
- Remove Glance uWSGI config in clean.sh
Updated clean.sh to remove Glance's Apache uWSGI config files in
APACHE_CONF_DIR, including /etc/apache2/sites-enabled/ on Ubuntu.
Test Plan:
- Run clean.sh.
- Confirm Glance uWSGI configs are removed from APACHE_CONF_DIR.
Closes-Bug: #2057999
Change-Id: I44475b8e084c4b20d7b7cb7f28574f797dbda7a2
* Update devstack from branch 'master'
to 5e837d1f0d9078c58bc634474a1adf311bc2b491
- Updated from generate-devstack-plugins-list
Change-Id: Ic99b518ddf1045893991accaa089f44d0d4f4b0d
* Update devstack from branch 'master'
to c7fdfbaed26c45e9f2a156b1928312dd828519ac
- Merge "Ignore 500 status code in generate plugin script"
- Ignore 500 status code in generate plugin script
Due to various reasons, this script may encounter the
500 status code from some repo (x/fuel-plugin-onos in current case[1])
If that happen then it return failure status code to the
propose-updates job and fail that job
- https://zuul.openstack.org/builds?job_name=propose-updates&project=openstack%2Fdevstack&skip=0
It is better not to raise the 500 error in this script and just ignore those
repo to process further to detect the plugin.
[1] https://zuul.openstack.org/build/dba0aa41d145472397916dfcd13948de/log/job-output.txt#2442
Change-Id: Ibca0a2aac404161340e8fc00170018eecf5c8326
* Update devstack from branch 'master'
to ee178dcdb5e8b82d718ecc1e36c2935d0c697f6c
- Merge "Drop the devstack-single-node-centos-7 nodeset"
- Drop the devstack-single-node-centos-7 nodeset
OpenDev is preparing to remove centos-7 nodes on March 15[*]. This
change drops one nodeset definition which is the last remaining
reference on DevStack's master branch.
[*] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/A2YIY5L7MVYSQMTVZU3L3OM7GLVVZPLK/
Change-Id: Icd487e1012263a9b0bc13b529d31ff2025108adf
* Update devstack from branch 'master'
to 94562b40032afdf0726c5141c85d6e6de2f6313d
- Merge "Make `centralized_db` driver as default cache driver"
- Make `centralized_db` driver as default cache driver
Making newly introduced `centralized_db` driver as default cache
driver for glance so that it can be tested in available CI jobs.
New cache driver `centralized_db` needs `worker_self_reference_url`
in glance-api.conf file otherwise glance api service will fail to
start.
Related blueprint centralized-cache-db
Depends-On: https://review.opendev.org/c/openstack/glance/+/899871
Change-Id: I75267988b1c80ac9daa5843ce8462bbac49ffe27
* Update devstack from branch 'master'
to 57c685496f0ef8da0d6ebc50845f752caf29948a
- Merge "Drop nodesets with ubuntu-xenial"
- Drop nodesets with ubuntu-xenial
The ubuntu-xenial labels are going to disappear from opendev as that
image is EOL and will we deleted. Clean up our zuul config.
Update some example reference as well.
Change-Id: Id04110f7c871caa1739ff2b62e9796be4fb9aa00
* Update devstack from branch 'master'
to 8bc99f3ef1bb48003a171997838a585311fee4d8
- Merge "nova: unset cpu_model on aarch64"
- nova: unset cpu_model on aarch64
Without this, running DevStack on an `aarch64` environment will end
up in cpu_model set to "Nehalem" and cpu_mode set to "host-passthrough"
which does not work.
This patch drops that value under aarch64 environments.
Change-Id: I30be5a388dda5ccf08718670dbb14a28a4a8a8eb
* Update devstack from branch 'master'
to ed41f85d722988c64d2e9a904fbbe05ed11d4b65
- Merge "Add cinder-manage to /usr/local/bin/"
- Add cinder-manage to /usr/local/bin/
This is useful in a dev environment.
Change-Id: I247eb4aea23a906d0e667ec6c5ac79f932bdca24
* Update devstack from branch 'master'
to 4ddd456dd3e71bcdf9a02a12dd5914b82ec48e91
- Add support for the pyproject.toml file in setup with constraints
In the _setup_package_with_constraints_edit name of the package was
always discovered from the setup.cfg file. But as some projects
implements PEP-621 (see [1] for the SQLAlchemy for example) it is not
enough now.
This patch adds parsing pyproject.toml file also if name is not found in
the setup.cfg file.
[1] a8dbf8763a
Closes-Bug: #2052509
Change-Id: Iee9262079d09a8bd22cd05a8f17950a41a0d1f9d
* Update devstack from branch 'master'
to 1ba76adccbf5d18a5dc6266d3808dcd97e0b9c68
- Merge "Increase timeout for reimage operation"
- Increase timeout for reimage operation
Looking at the recent failures in the tempest-integrated-compute
job, the reimage operation seems to be taking longer than our
expected time of 60 seconds (which was increased because of a similar
failure in the past, default is 20 seconds).
The main culprit for this failure is the image conversion from qcow2
to raw which is taking ~159 seconds.
Dec 05 13:29:59.709129 np0035951188 cinder-volume[77000]: DEBUG oslo_concurrency.processutils [req-5113eccb-05ba-486a-8130-a58898c8ad35 req-0edf972a-109a-465f-a771-ceb87ecbda3e tempest-ServerActionsV293TestJSON-1780705112 None] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf qemu-img convert -O raw -t none -f qcow2 /opt/stack/data/cinder/conversion/image_download_dbe01f18-1c90-4536-a09a-b49f0811c7a0_copod3cm /dev/mapper/stack--volumes--lvmdriver--1-volume--073a98e8--3c89--4734--9ae5--59af25f8914a" returned: 0 in 159.272s {{(pid=77000) execute /opt/stack/data/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:422}}
The recent run took ~165 seconds on the cinder side but it failed
early since the nova operation timed out in 60 seconds hence
deleting the volume.
To be on the safer side, 180 seconds seems to be a sane time for
the operation to complete which this patch configures.
Closes-Bug: 2046252
Change-Id: I8a9628216038f6d363cab5dd8177274c9cfc17c2
* Update devstack from branch 'master'
to 15a6f3e41044bfb990da023a1c0a24c0a072cd5f
- Merge "Uncap bashate"
- Uncap bashate
The bashate tool has been very stable for a while and we rarely expect
changes which may break existing scripts.
This removes the current capping to avoid updating the upper limit when
when a new release is created in bashate.
Change-Id: Iae94811aebf58b491d6b2b2773db88ac50fdd737
* Update devstack from branch 'master'
to 5c1736b78256f5da86a91c4489f43f8ba1bce224
- fix zswap enable flag
zswap should only be enabled if ENABLE_ZSWAP is true.
The if condition was checking ENABLE_KSMTUNED.
That is now fixed.
Change-Id: I76ba139de69fb1710bcb96cc9f638260463e2032
* Update devstack from branch 'master'
to 031732998ab86206ff2762af8e7f1d0596021036
- Merge "add support for zswap and ksmtuned"
- add support for zswap and ksmtuned
This change add a new lib/host-mem file and moves the existing
ksm support to a new configure_ksm function.
Additional support for ksmtuned is added with a new flag
"ENABLE_KSMTUNED" which defaults to true.
This change also adds support for zswap. zswap is disabled
by default. When enabled on ubuntu lz4 will
be used as the default compressor and z3fold as the zpool.
On non debian distros the compressor and zpool are not set.
The default values should result in very low overhead although
the zstd compressor may provide better overall performance in ci
or with slow io due to the higher compression ratio.
Additionally memory and network sysctl tunings are optionally applied
to defer writes, prefer swapping and optimise tcp connection
startup and keepalive. The sysctl tunings are disabled by default
The base devstack job has been modifed to enable zram and sysctl
tuning.
Both ksm and zswap are wrapped by a tune_host function
which is now called very early in devstack to ensure
they are configured before any memory/network intensive
operations are executed.
The ci jobs do not enable this functionality by default.
To use this functionaltiy define
ENABLE_SYSCTL_MEM_TUNING: true
ENABLE_SYSCTL_NET_TUNING: true
ENABLE_ZSWAP: true
in the devstack_localrc section of the job vars.
Change-Id: Ia5202d5a9903492a4c18b50ea8d12bd91cc9f135
* Update devstack from branch 'master'
to 6091df25a39c9b17883d86ccb091bf2b9c39aa15
- [OVN] Add support for the Neutron OVN agent service
The Neutron OVN agent is a service that could run in any node. The
functionality will depend on the extensions configured. This new
agent is meant to be the replacement for the Neutron OVN metadata
agent once the "metadata" extension is implemented in this service
[1].
[1]https://review.opendev.org/c/openstack/neutron/+/898238
Related-Bug: #2017871
Change-Id: I8f82f0047e89aac122a67f59db84f03e1a6bf519
* Update devstack from branch 'master'
to a2da805f8107703e5f6738399ce5f5e358190fdc
- Fixup of 'Fix spelling of `ADITIONAL_VENV_PACKAGES`'
Introduced a dangling } in the environment variable.
This removes it.
Change-Id: If9413dc1751399e5b9c9a0094772394252e5a81c
* Update devstack from branch 'master'
to a88b17177dd4100c5b42b105e7020627410638b2
- Merge "Fix spelling of `ADITIONAL_VENV_PACKAGES`"
- Fix spelling of `ADITIONAL_VENV_PACKAGES`
This preserved `ADITIONAL_VENV_PACKAGES` as an input for backwards
compatiblity, but takes `ADDITIONAL_VENV_PACKAGES` with priority.
Fixes spelling in comment.
Related-Bug: #2046936
Change-Id: I84151d8f71b12da134e8fb9dbf3ae30f2a171fe2
* Update devstack from branch 'master'
to 7699ce2d5c465f86f2aace7af6b150dceb0e6e1c
- Updated from generate-devstack-plugins-list
Change-Id: Ie5cbd87269a10d6abdf1d24f7e6224d9aac3bf5d
* Update devstack from branch 'master'
to 6b0f055b4ed407f8a190f768d0e654235ac015dd
- Make multiple attempts to download image
Downloading an image can fail due to network issues, so let's
retry 5 times before giving up. We have seen issues in CI due
to network issues as described below and in the Related-Bug:-
Often times fetching Fedora image in FIPS jobs fails due to
"GnuTLS: One of the involved algorithms has insufficient security level."
This occurs when request to pull image is redirected to a mirror that's
incompatible with FIPS enabled system.
Making multiple attempts to download images could provide better chance of
pulling images from different mirrors and avoid failure of the job.
This will also save a few rechecks.
Related-Bug: #2045725
Change-Id: I7163aea4d121cb27620e4f2a083a543abfc286bf
* Update devstack from branch 'master'
to 2211c778db0e18702c7177f7750571cba3697509
- Allow devstack to set cache driver for glance
Added new devstack variable `GLANCE_CACHE_DRIVER` default
to `sqlite` to set the cache driver for glance service.
Related blueprint centralized-cache-db
Change-Id: I76d064590356e2d65bfc6a3f57d1bdaeeb83a74a
* Update devstack from branch 'master'
to bb0c273697bf54dd569ad38e459cd161b62f96cb
- Option for SQLAlchemy and alembic git source
Change-Id: If7ff0075834a1e9cee01713676166e56b797debd
Closes-Bug: #2042941
* Update devstack from branch 'master'
to 9a55a925c4bd5aa5ab2d2bea00359a6d9f3e9836
- Merge "Revert "Enable keystone token caching by OSC""
- Revert "Enable keystone token caching by OSC"
This reverts commit 67630d4c52aef5ddcb15cff4f3b6594d447e8992.
Reason for revert: Seeing random failures across jobs as sometimes
'keyring_pass.cfg' gets duplicated keys and that makes executions
of any openstackclient command to fail until the file is removed.
This should be handled before re enabling the token caching again.
Change-Id: I3d2fe53a2e7552ac6304c30aa2fe5be33d77df53
Related-Bug: #2042943
* Update devstack from branch 'master'
to e7c12616e27ad2987c2dead1e1a413aaa2c632ee
- Add periodic-weekly pipeline with platform jobs
Originally we only had the openeuler jobs there, but the other platforms
could also do with some regular testing.
Change-Id: I93526a4c592d85acd4debf72eb59e306ab8e6382
* Update devstack from branch 'master'
to 57d3b21dd9518dae909754b085b833a5f4e06441
- Merge "ignore dbcounter sub dirs"
- ignore dbcounter sub dirs
currently id you run devstack with the dbcounter service enabled
the created subdirs show up in git status
this change justs add them to .gitgnore
Change-Id: Iee48eb4e12ac22734c8a2c1dcbe0b92a0a387eaa
* Update devstack from branch 'master'
to 0f402b8327cc3e501df93c735c1b049361ed3dbb
- Fix openEuler support
openEuler 22.03 LTS support was removed from devstack in last
few months due to its libvirt version is too old and the CI job
always fail.
This Patch add a yum repository for libvirt7.2.0, and add the
related CI job to make sure its works well.
Change-Id: Ic507f165cfa117451283360854c4776a968bbb10
* Update devstack from branch 'master'
to 3ffcc89d5dda1290c0a3ad6462dd41edb1dc35b7
- Merge "Enable keystone token caching by OSC"
- Enable keystone token caching by OSC
SDK uses python keyring library to enable token caching. Normally this
is requiring a proper desktop (interactive) session, but there are some
backend plugins working in non-interactive mode. Store cache in an
unencrypted file on FS (this is not worse than storing passwords in
plaintext).
Change-Id: I42d698f15db5918443073fff8f27b926126d1d0f
* Update devstack from branch 'master'
to bacb8400942b2ed6b724bdd3d28797896e1054c6
- Enable NEUTRON_ENFORCE_SCOPE to True by default
Neutron bobcat release has enabled the RBAC new defaults
by default. With the latest release of Neutron have new
defaults enable, we should configure the same by default in
devstack. This change make NEUTRON_ENFORCE_SCOPE flag to
True by default so that every job will run with Neutron
new defaults.
As old defaults are still supported (in deprecated way),
we will keep this flag so that we can have one job disable
it and test the old defaults.
Change-Id: I3361d33885b2e3af7cad0141f9b799b2723ee8a1
* Update devstack from branch 'master'
to cace4044316befbbef9bcb7af2003f3045350830
- Fix performance stats gathering for global VENV
Change-Id: I113c571ffddb241b29b1394e181ed0145b3c1e04
* Update devstack from branch 'master'
to 5613db3caa9193dcf84edabe04400341644ecab0
- Merge "Add support volume backup_driver config option"
- Add support volume backup_driver config option
The depends-on patch adds a new backup_driver option to tempest.
The goal of this change is to be able to do a proper cleanup of
containers when swift is used as a backup driver.
Thich change makes sure that the new option is properly set to
"swift" when Swift is used as the driver.
Depends-On: https://review.opendev.org/c/openstack/tempest/+/896011/13
Change-Id: I76e7fd712ee352051f8aa2f2912a29abad9ad017
* Update devstack from branch 'master'
to 99919cbbd833743f8286b3bb4a4fc923e4050e85
- Merge "Horizon: Install pymemcached"
- Horizon: Install pymemcached
... so that we can use PyMemcacheCache backend. The MemcachedCache
backend, which has been used previously, has been removed in recent
Django, and we are switching the default backend in [1].
[1] https://review.opendev.org/c/openstack/horizon/+/891828
Change-Id: Ie1da8970628e34c41721198cdada8c7bb3b26ec0
* Update devstack from branch 'master'
to 4975fad23efeb97e5b8fd799c93ad9367face1ba
- Merge "Allow forcing nova compute_id"
- Allow forcing nova compute_id
Developers that need to stack and re-stack non-AIO compute-only
environments will want to be able to keep the compute node uuid the
same across runs. This mimics the behavior of a deployment tool that
pre-creates the uuids, so it matches pretty well. Default to the
current behavior of create-on-start, but allow forcing it ahead of
time to something specific.
Change-Id: Icab0b783e2233cad9a93c04758a5bccac0832203
* Update devstack from branch 'master'
to eb9b08a8833884b7c7c5b55813d7621715fe7adf
- Updated from generate-devstack-plugins-list
Change-Id: Ieecc17159ac36b65124598c36fc92b77c2a75399
* Update devstack from branch 'master'
to ca4d5132e63752878620c4e4f374d98d433b3f52
- zuul: Drop neutron-linuxbridge-tempest job
Neutron has deprecated linuxbridge support and is only doing reduced
testing for the neutron-linuxbridge-tempest job, so we need no longer
run it in devstack, even less gate on it.
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: Ie1a8f978efe7fc9b037cf6a6b70b67d539d76fd6
* Update devstack from branch 'master'
to 68ca13311da92ba56efe85725339c248aead0b9a
- Merge "Update DEVSTACK_SERIES to 2024.1"
- Update DEVSTACK_SERIES to 2024.1
stable/2023.2 branch has been created now and
current master is for 2024.1
Change-Id: I67eee1ba721a1ad99b3503312acc2f94a52c5552
* Update devstack from branch 'master'
to 9e41895dea37cbf193bf4cf08c66215d33b83174
- Merge "CI: Make bookworm platform job voting"
- CI: Make bookworm platform job voting
It has been very stable for some time and it is going to be a major
platform for the next cycle.
Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: Id2df9514b41eda0798179157282a8486b1e9ae23
* Update devstack from branch 'master'
to f871476c222b2760542407bb75a45a571c568cef
- Merge "Use OS_CLOUD in sample local.sh"
- Use OS_CLOUD in sample local.sh
local.sh, if present, will be executed at the end of stack.sh. The
sample file here is meant to be copied to devstack root if desired.
Unfortunately, due to Change I86ffa9cd52454f1c1c72d29b3a0e0caa3e44b829
changing to use OS_CLOUD in stack.sh, sourcing openrc here will cause
both OS_CLOUD and traditional OS_* env vars to be set, which causes a
conflict.
Change-Id: Id80b46acab7d600ad7394ab5bc1984304825a672
* Update devstack from branch 'master'
to 25cd7eb67286ba39060d05b3f3f9e785d125195a
- Fix g-api-r for non-global venv
This makes the glance-api-remote setup honor the GLOBAL_VENV flag,
and not pass the --venv stuff to uwsgi if it is disabled. This should
fix the glance-multistore-cinder-import-fips job.
Change-Id: I2005da5ced027d273e1f25f47b644fecafffc6c1
* Update devstack from branch 'master'
to d3953db76641e825565390acc6f68501777c0f53
- Updated from generate-devstack-plugins-list
Change-Id: I18a47f5d604bbb83173151fb0b129deee2fcbe62
* Update devstack from branch 'master'
to 129d0964a87ad5757ba21587e1aa7daac2300447
- Merge "Remove openeuler job from periodic and check queue"
- Remove openeuler job from periodic and check queue
The openeuler job running version 22.03 fails due to old libvirt.
Nova requires version 7.0.0 or greater.
Related-Bug: #2035224
Change-Id: I4ad6151c3d8555de059c9228253d287aecf9f953
* Update devstack from branch 'master'
to 0c9dbbbe1150abce7e5cf9929f1686a762d29bbc
- Merge "Allow others to override NOVA_SERVICE_REPORT_INTERVAL"
- Allow others to override NOVA_SERVICE_REPORT_INTERVAL
While the patch where this was first introduced and set to 120 [1] is
sensible for the vast majority of jobs, it's conceivable that some
jobs might want a different value.
Specifically, the whitebox-tempest-plugin changes configurations and
restarts Nova services, and to do so it waits for the service status
to update in the API before continuing with the tests. With the report
interval set to 120 and the down time threshold set to 720, the
service would continue showing 'up' in the API long after it was
actually down, causing the wait to time out.
Whitebox is a low-traffic project with only a couple of devstack jobs
that run tempest tests sequentially (concurrency=1). Its CI is also
pretty stable. It seems legitimate for it to keep the old default
values of report_interval and service_down_time.
This patch keeps the 120 default for NOVA_SERVICE_REPORT_INTERVAL, but
makes it configurable by individual jobs. Since the original patch
also introduced CINDER_SERVICE_REPORT_INTERVAL as a constant, make
that configurable as well.
[1] https://review.opendev.org/c/openstack/devstack/+/890439
Needed-by: https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/891612
Change-Id: I64fa2059537ea072a38fb4900d3c7d2d8f0ce429
* Update devstack from branch 'master'
to 428cb8a0a942164b2b13d1c08e3b746e306feb00
- Merge "[nova][ironic] Support configuring 1 shard on n-cpu"
- [nova][ironic] Support configuring 1 shard on n-cpu
Allows for testing of basic sharding configuration.
Change-Id: Idfb2bd1822898d95af8643d69d97d9a76b4d64cc
Needed-By: https://review.opendev.org/c/openstack/ironic/+/894460
* Update devstack from branch 'master'
to af8750c82a679689c8f2e38dacaefb7561ca5af0
- Merge "Remove wget + rpm workaround to manage repos install in CentOS"
- Remove wget + rpm workaround to manage repos install in CentOS
RDO has moved rdo-release packages to a new infra which supports EMS so
we do not need to wget it and install it using local rpm install.
This partially reverts [1].
[1] https://review.opendev.org/c/openstack/devstack/+/884277/
Change-Id: I189d0c3da0e7b017e2568022c14e6c8fb28251f1
* Update devstack from branch 'master'
to e6ac2b6983dcdd774cdc6bb80158d05d06623425
- Merge "Add OVN_BRIDGE_MAPPINGS - support extra bridge"
- Add OVN_BRIDGE_MAPPINGS - support extra bridge
Add's the OVN_BRIDGE_MAPPINGS variable to ovn_agent.
Uses the same format as OVS_BRIDGE_MAPPINGS, it defaults
to "$PYSICAL_NETWORK:$PUBLIC_BRIDGE".
This enables use of providernet for public network and
setting up additional bridges, for example a for baremetal.
Example:
Q_USE_PROVIDER_NETWORKING="True"
OVS_PHYSICAL_BRIDGE="brbm"
PHYSICAL_NETWORK="mynetwork"
PUBLIC_PHYSICAL_NETWORK="public"
PUBLIC_BRIDGE="br-ex"
OVN_BRIDGE_MAPPINGS="public:br-ex,mynetwork:brbm"
Change-Id: I37317251bbe95d64de06d6232c2d472a98c0ee4d
* Update devstack from branch 'master'
to d51a6b9a1141b687e48ba82e63984a7d44a632c3
- Merge "Fix $LOGDIR owner to be stack.stack"
- Fix $LOGDIR owner to be stack.stack
I have seen this failure in the gate a few times:
[ERROR] /opt/stack/devstack/functions-common:2334 Neutron did not start
/opt/stack/devstack/functions-common: line 310:
/opt/stack/logs/error.log: Permission denied
So whatever was trying to be written to error.log never
happened. Change to be like other directories in this
file and make the $LOGDIR owner stack.stack.
Change-Id: I673011aba10c8d03234100503ccc5876e75baff2
* Update devstack from branch 'master'
to a389128dba4ce7d7051b86f3ac7db4164d24b95f
- OVN: Let ironic manage the OVN startup in it's case.
In order for Ironic perform full testing with devstack, it uses
virtual machines attached to a ovs bridge network to simulate
bare metal machines. This worked great for OVS because often
OVS was already running on the nodes due to the package, and
we could just apply configuration and be done with it when
Ironic's devstack plugin was applying initial configuration and
setting up the test environment.
With OVN, and the requirement of a specific co-installed OVS
version, Ironic has discovered that we cannot perform this same
configuration without having already started OVN during the
initial system setup. Which is fine, but we can't initialize
and start OVN twice. It just doesn't work.
The original form of this patch was proposed by lucasgnomes
in order to validate that we, did, indeed, need to do this
to enable Ironic to successfully test an OVN based
configuration, and is now being revised to handle that case
automatically when Ironic is the selected virt plugin.
Co-Authored-By: Julia Kreger <juliaashleykreger@gmail.com>
Change-Id: Ifbfdaaa97fdbe75ede49dc47235e92a8035d1de6
Zuul