Core/Ram/Disk Filters are not required when using filter_scheduler.
After https://review.openstack.org/#/c/565841 when using these
Filters nova is not scheduling to the ironic nodes and overcloud
deployment fails.
For now just testing the undercloud, good to see what scheduler/filters
are being enabled in overcloud and reflect there as well.
Related-Bug: #1787910
Depends-On: Ia82f1c6be0d5504498e77a90268cad8abecdeae2
Change-Id: I0e376d99adeaa318118833018be81491c6b14095
In the environment/network-environment*.yaml files the
itaration is done only on networks that is enabled.
We do not need conditionals inside the loop to check
wheather the network is enabled or not.
Change-Id: I621c205aebcdb353ac487a5804bbe83fbc20c95d
This patch enables collectd on overcloud nodes to connect to local QDR
running on each overcloud node.
Depends-On: I4cb6aa95e253b7fd19ed265fbcba0dfe6663592d
Change-Id: I1d95454f049ca22d694b21b5102e24c63c6009cd
This parameter would be used by os-vif repo, this would
be used in ovs-vsctl commands to reach remote ovsdb over
tcp/ssl connection.
Depends-On: I0cb78399a777e70ed7c1bf7225574bed146728e1
Change-Id: Ie50e3e60cf44d48cf9cb6f3304520df257906b16
Signed-off-by: hanish gogada <hanishgogadahcu@gmail.com>
We need the tripleo common on the undercloud heat, let's mount an
additional volume to share them.
Change-Id: If306862f5a9b7455165523ab7b8350d18395edb7
Closes-Bug: #1784569
Correct playbook selection is now done automatically using
external_update_tasks and external_upgrade_tasks. The
CephAnsiblePlaybook is still usable and highest priority if set to
something else than the default. It can also be set to [] to
completely skip ceph-ansible playbook execution.
Closes-Bug: #1783949
Change-Id: If7955b31eda432dd61331281ad3d8f25a335fdfe
Depends-On: Ifdf5f1175849f79b98c76b4bcdef2a70f8f1fedb
After switching from Heat workflow resources to external_deploy_tasks,
the `ceph-upgrade run` command no longer works and can be
dropped. Instead we'll be using `external-update run` and
`external-upgrade run` commands, which will not do stack update. It
will run Ansible and for Ceph specifically it will set the necessary
playbook directly via Ansible.
Partial-Bug: #1783949
Change-Id: I3490163bc426d070e245387201d64e07b908c74f
Depends-On: I228ce6228d0bd0bd4d40bc7a7cdd6bfe98a7a6ed
Compute nodes that launch VMs will still need vxlan enabled
vxlan was left out of the enabled driver types in neutron
for the ml2-ansible environment files
Change-Id: Ib56610e403ac1e3a41cb9b65b57c40f12f7b5d54
Closes-Bug: #1783776
This makes the docker-registry service focused on installing the
registry, as it should be. Also this makes it possible to invoke this
service during overcloud deploy too.
This change also switches to calling the tripleo-common script
tripleo-container-image-prepare instead of the full openstack command.
This will allow a mistral image to do a prepare without depending on
the python-tripleoclient package.
The {{role}}Services and {{role}}Count are propagated to
tripleo-container-image-prepare so that images are filtered correctly.
sudo is used instead of become:true so that the tripleo-common mistral
sudoers pattern matches.
Depends-On: Ic1648e43f45bb7604d4c0f9abf247a475fb23707
Change-Id: Ibc16bed673de7b22cd8eef3f6fb0d45871083873
Blueprint: container-prepare-workflow
This patch adds composable new service (QDR) for containerized deployments.
Metrics QDR will run on each overcloud node in 'edge' mode. This basically
means that there is a possibility that there will be two QDRs running
on controllers in case that oslo messaging is deployed. This is a reason why
we need separate composable service for this use case.
Depends-On: If9e3658d304c3071f53ecb1c42796d2603875fcd
Depends-On: I68f39b6bda02ba3920f2ab1cf2df0bd54ad7453f
Depends-On: I73f988d05840eca44949f13f248f86d094a57c46
Change-Id: I1353020f874b348afd98e7ed3832033f85a5267f
NovaResumeGuestsStateOnHostBoot (true/false) parameter which
configures whether or not to start again instances which were running at
the time of a compute reboot.
This will set the resume_guests_state_on_host_boot parameter in nova.conf
and configures and enables libvirt-guests with a dependency to the
docker service to shutdown instances before the libvirt container gets
stopped.
NovaResumeGuestsShutdownTimeout specifies the number in seconds for an
instance to allow to shutdown.
Change-Id: I946600ebbc3afd88385ca89015e8f6a6c46f46ef
Closes-Bug: 1778216
Depends-On: I2766cdd66ff17756daaf1a75ad516a7af6eebddc
Depends-On: Id1cc2e75af316b864cebf601395f1111b7fb049a
This change adds a new routes field to the network
definition in network_data.yaml. This field contains
a list of network routes in JSON, e.g.
[{'destination':'10.0.0.0/16','nexthop':'10.0.0.1'}].
This list is used to set the ``host_routes`` property
of each networks subnet.
Co-Authored-By: Dan Sneddon <dsneddon@redhat.com>
Partial: blueprint tripleo-routed-networks-templates
Depends-On: Ifc5aad7a154c33488a7613c8ee038c92ee6cb1a7
Change-Id: I33b34f1445f4203fbf25edeb093b37c7494c664f
The direct deploy interface looks promising in the scale tests so far,
but it prevent local testing and PoC with nodes with less than 8 GiB
RAM because it has to convert the overcloud-full image in memory.
This change changes back to the iscsi deploy interface, leaving
the direct deploy interface fully configured and opt-in.
This patch will likely be reverted in Stein.
Change-Id: I5f8126474ab15a310b4ba305c4d537b93e9f0399
Related-Blueprint: ironic-direct-deploy
With NovaNfsEnabled instance create fails due to wrong default
secontext. The default in THT is set to nova_var_lib_t in
Ie4fe217bd119b638f42c682d21572547f02f17b2 while
system_u:object_r:nfs_t:s0 should have access. The virt_use_nfs
boolean, which is turned on by openstack-selinux, should cover
this use case.
This changes the default to context=system_u:object_r:nfs_t:s0
Change-Id: I2a28462b6f6bc9f8a41a81ea8c65471f05df3b85
Closes-Bug: 1781894
to eliminate special 'docker' names.
Containerized manila is now the standard way to deploy
so we can avoid confusion by just using the regular
manila environment file names for these rather than having
some manila environment files with 'docker' in their names.
Note that we are using the content of
environments/manila-cephfsnative-config-docker.yaml
for
environments/manila-cephfsnative-config.yaml. This resolves an
issue wherein the parameters in the latter file were not updated
when support for the CephFS-NFS back end was added [1].
Closes-Bug: #1782622
[1] Ib408c7827e5fba0c1b01388db26363806fc64370
Change-Id: I08431d848158846a434fecc98d3bee838c7fad68
When OVN DBs pacemaker bundle is started on the controller nodes,
all the ovsdb-servers are configured to listen on the virtual ip
(on ports 6641/6642). But only master node is configured with virtual ip.
On the other nodes, we see the below error messages
ovsdb_jsonrpc_server|ERR|ptcp:6641:172.17.1.18: listen failed: Cannot assign
requested address.
The commit [1] addressed this issue in puppet-tripleo by setting the
sysctl value 'net.ipv4.ip_nonlocal_bind' to 1 using puppet's sysctl::value.
But the ovn-dbs.yaml service file is missing this puppet tag when the
container 'ovn_dbs_init_bundle' is started.
We can fix the issue by defining this tag, but this also requires setting
'privileged=true' when starting the docker container.
Instead, this patch makes use of the t-h-t param 'KernelIpNonLocalBind'
which was introduced in this commit [2].
[1] - I6f762534350a3f96696c87ccd2d14545dccc8a0b
[2] - Idd3d432b8f7eb573d94cd56be8e05614510ebddf
Change-Id: I5ae8cd368bcd58810b18e172ee685fdbf0e48d98
Closes-bug: #1781585
We inherit the `prepare` commands from deploy, in Rocky we will
automatically get config-download env file there so no need to
explicitly disable DeploymentSteps in *-prepare.yaml files too. We
should also disable the WorkflowSteps in config-download environment,
as they too aren't meant to be used with config-download.
Similarly, for `converge` commands in the *-converge.yaml files we
shouldn't re-enable the DeploymentSteps and WorkflowSteps, as that
would go against using config-download.
Change-Id: I89f54ba9a0a15afd26da4d4b26aba8ef09ebf04b
