Switches to use ephemeral Heat by default for all overcloud operations
and defaults enable_heat to False in undercloud.conf. Stack data will be
migrated to the ephemeral Heat model (to use the consistent working
directory) as part of the upgrade with the inclusion of the depends-on.
To improve the UX when using ephemeral Heat, "stack resource list" is
now run after "stack failures list" automaticaly in the case of Heat
stack failures.
Signed-off-by: James Slagle <jslagle@redhat.com>
Change-Id: I22b2ec530f8b888a94a88e1726792a8afef227ab
These new configuration options can be used to optionally disable these
services when using ephemeral Heat.
Depends-On: I2c9cf50363579d4e18aaeaf783770ca7a4266622
Change-Id: I5503a0bb632e7ab03e2c6c5fecec617899179525
Signed-off-by: James Slagle <jslagle@redhat.com>
Since tempest container is no longer tested in CI and is
replaced with os_tempest ansible-role.
An user can use and install tempest from rpm which is
supported as earlier.
It removes all the entry point of tempest container.
Depends-On: https://review.opendev.org/c/openstack/tripleo-common/+/771993
Related-Bug: #1916875
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I2e2c126aa95589a8d26eaec9626abbf4a86044ca
The undercloud currently defines the auth token life time in the
undercloud.yaml environment in tripleo-heat-templates. At certain scale,
it makes sense to increase this so we should make it a top level
configuration item.
Change-Id: Ibf917826a2d6b2662215c58c9dd8ec8007e57881
Support for this was removed in THT several releases ago and it was only
for the initial non-containerized undercloud to containerized
undercloud.
Change-Id: I8583f795beaf0d6282cf4c836b7f597da35fb650
We're working on an effort to remove Swift on the Undercloud.
This patch will help us to easily control if whether or not we want
Swift deployed on the Undercloud.
Change-Id: Ia58efb14803d54ca297218a58208c39c31641403
Mistral isn't needed by default anymore, we replaced it by Ansible.
Therefore, we don't need Zaqar enabled by default as well.
Depends-On: https://review.opendev.org/746595
Depends-On: https://review.opendev.org/750795
Change-Id: I327d7f06fc6f49aae42d0a9d22c840f94bd84705
undercloud_enable_paunch isn't needed anymore since we retire Paunch
project.
There is no need of deprecating the option since it would have no effect
if set in undercloud.conf.
Change-Id: I9972d3e9826422cd6ab56c801ff93c4d2dfc8404
When deploying on IPv6 stateful ironic must use the
neutron network interface driver. This because we need
to configure neutron service ports (provisioning, cleaning
etc.) with multiple ip addresses for certain UEFI firmware
and chainloading combinations (iPXE -> Ironic IPA) to work.
Closes-Bug: #1864491
Change-Id: I5a9890ccb95a21b95f488cd7a5b5fd1a6cdff38b
Set to True by default, Paunch remains enabled.
However it can be switched to False, then the Undercloud containers will
be deployed by tripleo-ansible.
Change-Id: I6f9498f2e8e54c6b670d616a3122263cd42c44e8
Add option ipv6_address_mode in undercloud.conf to control
the address mode, dhcpv6-steteful or dhcpv6-steteless, for
IPv6 provisioning network.
Related-Bug: #1847606
Change-Id: I7de5f5487065d20068229e0d34102be6119fbeef
Add a new option ``dns_nameservers`` in the subnet sections
for the undercloud ctlplane network. By default the option
is not set, and in that case the ``undercloud_nameservers``
are used, maintaining the current behaviour.
This decouples the nameservers used on the undercloud and
the ones used for the overcloud nodes. In a DCN setting
different DNS server may be preferred per-site.
Related-Bug: #1834306
Change-Id: I0dc03eddf9ea00ff33cd3ae0cdc8f42a4961e89c
Add the ability to install an undercloud minion which is connected to an
original undercloud. This minion can have either heat-engine or
ironic-conductor deployed on it.
Adds two new openstack commands for the minion install and a new
minion.conf can be used to configure them.
openstack undercloud minion install
openstack undercloud minion upgrade
Depends-On: https://review.opendev.org/#/c/656984
Change-Id: I61832f5088be172eaf31b36a9cca8dc289580bb2
Related-Blueprint: undercloud-minion
This can be set to false for underclouds which only use
deployed-server.
Change-Id: Ia1eaec2ed12eb5eb366e8c78b174aff43b447051
Depends-On: https://review.opendev.org/#/c/664174/
Blueprint: nova-less-deploy
We've retired the tripleo-ui repository so we need to remove the ui
configurations for the undercloud.
Change-Id: I536b2cf361cc4b2e47332bb9842d85ffe0643a60
Related-Bug: #1831478
Add a new parameter to undercloud.conf to disable the container
healthchecks.
The parameter is: container_healthcheck_disabled and it's False by
default, so the healthchecks are enabled by default.
Depends-On: Id8d7e21d58cf5ab155404db597d96665b94d7c2a
Change-Id: Icebfad41cc286a2e209511c147d74f1a933c66a2
Add new option 'host_routes' to the subnet definitions
for the ctlplane network in undercloud.conf.
Routes defined for the local subnet will be appended
to the THT parameter 'ControlPlaneStaticRoutes'. The
net-config template for the undercloud will ensure
these routes are configured on the undercloud.
Routes are also added to UndercloudCtlplaneSubnets
parameter used by the undercloud to create the
ctlplane network and subnets. In THT change:
I46b7c7175f542ad4d375a20f133c05064e7b7222 this new
data is used so that the host routes are configured
for the neutron ctlplane subnets.
Related-Bug: #1819464
Change-Id: I692fcc4a494b2cda1911814a53a0c6ec2f99f807
The docker_bip, docker_insecure_registries and docker_registry_mirror
have been deprecated. docker_bip will be removed in later versions.
docker_insecure_registries has been renamed to
container_insecure_regiestries. docker_registry_mirror has been renamed
to container_registry_mirror.
Change-Id: Ic39e665b241aed74347be5eaf24fb291035d5658
Related-Blueprint: podman-support
Standalone does not use any of the composable networks by
default. Deploy Standaloen using /dev/null as network data
so that these resources are not included when creating the
plan.
Undercloud uses only the External network for the external
VIP. Deploy the undercloud using the Undercloud specific
network_data_undercloud.yaml, ensures external_from_pool.yaml
is in the plan.
Related-Bug: #1809313
Depends-On: Ib11a134df93e59947168b40bc71fb1da9172d4ac
Change-Id: I102912851a3b9952daaf7c4d5a34a919f527f805
This change adds an undercloud_timezone configuration that can be used
to configure the timezone when we install the undercloud.
Change-Id: I5dcf3250a181c3614189618b9bae62e466b00275
Related-Bug: #1784068
* Make dhcp_start and dhcp_end optional for subnet definitions
in undercloud.conf.
* Allow non-contiguous allocation pools for ctlplane subnets
Calcualte the allocation pools by removing the local_ip,
gateway, admin_host, public_host and ``inspection_iprange``,
from the subnets full ip range. Allocation_pools for all
remaining ranges will be configured. A new per-subnet option
``dhcp_exclude`` is added, a list of IP addresses or IP
ranges that will be excluded from the allocation pool. For
example:
dhcp_exclude = 172.20.0.101,172.20.0.210-172.20.0.219
^ ip addr ^ ip range
If dhcp_start is defined and dhcp_end is not defined (or vice
versa) any addresses prior to (or after) this address is
removed from the allocation pools.
Make dhcp_start and dhcp_end options ListOpts to enable non-
contigous allocation pools. For example, to create allocation
pools: [{'start': '172.20.0.100', 'end': '172.20.0.150'},
{'start': '172.20.0.200', 'end': '172.20.0.250'}]
the following configuration can be used in undercloud.conf:
dhcp_start = 172.20.0.100,172.20.0.200
dhcp_end = 172.20.0.150,172.20.0.250
A new method is added for remote_subnet_opts, same options as
for the local_subnet_opts but without the defaults.
To allow optional dhcp_start and dhcp_end for the local_subnet
which have defaults defined, a condition is used to ignore
dhcp_start and dhcp_end in case they are the default values
and the cidr is NOT the default.
Related-Bug: #1806512
Related-Bug: #1807707
Change-Id: I4ba148f465b4c452bd5b2c31009ac8a2897bcd5f
Add docker_bip option to the undercloud.conf in order
to easily override the value of: DockerNetworkOptions
through the undercloud.conf
Change-Id: Ibbf7c6101539bdf575c23295c1b9fa4bfc84cff7
This parameter, default to 'docker' for now, can be changed to 'podman'
if we want to deploy an Undercloud with Podman instead of Docker.
blueprint podman-support
Change-Id: I8e83a3903f6c67087d4e18734a61661dbd597185
In this case an additional architecture is any architecture that is NOT
the same as the one running the install.
Blueprint: multiarch-support
Change-Id: Idbf9d52515bddf598792bf4db71c56084c36075c
Undercloud deployment starts logging into its log file
too late, omitting log records from undercloud_config,
preflight checks. This is a problem as we want to log
at least the commands used for undercloud install/upgrade.
Ideally, messages in stdout/stderr should not miss the
log file.
Fix this via the added custom undercloud_log_file config
(use --log-file for standalone CLI). Use those to
configure logging to a file.
Fix missing formatting, like timestamps and source, for
undercloud config and preflight checks.
Write preflight/install/upgrade logs into the same
logfile.
Move the load oslo config method into shared utilities.
Add the configure logging shared utility for the classless
modules (w/o oslo_log supported). Such modules can
mimic oslo_log behavior defined for the main deployment
modules derived from openstack client classes, which
support logging to files natively and are not affected
by the subject issue. With an exception made for those
classless modules allowing them to log INFO+ be default.
So operators will have the pre-flight check
notes logged, for example.
Change-Id: I340be11bc9471df22f038629679634c3542d34d6
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
This option was added in change
I5cf5798cd084d99a3c892daab6db444d1e608beb but was never actually wired
in to do anything.
Since we now have such comprehensive image build pipelines, I think it
is better to removed this unused option rather than wire it in.
Change-Id: I20f67d8b1bbeb8b768777a41b5d33c819192ea2d
When upgrading a non-containerized undercloud to a containerized
undercloud, operators might want to purge old packages/config that were
deployed in Queens. It can be done by setting upgrade_cleanup to
True. The default is false so the cleanup won't happen in default
upgrades.
Change-Id: Ie770f72a8bf9f13ce7258a22ba9f96e5c70a35c1
In order to support a basic configuration file for a standalone
deployment, this change moves the configuration items out into their own
classes for inheriting configuration items since the undercloud install
is basically a special form of a standalone. By creating a standalone
configuration file, we will be able to use enable_* for services to
allow for a quick deployment of specific architectures.
Change-Id: Id07acaa2dfb8432d97dabccbb256a206cbf94e1f
Related-Blueprint: all-in-one
Alex Schultz