Age | Commit message (Collapse) | Author | Files | Lines |
|
Since we use networking-vpp's router functionality, we need to create
a tap interface on VPP to connect to br-ex on the host for external
connectivity.
Change-Id: Ia25db8456f1ad6beb96c7b9b5f318b166ef4576a
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
Change-Id: I5dfaf85d67fb038109edaf5c5d8a3e901b9148f4
Signed-off-by: Feng Pan <fpan@redhat.com>
|
|
|
|
Change-Id: I3250b57316b4ec85e0558f1b512f6f3ed7c349fb
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
Signed-off-by: jhinman1 <john.hinman@intel.com>
|
|
This will restore L3 connectivity and trunk ports.
Change-Id: I37039207bc7cf9965d26e6dfa034e84bf9b7224d
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
|
|
This is enabled in regular ODL deployments but is missing from the
bgpvpn scenario. Trunk ports are requested by SDNVPN team for testing
with bgpvpn.
Change-Id: I1b4d3eea61e29e1ede0e06d78fde842ef13b7b8e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
JIRA: APEX-555
Change-Id: Ib94b0182fd5fbc3a254cae5862a82982bf3131be
Signed-off-by: tomsou <soth@intracom-telecom.com>
|
|
Change-Id: Id90ca9975d25cdfa52f266cb6ea578892789efc8
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
stable/pike
|
|
This enables the configuration of notification topics via the
KeystoneNotificationTopics parameter.
Change-Id: I224e730e41e1bcb703e5deebfab3ca74f08faa02
Related-Bug: #1729293
(cherry picked from commit 3de75ccea06a160f8afb21f9da461109a08f7cbc)
|
|
This sets the keystone notification topics only if ceilometer is
enabled. This mitigates the issue of keystone sending notifications
when nobody is receiving them.
Closes-Bug: #1729293
Depends-On: I4dcce73446633c08ea37ba567610eec398094036
Change-Id: I063af5e642388acc180cb8e728481c5a36cc8ddc
(cherry picked from commit 4adb82d03ddd72191bb379f277374a0a5720bbc4)
|
|
In case an ansible update is available during the upgrade then
the ansible package gets updated to a new version by the ansible
tasks. This could potentially lead to issues as the one described
in LP#1729546. This change updates the ansible package via yum
before starting the ansible upgrade tasks in order to avoid having
ansible updating itself.
Related-bug: 1729546
Change-Id: I2ea0aa1f670053578996018663c9fa52dec14b77
(cherry picked from commit 0c1ac1d752aaf88832b34e165f7d147e2304ff1c)
|
|
Due to the fact that it doesn't use a separate CA (or sub CA) for
libvirtd, and that proper SASL is not being used. We are disabling this
option since it doesn't meet the appropriate security requirements.
We'll look into adding this back once these issues get fixed.
Change-Id: I6a5e4db1b6dd6bc8b7e73e53b614b070d15b8a23
Closes-Bug: #1730370
(cherry picked from commit 645757cbd6bdb1a1b75cb4aa8acce80a178099ce)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
nova-manage cell_v2 create_cell just uses a dumb string comparison to detect
when a cell already exists. If there is a slight difference (e.g ordering of
params in the db uri query string) it can result in duplicate cells.
With this patch we should detect that the default cell already exists and
update it to use the current transport_url/database_connection instead of
attempting to create a new cell.
Change-Id: If6a32e87b19cb0edf683144367701a115657ad0a
Closes-bug: 1718912
(cherry picked from commit ebcaabcc5c5d2840128b3609c82c4a70a81ea0a0)
|
|
The compute service list is polled until all expected hosts are reported or a
timeout occurs (600s).
Adds a cellv2_discovery flag to puppet services. Used to generate a list of
hosts that should have cellv2 host mappings.
Adds a canonical fqdn and that should match the fqdn reported by a host.
Adds the ability to upload a config script for docker config instead of using
complex bash on-liners.
Closes-bug: 1720821
Change-Id: I33e2f296526c957cb5f96dff19682a4e60c6a0f0
(cherry picked from commit 61fcfca045aeb5be1ee280d8dd9c260fb39b9084)
|
|
The cinder-backup and cinder-volume templates were lagging behind the
non-pacemaker version and didn't pass CI. This commit aims at bringing
back parity.
Change-Id: I11a12f52538168c858b16c9786eb83ae88161488
Depends-On: Iea84a291414e515d8c72a60646188e5b37354a38
Closes-Bug: #1729430
(cherry picked from commit 72c5c73aaafc013d3e2292cded11234ae2b55e80)
|
|
This was previously conflicting with the InternalApiNetCidr value in
environments/network-environment.yaml.
Change-Id: I3f1cb6f056fb19a1ba93d1076191abe7aca4fa21
Depends-On: Ie803b33c93b931f7fefb87b6833eb22fd59cd92d
Closes-Bug: #1726773
(cherry picked from commit 509209a29be1ac3e72d6ea97eaf328760693daaf)
|
|
|
|
|
|
Now that we got a promotion, there is a container image for fluentd in
tripleomaster registry. We can finally re-enable the containerized
fluentd service in scenario0001.
Change-Id: I636e63f9b66dd47267fa40febf49a6ec9a6b7ef3
Related-Bug: #1721723
Closes-Bug: #1726891
(cherry picked from commit c795e748d2e0fe1299919872250d6951246c1365)
|
|
stable/pike
|
|
stable/pike
|
|
into stable/pike
|
|
|
|
This patch adds env files for SRIOV, OVS-DPDK, L2GW, BGPVPN
and SFC deployments with ODL.
These files contain configs not present in basic ODL deployment
env file. While deploying, these need to be used along the basic
deployment env file like
openstack overcloud deploy \
-e environments/services-docker/neutron-opendaylight.yaml \
-e environments/services-docker/neutron-opendaylight-dpdk.yaml
and
openstack overcloud deploy \
-e environments/services-docker/neutron-opendaylight.yaml \
-e environments/services-docker/neutron-opendaylight-sriov.yaml
and so forth for all other deployments.
Closes-Bug: 1722881
Change-Id: I2b70d3f4518e0c014cf37f7fecd92f69989f0860
(cherry picked from commit e0c89d6593dadd9bf6ba9fa6f618e7c44ec7aa2e)
|
|
For some reasonf that directory doesn't have r/x rights, so when
compress is ran as root, it can access config files in it, but when
horizon is run by apache, it can't, and expects different theme files,
thus failing with OfflineGenerationError. Giving apache access to that
directory fixes the problem and makes the custom theme work.
Closes-bug: #1730911
Change-Id: I53f6db23b036bc9b5a689bbac958550f384194c6
(cherry picked from commit 2827fa428c757180019dd7c1aacafcca554845ab)
|
|
|
|
stable/pike
|
|
into stable/pike
|
|
This change noops ControllerDeployedServer{Pre,Post}Config to avoid
getting the upgrade of a split stack deployment getting stuck due
to the cluster being in maintenance mode. For reference a similar
change has been done for the regular Controller role in:
https://review.openstack.org/#/c/487313/
Change-Id: Idd393011b3c4d0d236780e11a04a59d426750de1
Closes-bug: 1725175
(cherry picked from commit 8e92d7c6db6fcae863a250f63b01a98f7a3f3340)
|
|
|
|
puppet run on never fails, even when it should, since we moved
to the ansible way of applying it. The reason is the current following code:
- name: Run puppet host configuration for step {{step}}
command: >-
puppet apply
--modulepath=/etc/puppet/modules:/opt/stack/puppet-modules:/usr/share/openstack-puppet/modules
--logdest syslog --logdest console --color=false
/var/lib/tripleo-config/puppet_step_config.pp
The above is missing the --detailed-exitcodes switch and so puppet will never
really error out on us and the deployment will keep on running all the
steps even though a previous puppet manifest might have failed. This
cause extra hard-to-debug failures.
Initially the issue was observed on the puppet host runs, but this
parameter is missing also from docker-puppet.py, so let's add it there
as well as it makes sense to return proper error codes whenever we call
puppet.
Besides this being a good idea in general, we actually *have* to do it
because puppet does not fail correctly without this option due to the
following puppet bug:
https://tickets.puppetlabs.com/browse/PUP-2754
Co-Authored-By: Damien Ciabrini <dciabrin@redhat.com>
Change-Id: Ie9df4f520645404560a9635fb66e3af42b966f54
Closes-Bug: #1723163
(cherry picked from commit 11e599d116cfbf7df4dcd0e7670c3405a4224c1a)
|
|
Mixing containers and BM is currently not working. Once the master
promotion will take place we will have a fluentd container and
can readd fluentd as a container and the problem should not re-occurr.
Change-Id: Iad97f7e0e4de56f46a46d2381fc1ea5822a2114a
Related-Bug: #1726891
(cherry picked from commit 35d91ddc6d11bb2696321fff4593d5cca3b0cba8)
|
|
|
|
This is required for nfs exports mounted by the nova_compute container to be
visible to nova_libvirt.
Depends-on: I8a63c044e15d7ca0f54654e9fc9c5d878461aa25
Change-Id: I55859e744e3c2ebbd6975c96b84b6b0774dc6700
Closes-bug: 1730533
(cherry picked from commit ef0493f5ea6a7f5412fcf1e1722d71092aba1398)
|
|
into stable/pike
|
|
into stable/pike
|
|
During mysql initialization, mysql needs to be able to write in the
database directory.
Change-Id: I82c2e46f66ab01021cb910eb7e0d17c81b00fa09
Closes-bug: #1730349
(cherry picked from commit 0d65e380caf89d8c486e8ea87571298a6687b680)
|
|
|
|
|
|
Depends-On: 1d6084045e6019c7ad536a8adfd5249b1d95e37e
Closes-bug: #1722788
Change-Id: I22a815bbc8dad65366fbc212f35bdb9d7b4faa52
(cherry picked from commit 66f85f17273353c30ae5625d29c367e0a5f513a8)
|
|
stable/pike
|
|
|