As tracked by ci squad at [1] scenario2 standalone is missing some
services and has extra horizon compared to the multinode being
replaced
[1] https://tree.taiga.io/project/tripleo-ci-board/task/543
Change-Id: I034dd365f6fd20060f9ad49c4e81b3c534efbe4b
MongoDB support was stopped in Pike, it is not used anywhere now.
Therefore, in Stein are removing it to clean things up.
Change-Id: I4ec8f35b1dd71c25cfb41cc54105ac743ef67745
As tracked in [1] the scenario4 standalone is carrying some
extra services compared to the multinode it replaces.
This disables cinder, fluentd, horizon and redis for scenario4
[1] https://tree.taiga.io/project/tripleo-ci-board/task/541
Change-Id: Ia6fbe2fe7392f25cc11276e2a9e17f4e5d6df1f1
Neutron has support[1] to set the guaranteed MTU for
networks and network segments so that this is exposed
to plug-ins. In interest of supporting the use of
plug-ins to configure network devices in the future
this change adds MTU property on neutron networks.
The new (optional) property 'mtu' in the network
defenitions in 'network_data.yaml' is used to control
the MTU settings. By default the mtu is '1500'.
We already configure the MTU on the ctlplane neutron
networks, this adds the MTU to composable networks.
Also update the nic-config sample templates to include
mtu settings. A heat value resource is added to
nic-config templates to get the required minimum
viable MTU value for bridges, bonds and member
interfaces to ensure the MTU is large enough to allow
the largest configured MTU to traverse the path.
Closes-Bug: #1790537
Change-Id: I11e38f82eb9040f77412fe8ad200fcc48031e2f8
Numerous files have incorrect modes set. Correct these so that executables
have 755 and yaml files are 644 to address rpmlint errors.
Change-Id: I8db36209b41a492f6b85e3469994de884bf556e8
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration.
With this patch the baremetal version of zaqar service has been removed.
Change-Id: I8947d2fc5e5672e701d2802cd14a3fa176877a7d
Related-Blueprint: services-yaml-flattening
This change combines the previous puppet and docker files into a single file
that performs the docker service installation and configuration.
With this patch the baremetal version of Ironic services have been removed.
Change-Id: Icb33158a129356d939940433c82dae25a6334baf
Related-Blueprint: services-yaml-flattening
The integration between podman and pacemaker is still work in progress.
While it's being done, let's remove pacemaker from this job, so we can
have at least one CI job running with podman on the overcloud.
We still have coverage for pacemaker in the container-upgrade jobs.
This patch will likely be reverted once we have pacemaker + podman
ready for centos7.
Change-Id: I8638386c8f394c98b047fb2ae4ff97daeeaf4475
For the isolated networks we use the subnets host_routes
to set and get the routes for overcloud node interfaces.
This change add's this to the ctlplane interface.
Partial: blueprint tripleo-routed-networks-templates
Change-Id: Id4cf0cc17bc331ae27f8d0ef8f285050330b7be0
With the upgrade to puppet 5, we can no longer use dots in the hieradata
key lookups. This change updates the THT for firewall_rules,
haproxy_endpoints and haproxy_userlists to use the colon notation.
Change-Id: I6f67153e04aed191acb715fe8cfa976ee2e75878
Related-Bug: #1803024
The service is disabled by default but we need it in the registry so we
can enable it later in CI:
https://review.openstack.org/#/c/612526
Change-Id: I74466e6f9148d124734aeac9e06d85f4917abdba
Used by a new featureset[1] that uses the neutron ansible-networking driver
to configure the switch providing networking for overcloud ironic
nodes such that tenant networks are segregated via vlan.
This scenario also sets up ssh keys so that ansible inside the neutron
container can ssh to the controller to configure OVS.
The new scenario also includes a temporary workaround to upgrade
ansible in the neutron container, this can be removed once ansible
in the container is v2.5.8+
Also remove scenario011 as the patches that used it never merged and
now the tennant networks are working in the overcloud, we'll test
with this instead.
[1] - https://review.openstack.org/#/c/579601/
Change-Id: Ife83825216ccb96a5f24918f42a757d0c48b0e9d
This variable is used in the docker_image_availability check to
determine how to query the registries for image availability. Setting
this variable allows us to enable the docker_image_availability check
in the gate.
Change-Id: Ia1da542d342228bb28ad487371fad8d3ffc62d0b
Previously we were only deploying a master node. This commit adds the
worker and infra service to the deployed node and configures it as an
all-in-one node. In order to do so, we need to disable HAproxy when
deploying in all-in-one as the HAproxy instance Openshift deploys on
the infra node conflicts with the one we normally set up. They both
bind ports 80 and 443.
Also removes the useless ComputeServices parameter that only makes
sense in a multinode environment.
Change-Id: I6c7d1b3f2fa5c7b1d9cf695c9e021a4192e5d23a
Depends-On: Ibc98e699d34dc6ab9ff6dce0d41f275b6403d983
Depends-On: I0aa878db62e28340d019cd92769f477189886571
Remove scripts and templates which dealt with Pacemaker and its
resource restarts before we moved to containerized deployments. These
should all now be unused.
Many environments had this mapping:
OS::TripleO::Tasks::ControllerPreConfig: OS::Heat::None
OS::TripleO::Tasks::ControllerPostConfig: OS::Heat::None
OS::TripleO::Tasks::ControllerPostPuppetRestart: ../../extraconfig/tasks/post_puppet_pacemaker_restart.yaml
The ControllerPostPuppetRestart is only ever referenced from
ControllerPostConfig, so if ControllerPostConfig is OS::Heat::None, it
doesn't matter what ControllerPostPuppetRestart is mapped to.
Change-Id: Ibca72affb3d55cf62e5dfb52fe56b3b1c8b12ee0
Closes-Bug: #1794720
NeutronEnableDHCPAgent is no longer consumed anywhere in OpenStack so
this patch is removing all occurrences of it in the environment files.
Change-Id: I042944c3f24d22fa60d4ed13fd9a56c5b93f465f
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
It isn't useful for much of anything in a production deployment
and it conflicts with the local DNS server in CI.
Change-Id: Ied3ecdc71bfdf9bb6439e2c9464aa01346e69226
Closes-Bug: 1795043
Enabling Ceph on scenario010 allow us to test conversion of amphora
image format from QCOW2 to RAW in octavia-undercloud role in
tripleo-common.
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
mistake.
Partial-Bug: #1778303
Related-Bug: #1722758
Change-Id: I717301dc0777ecd2118253a86cd1f8353539482f
This patch adds a new role called OpenShiftInfra which is required to
define infra nodes. We've been bundling infra nodes with compute and
master nodes and they ought to be independent.
With the new node label management introduced in openshift-ansible, it
sounds like this is a good time for us to unbundle these nodes.
Co-Authored-By: Martin André <m.andre@redhat.com>
Depends-On: I291b6ac65eaa1a015bca2ee2bc1be90b0ea0aadc
Change-Id: I4f8127a9e2d822057f3db8f0974ab1db0698985a
scenario007 CI job which enables OVN, is failing with the error
'Property DockerCinderConfigImage not assigned'.
docker-ha.yaml defines the cinder pacemaker service. This patch undefines
the cinder services in scenari007 file.
Change-Id: Ic743377c075c9a6f9a84fb13e35f0c1f29ff7228
As there are several log path that are not set properly to be used by fluentd.
Fluentd needs to be enabled on the scenarios to be able to check the path properly.
This patch only enables fluentd on scenario002-multinode-containers.
Change-Id: If253da4f0f89221dc6ddacc280c984079c6a3c7f