Skip to content

Synchronise master with upstream#689

Merged
priteau merged 6 commits intostackhpc/masterfrom
upstream/master-2025-03-03
Mar 3, 2025
Merged

Synchronise master with upstream#689
priteau merged 6 commits intostackhpc/masterfrom
upstream/master-2025-03-03

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Mar 3, 2025

This PR contains a snapshot of master from upstream master.

sdodsley and others added 6 commits February 3, 2025 17:57
From the release of 2024.2 (Dalmatian) the SDK required by the
Pure Cinder driver changes from ``purestorage`` to ``py-pure-client``.
This patch updates the Pure documentation to reflect this change.

Change-Id: I7092f3b7ca00019822b8d8f6f425fbb13db9d8ae
When Kolla Ansible is executed with a '--limit' argument, the scope of
an operation is limited to the hosts in the limit. For example:

   kolla-ansible deploy --limit control

Due to the nature of configuring clustered software services, there are
cases where we need to know information about other hosts. Most often
this is related to their hostname or network addresses. To make this
work, Kolla Ansible gathers facts for hosts outside of the limit using
delegated fact gathering [1].

By default, Kolla Ansible gathers facts for all hosts. Because delegated
facts are gathered serially in batches by the active hosts, this can
take a long time when there are not many hosts in the limit.

This change makes it possible to reduce the set of hosts eligible for
delegated fact gathering by setting 'kolla_ansible_delegate_facts_hosts'
to a list of hosts.

[1] https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_delegation.html#delegating-facts

Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/899615

Change-Id: Id0bda00b81b5bc6a9a870e231335c33d9828e95f
In many cases we use the kolla_address filter to look up the IP address
of the current host or another host on a particular network interface.
This filter uses the host's facts to determine the IP, meaning that we
must have gathered facts for the host, even if it is outside of a
requested --limit. This is a limitation, since it requires that all
hosts must be reachable, even if we are not directly configuring them.

Most instances of this cross-host fact referencing involve a controller,
since they host clustered services. The only instance found to affect
compute nodes is in the prometheus role, where Prometheus server needs
to know the IP address of all targets in its scrape configs.

If we are able to specify the address of the scrape targets as a static
variable such as a host variable, then facts would not be required for
compute nodes outside of the --limit.

Removing the requirement to have facts for all compute nodes has
benefits for performance (gathering facts for all hosts can take a long
time) and fault tolerance (we can operate when some compute hosts are
unreachable).

This change modifies the kolla_address filter to accept an optional
override_var argument which can be used to specify the name of a host
variable that may override the returned IP address. This is used in the
Prometheus server configuration to allow specifying the IP address used
by Prometheus server when collecting metrics from exporter using
a 'prometheus_target_address' host variable. If specified, this takes
precedence over the API interface address currently used. This makes it
possible to statically override prometheus_target_address and avoid the
cross-host fact reference.

This is not a complete solution because it is not yet possible to skip
the cross-host fact gathering step.

Partial-Bug: #2041860
Change-Id: I207ca56362de00d8ec578333eab9e1a72e7bcd19
@github-actions github-actions bot requested a review from a team as a code owner March 3, 2025 06:22
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Mar 3, 2025
@priteau priteau closed this Mar 3, 2025
@priteau priteau reopened this Mar 3, 2025
@priteau priteau enabled auto-merge March 3, 2025 08:33
@priteau priteau merged commit d2ad8ef into stackhpc/master Mar 3, 2025
3 checks passed
@priteau priteau deleted the upstream/master-2025-03-03 branch March 3, 2025 08:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated action performed by GitHub Actions synchronisation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants