In ancient times, B&R used heat templates to deploy ReaR to the
controllers. Since a long time, this has been superseded by an ansible
playbook ran by openstack overcloud backup --setup-rear. Now, that
feature is duplicated, so we remove the possibility of installing
ReaR with heat.
A deprecation notice has been submitted to stable/train in patch #847148
This patch adds a new CI scenario to support Octavia upgrade CI job
without Ceph until a limitation with standalone upgrade with a single
ceph-mon is resolved .
This change will add a couple extra firewall rules to scenario 003
which will ensure we're exercising an optional code path, which
provides a functional example of how we can leverage the feature.
The scenario test matrix has been updated to indicate "extra firewall"
is tested in scn003.
Signed-off-by: Kevin Carter <email@example.com>
OpenShift deployed by TripleO support has been removed in a downstream
version of Stein which make the upstream support difficult to maintain.
OpenShift can be deployed using OpenShift-Ansible and
users who desire to deploy OpenShift 3.11 onto bare metal nodes can
still do so using openshift-ansible directly. The provisioning of
the Operating System on baremetal can be done with OpenStack Ironic on
the Overcloud or also can be done with deployed-servers, achieving the
Congress doesn't seem to be used anywhere, we never had a bug report or
any sign of somebody out there actually using it.
Let's remove its support in TripleO, to reduce the codebase.
This patch switches the default mechanism driver for neutron from
openvswitch to OVN.
It will also flip scenario007 job to run with ML2/OVS.
Co-Authored-By: Kamil Sambor <firstname.lastname@example.org>
Enabling Ceph on scenario010 allow us to test conversion of amphora
image format from QCOW2 to RAW in octavia-undercloud role in
This patch also removes NeutronServicePlugins from being set (in line
with I3da329db28701c7e9798083982953c5c9c861c50) and unchecks Octavia
from scenario003 in the service testing matrix set previously by
A very basic deployment to be used with free-ipa, and upgrade ci.
There may be other valuable uses for this deployment as well.
Co-Authored-By: Jiri Stransky <email@example.com>
As we create new standard roles, we should include them from a single
location for ease of use and to reduce the duplication of the role
definitions elsewhere. This change adds a roles folder to the THT that
can be used with the new roles commands in python-tripleoclient by the
end user to generate a roles_data.yaml from a standard set of roles.
This submission installs the Neutron L2 Gateway service
in the scenario 004.
This is only to check that the service is installed correctly
no sanity check is running yet.
This submission will enable the BGPVPN API
This addition to scenario004 does not
provide any sanity check for the Neutron API
extension. At this stage is meant to
install the required packages and prerequisites,
configure the extension and
having the services started correctly.
In the README.rst file, this is displayed as
neutron-bgpvpn, so for further integrations
should be added as neutron-<extension_name>
for an easier reading.
This patch enables deployment of sensu-client service in scenario001.
Adds the Manila and CephMDS services into scenario004 and a few
resources in the pingtest to test the Manila deployment.
Also adds Pacemaker to scenario004 which is needed for ManilaShare.
This change adds the ec2api service using the
The deprecated nova-cert service is not supported, and therefore the
RegisterImage action is not supported either.