The new master branch should point now to rocky.
So, HOT templates should specify that they might contain features
for rocky release [1]
Also, this submission updates the yaml validation to use only latest
heat_version alias. There are cases in which we will need to set
the version for specific templates i.e. mixed versions, so there
is added a variable to assign specific templates to specific heat_version
aliases, avoiding the introductions of error by bulk replacing the
the old version in new releases.
[1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky
Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
It was missing tags which were necessary for the role to get the
appropriate certificate [1]. So, without these tags, the certificate
wasn't persisted in the node, and the job would fail if TLS would be
enabled. This was discovered as part of the "Public TLS by default"
work.
[1] https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/role.role.j2.yaml#L565
Change-Id: I46ee2ef837da51be4db30a8c059b82cb1a8c3606
This commit introduces oslo.messaging services in place of a single
rabbitmq server. This will enable the separation of rpc and
notifications for the continued use of a single backend (e.g.
rabbitmq server) or a dual backend for the messaging communications.
This patch:
* add oslo_messaging_rpc and oslo_messaging_notify services
* add puppet services for rpc and notification
(rabbitmq and qdrouterd servers)
* add docker services to deploy rpc (rabbitmq or qdrouterd)
and notify (rabbitmq or shared)
* retains rabbit parameters for core services
* update resource registries, service_net_map, roles, etc.
* update ci environment container scenarios
* add environment generator for messaging
* add release note
Depends-On: Ic2c1a58526febefc1703da5fec12ff68dcc0efa0
Depends-On: I154e2fe6f66b296b9b643627d57696e5178e1815
Depends-On: I03e99d35ed043cf11bea9b7462058bd80f4d99da
Needed-By: Ie181a92731e254b7f613ad25fee6cc37e985c315
Change-Id: I934561612d26befd88a9053262836b47bdf4efb0
Removes hardcoded references to the Ceph container image to use
in CI to rely (and test) the tripleoclient default.
Change-Id: I7f028e31eb5e993aa6af9b7f2c19f64ed45224dd
This service is needed to install CA certificates for the overcloud. We
need it because the plan is to enable public TLS by default. And without
this it won't work.
Change-Id: I168e6a543f7143900fdb855ec29d8532fb9736ae
OVN configuration was not done when deployed with
scenario007 as default for NeutronMl2PluginBase was
used which is neutron-plugin-ml2.yaml. This patch
fixes this to use neutron-plugin-ml2-ovn.yaml which
correctly configures neutron for ovn metadata.
Change-Id: I7cadd0567951b85c1ba69d4b4843ee29b67e7a11
Closes-Bug: #1757134
The ceph-container project is moving to a new style of tags for
Ceph. Update scenario001/004 to pull Ceph container images using
the new tags.
Change-Id: I2a6a7c5fb5148e951f85850c09be7cbb59fce0f8
A very basic deployment to be used with free-ipa, and upgrade ci.
There may be other valuable uses for this deployment as well.
Tested-With: https://review.openstack.org/#/c/540114/
Co-Authored-By: Jiri Stransky <jistr@redhat.com>
Change-Id: I433297dcd597e49a2ffccc2e61118bbba69f883c
These relative paths were incorrect given where these environment files
live in the templates directory tree.
These environment files aren't actually used by ci as their equivalent
network-isolation-absolute.yaml versions are preferred. However, if we
fix these paths we could consider switching ci over to use these as it's
arguable more preferrable instead of the hardcoded packaged path.
Change-Id: Ib0e4779c4883776e25bf7eb5aee60a91ce28a73d
In mixed version test scenario, we can have a ping test triggered
after the overcloud installation just to make sure that it works.
If we fix the version to queen then this scenario cannot work.
Change-Id: Ifdc0531cdba03af63231d3c3b16f59e4e22ec837
This file has been used for the containerized undercloud so we can
deploy a simple bridge with os-net-config.
We're moving the environments used for CI into THT, so we can branch
them. This is part of this effort.
Change-Id: I4255120e12123568a388c75956e6e8d32dec66aa
To be able to support multiple Ceph cluster, an initial step is
to allow for configuration of each cluster name.
Depends-On: I8d5293eaaf104b6374dfa13992a67ddc37397f10
Implements: blueprint custom-ceph-cluster-name
Change-Id: I1b4d51ca6a2d08fa7a68eea680eb104eff732057
Now SNMP is secured, we can re-enable it in CI.
This reverts commit cb90c8ce484d8e0328a0f2a8250e1c0fa81dd6cb.
Change-Id: I4ec805015ab8975d8922279ea64546799f5ce92a
Some work is being done in I46fce28926cb5a881f7384948480266712ae75e3
to secure SNMP on a specific network but until then we need to stop
opening the services so cloud providers won't report any security issue
for TripleO jobs.
Change-Id: Icd8a6ddda6152186d6be4a227f6449232fecba5e
Related-Bug: #1749324
This change converts the existing NIC templates to jinja2 in
order to dynamically render the ports and networks according
to the network_data.yaml. If networks are added to the
network_data.yaml file, parameters will be added to all
NIC templates. The YAML files (as output from jinja with
the default network_data.yaml) are present as an example.
The roles in roles_data.yaml are used to produce NIC configs
for the standard and custom composable roles. In order to
keep the ordering of NICs the same in the multiple-nics
templates, the order of networks was changed in the
network_data.yaml file. This is reflected in the network
templates, and in some of the files that is the only
change.
The roles and roles_data.yaml were modified to include
a legacy name for the NIC config templates for the
built-in roles Controller, Compute, Object Storage,
Block Storage, Ceph Storage, Compute-DPDK, and
Networker roles. There will now be a file produced
with the legacy name, but also one produced with the
<role>-role.j2.yaml format (along with environment
files to help use the new filenames).
Note this change also fixes some typos as well as
a number of templates that had VLANs with device:
entries which were ignored.
Closes-Bug: 1737041
Depends-On: I49c0245c36de3103671080fd1c8cfb3432856f35
Change-Id: I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4
The initial fluentd client implementation predates the introduction of
service_config_settings, and necessitated some invasive changes to
what is now common/serivces.yaml. This commit modifies existing
services to use the service_config_settings based configuration
mechanism supported by more recent versions of the fluentd support in
puppet-tripleo.
Partial-bug: #1715187
Depends-On: I3149902401d68d6fd236073a73a20f982d4b952a
Depends-On: I2b057190ec0e4e75ee4ee47ebe0164c2644e5ab7
Depends-On: Ie7df4b8b94cb0ae38096ab95800f211ef1cd8455
Change-Id: I28028ffa00df2da8e0478a551d3de89c3ee46e1f
This change adds a StorageNFS network. It's required by
https://review.openstack.org/#/c/471245 which implements
NFS Ganesha backend for Manila service.
To define and enable the StorageNFS network, deploy using
network_data_ganesha.yaml instead of network_data.yaml.
Besides the former adding the StorageNFS network, these
are otherwise identical.
If enabled it's also necessary to add StorageNFSIpSubnet and
StorageNFSNetworkVlanID heat parameters into network templates.
Co-Authored-By: Dan Sneddon <dsneddon@redhat.com>
Change-Id: If31722d669efe91082c93ecb815e6c41676480c8
Partially-Implements: blueprint nfs-ganesha
te-broker can set up an OVB stack to deploy the overcloud
with public bond network isolation but the heat templates
used in the overcloud deployment were missing.
This review adds these templates from openstack-virtual-baremetal
so that public bond network isolation can be tested in CI.
Change-Id: Ied543e70491ff85d6fab4371812bca802c6b1032
We installed docker our traditional way when deploying with Kubespray
and disabled Kubespray's management of Docker, because Kubespray
installs non-CentOS Docker binaries.
However, openshift-ansible installs Docker from CentOS, we don't need
to install it using the Docker composable service too. That way
openshift-ansible will be the authority on Docker configuration when
deploying OpenShift.
Change-Id: I1352d4050e2f38300068d858b19e0b4a31cf50a7
Related-Bug: #1741224
This patch adds support for networking-ovn-metadata-agent.
It will deploy the agent on compute nodes and disable Nova
force_config_drive.
The following two patches have been squashed into this one:
* https://review.openstack.org/#/c/525164/
* https://review.openstack.org/#/c/522813/
The reason behind the squash is that we had interdepenencies
and this patch alone wouldn't be testing the code properly
without the two other ones since scenario007 job in baremetal
has been removed for this cycle.
UpgradeImpact
Depends-On: I678652294cb8f964c34b742a0bc0ea360d736fb9
Depends-On: If3dffde5e0db8f7607a9708d36d54d1600fe5da8
Depends-On: I38f775479d178f5b252619635b67f876bc8c5ed5
Depends-On: Ifdd42437333730a3b3e6f36cbab6df0a2971a5a1
Depends-On: I940cec6d670df39ac6e2a3559a028acbeee99331
Change-Id: Idc2bb4e31a64502ac6fcdac771d823509dc328e7
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
This patch will force the 3nodes job to be containerized, like all jobs
should be in Queens.
Another patch in tripleo-quickstart will update the featureset.
Also moving Clustercheck service where MariaDB & Pacemaker run.
Also remove Heat since we'll run Tempest.
Change-Id: I31e1fe29491d2cbaa8ed9cd35ee84bbb1d455154
The ipv4 nic-config templates in tripleo-heat-templates were never
updated to use "group: script" and were still using the deprecated
"group: os-apply-config".
This commit updates the templates. Doing so means they will also work
with the config-download deploy mechanism which only supports the
"group: script" method. This update allows us to move forward with
converting ci jobs that use these templates (such as ovb-ha) to use
config-download.
Change-Id: If3cc2749c070a9e88a33b8b0643aeef8a97dd181
The path to run-os-net-config.sh in these nic config templates for ci
should be relative, not absolute. The absolute path does not honor a
different directory specified via --templates, and it also fails the
overcloud deploy entirely b/c the absolute path does not exist in the
plan in swift.
Change-Id: I85ac081571965f42beef4bd283db985b9a03078f
Ceph containers are started with `docker run --memory`
and `docker run --cpus` to limit their memory and CPU
resources. The defaults for OSD and MDS containers were
recently increased [1] to values better for production
but this change keeps them at lower values just for
CI.
[1] https://github.com/ceph/ceph-ansible/pull/2304
Change-Id: I5b5cf5cc52907af092bea5e162d4b577ee05c23a
Related-Bug: 1741499
docker-puppet.py uses the DockerPuppetDebug boolean to trigger debug
logging. It is disabled by default which makes it hard to understand
what is happening in CI. Let's enable it for CI.
Change-Id: I071955df802d09bb4f6496617942868c7da421fd
To decrease the time test_telemetry_integration takes, we do the
following:
* Enable ManagePolling so ceilometer agents will poll every
ceilometer::agent::polling::polling_interval interval (already set to
15)
* We change the publishers list to set an archive policy to use for
Gnocchi. We use high so one 1 points will be keep every 60s.
Note that the tempest telemetry.alarm_granularity configuration must be
kept in sync with the archive policy. This is done here:
I62c47723d68bb1cef9733df2f737c3ab3f5aa8fb
The test should takes 2 minutes instead of 10 after this change.
Change-Id: Ie00d3487d54f4d1226f6a8a210975eabdcd8a96c
Depends-On: I62c47723d68bb1cef9733df2f737c3ab3f5aa8fb
This parameter must have been missed (or was adder later) when these
were templates were copied from tripleo-ci in
I9fd8b8bbcf18d26b1e05d33e2598c0d146814aff
Change-Id: Iccd871647f44f9ebad7319c664d45188c42c4aae
scenario001 is timeouting a lot while scenario 007 is fine and far from
timeout limit, so moving out services.
Change-Id: Id34321f95a0584cbc9f6e40f3cd47ed0386cfc9d
The job timeouts too much, some services are already covered by
scenarios, no need to duplicate testing.
Change-Id: I30092400142af5c3308534a8da9daa22cbb82bad
Depends-On: I2a4aa707fa10664f1fc9026e3eb417f35834436f
Add CephAnsibleEnvironmentVariables which allows a user to
override any Ansible environment variable.
Depends-On: I5d69af146ca6ca8b3d5f78445cd1b47828daa955
Change-Id: Ic731c8f0c988c485c5b3448182a568b8514cab0a
Closes-Bug: 1738276