https://review.opendev.org/#/c/611188/ incorrectly removed the
undercloud-aodh.yaml environment file as we still reference it in
python-tripleoclient.
Change-Id: I458dd389ef8a953d5ec8f2bcb0fa454fe0ffffcb
Closes-Bug: #1828893
This reverts commit 374fafd66afa792ba197403b479dadbfa3055bce.
The root cause of the timeout has been addressed by:
Id22b1465d6d2424d90781983b970aba4545feb8a
We don't need that horrible hack.
Related-Bug: #1826281
Change-Id: I5f1c89e7fad7624c2edbf557ec39f5777b089d55
Chrony has replaced the usage of ntp and is not supported beyond Stein.
Change-Id: Iab476205f29e0ca9e4053c0c9fb2d051b72b13f0
Related-Blueprint: tripleo-chrony
All known consumers of boot data (os-collect-config, etc) have a
preference for using config-drive as the data source.
The last known consumer was novajoin, but that switched to preferring
config-drive early in the Stein development cycle[1] so it should now
be safe to switch off the nova metadata API service.
[1] https://review.opendev.org/#/c/607492/
Blueprint: nova-less-deploy
Change-Id: If35aec24f446769fca7897c2126fb6657454f073
This change introduces an optional extracted version of the Placement
service into TripleO. This extracted version will only be required once
the Placement service is fully removed from Nova during the T cycle
(previously S but delayed) at which point the corresponding
NovaPlacement service will also be removed from TripleO.
The majority of this change is code motion between the original
NovaPlacement service and the new PlacementAPI service.
Upgrades from the original NovaPlacement service to the extracted
PlacementAPI service are not currently supported by this change and will
be worked on independently during the Train cycle.
Co-authored-by: mschuppert@redhat.com
Depends-On: https://review.openstack.org/#/c/624335/
Change-Id: I9e3287bcbe9d317f32bf6b468c6ee17f04b6fff9
753a3504184d966c63121ca95bc0135afbc83a75 removed ceph entries
from sample-env-generator/storage.yaml which resulted in nova-nfs
and cinder-netapp-config to be in the same section. Therefore
environment_generator.py did not update the nova-nfs.yaml .
Also add quotes to the nfs version as they are required in
the resulting nova-nfs.yaml .
Closes-Bug: #1825374
Change-Id: I209480f209e3a8841362ea619b1c9b073c89f338
We've switched the selinux mode management to ansible as part of the
deploy-steps and it's always included now so the service is not
necessary.
Change-Id: I562053ba6767bd9ab7af3cf06b93906568bec5cd
This service is mapped to OS::Heat::None by default, but when enabled,
it allows to configure defaut AZ for neutron, AZ for L3/DHCP agents and
AZ-aware network scheduling/routing. The zone name is the stack
name by default, but can be overridden with parameter values.
Change-Id: Ie5762c61cd615d7c115069381d6c43c468806e47
implements: blueprint split-controlplane-templates
This service is mapped to OS::Heat::None by default, but when enabled,
it uses external deploy tasks to create a new aggregate and zone in
Nova. All Compute nodes in the stack will be added to the zone by
default.
The zone name is the stack name by default, but can be overridden with
parameter values.
Change-Id: I0afb2265949f1222a86b350734e62da673e83aa9
Depends-On:I064f872e20537642880d5482cb9e0c2a801715ef
implements: blueprint split-controlplane-templates
After moving sriov configuration to os-net-config, there is no need
for NeutronSriovNumVFs parameter as itwill be deprecated
Also we need to add the NUMATopologyFilter to the
NovaSchedulerDefaultFilters
Change-Id: I566efe482031850df7c926b6dae72e44b6f369f5
This patch groups all metrics related environment files
to single directory and changes it's name to make more
sense.It also adds environment file for enabling RabbitMQ
monitoring.
Co-Authored-By: Nagasai Vinaykumar Kapalavai <vkapalav@redhat.com>
Change-Id: I8419ef82e79d1e26c7b1fc267feadf909a7978d9
Depends-On: I248859bf0e4b70e3a057e96b5fb74be64f4008ed
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration
for the ovn services.
Related-Blueprint: services-yaml-flattening
Change-Id: I6261863c15f594fed8207ff258f1d9c809a9a864
If the plan-environment.yaml includes docker-ha.yaml by default, the
pacemaker version of some services get enabled for the undercloud. Let
us be more explicit about these services in the undercloud environment
file to ensure we get the right version configured always.
Change-Id: I806f95e3b4988b0f3c427a652cdd6ea39154798a
Closes-Bug: #1824030
Not all roles are connected to all networks, there is no
need to create metadata for networks not associated with
the role.
In edge/spine-and-leaf deployments the total number of
composable networks used can be high. Passing all the
networks we quickly go beyond the nova metadata fields
size limit (each field cannot exceed 256 bytes).
Also update tools/check-up-to-date.sh script to use the
simple yaml-diff.py instead of diff. The env generator
code will sort data, while jinja rendered environments
are not sorted, thus need to diff the data in yaml not
the text.
Closes-Bug: #1821377
Change-Id: I5ae3bc845b0a6ad6986d44b14ff4b0737a9b033b
Template level changes to update endpoint list
in ceilometer to support data dispatch to
qdr running locally.
Depends-On: I7bbac48f2dfa9ec532f56a814af25117e11511ea
Depends-On: Ifd5c4bca8d1fc7bbfa9f03fc09250cce9dabd954
Change-Id: Ifb17e002d011a8618496a5af375ac75fd4112630
The environment files that select which network configuration files
to use for a deployment have an incorrect comment. The comment
mentions port configurations above the network configuration
templates. This patch corrects the comments.
Change-Id: Idb5c09f7c803a89d388e4458b032bbebd4b2590b
Closes-bug: 1822693
The entries in the tls-everywhere-endpoints-dns.yaml was wrong for
octavia; pointing to IPs instead of DNS. This made the TLS everywhere
deployment fail, since it assigns certificates for DNS subjectAltNames.
Change-Id: Ic6f0f26c03c443edf1715927a4542245e08567f4
Closes-Bug: #1822035
Move the apache service undercloud the deployment directory.
Change-Id: Iead4f910390cb75f56f96da2d24889a461275c9d
Related-Blueprint: services-yaml-flattening