From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 40A60238C0A for ; Mon, 25 Aug 2025 12:03:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756123415; cv=none; b=cBklEyjJC1DDG3a3nJ4vqWNOKFDlRJayfbsvaVmvOK1OHq/34s4mjJCTYEbjoE8CmsWCCGA39+ACWQ6N9hHt84i/iIoRY7K8T7aw/6CkihkqbvlFNCPfIDNSIoXYipfMHqIwwWSkfCGRfLyuYhj8q7NKo7IohkrQ0onOK6XWeCo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756123415; c=relaxed/simple; bh=vyUaeyoxUaRJNHE5t91qdIiz+O5gSReZAnGF9vQTHv0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=qduXK7Q+WUa1dYps1qzSey8gL6QMuWLgMS9t+Wu4lb2DiK9VRefepAzNaYTcQgefjIMfzk8kqu5zshkfy3oNKmRZxVlHtn44rfWl5UE04OTU0qdd87lAHgWtza3USIZx188XP3zYFjVQFaPAAzlP5BZQ8cZ+zTYVZSkMZfffKLI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=nmB2LUlI; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="nmB2LUlI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 05829C4CEED; Mon, 25 Aug 2025 12:03:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1756123414; bh=vyUaeyoxUaRJNHE5t91qdIiz+O5gSReZAnGF9vQTHv0=; h=Date:Reply-To:Subject:To:Cc:References:From:In-Reply-To:From; b=nmB2LUlInQP01yQZszE1KqnG+/v4A/D2/nMD/bFBRY6teyAohH9dGvOrYG+QmAMxG +3AIAZSWiNu20+m+XmIT0XzlH7o27PQHUK81cPYfZ4I0XKzj1PAeiheUuNB4GHXeiF asM/q0gr6E9LquqtInKN3iSHbBxVaBDWynTjch7GxDT1Hn03Jh+MNwlT/tfvUmO+Kw Y8JoX7s0BUe+ecfuN+b880XfI18wzsUZaAKayeJzLnTA8cxvW/c+cbzyr7aiKBGvLe qomyCilN/OGaDdjukNb7KHf4tua89VmRlZ5evhr0bCjmIZbUfSNbtjoPJ+5wBuGz7F hH0IrdfJ9wsHw== Message-ID: <508b99e8-a42d-455c-a264-6599d3c76f41@kernel.org> Date: Mon, 25 Aug 2025 14:03:32 +0200 Precedence: bulk X-Mailing-List: kdevops@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: Daniel Gomez Subject: Re: [RFC PATCH v1] Add an Ansible requirements.yml file To: Luis Chamberlain , Chuck Lever Cc: kdevops@lists.linux.dev, Chuck Lever References: <20250824162305.16602-1-cel@kernel.org> Content-Language: en-US From: Daniel Gomez Organization: kernel.org In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 25/08/2025 10.38, Luis Chamberlain wrote: > On Sun, Aug 24, 2025 at 12:23:05PM -0400, Chuck Lever wrote: >> From: Chuck Lever >> >> Commit b90d89d27659 ("Switch to the cloud.terraform.terraform >> module") introduced the use of the cloud.terraform module, and >> commit 7ccb64834eeb ("guestfs: Replace scripts/destroy_guestfs.sh >> with an Ansible playbook") introduced the use of the >> community.libvirt module. It would be friendly if kdevops could >> pull in the Ansible modules it needs transparently. >> >> The requirements.yml file is a manifest of Ansible collections that >> the project needs to run. Installation of these collections is made >> automatic by adding: >> >> ansible-galaxy install -r requirements.yml >> >> to the "make ansible_cfg" step. This mechanism can keep cached >> versions of collections up to date, and can also constrain a >> cached collection to a specific version, if that's needed. >> >> The initial file contains requirements I could find easily, and >> should be updated over time as new collection dependencies are >> introduced. >> >> See also: >> >> https://docs.ansible.com/ansible/latest/user_guide/collections_using.html >> >> Question: Can we assume that the Ansible controller has internet >> access all the time? > > That's not really an issue at all, but what I learned using galaxy stuff > was if we required *our* own stuff upstream on galaxy it was not worth > it. > > Given you're only using external stuff, then that seems sensible to me. > But now given our ongoing dialog over how to ease the pain to make it > easy to use kdevops for new folks, how would this be handled? Are we > OK with the request to phone home out? I wonder if this is a non-Debian issue? I see I have all these installed by the Debian ansible package: Here the ansible package sources: https://packages.debian.org/forky/all/ansible/filelist ansible-galaxy collection list # /usr/lib/python3/dist-packages/ansible/_internal/ansible_collections Collection Version ---------------------------------------- ------- ansible._protomatter 2.19.0 # /usr/lib/python3/dist-packages/ansible_collections Collection Version ---------------------------------------- ------- amazon.aws 10.1.0 ansible.netcommon 8.0.1 ansible.posix 2.1.0 ansible.utils 6.0.0 ansible.windows 3.2.0 arista.eos 11.0.1 awx.awx 24.6.1 azure.azcollection 3.7.0 check_point.mgmt 6.4.1 chocolatey.chocolatey 1.5.3 cisco.aci 2.12.0 cisco.dnac 6.37.0 cisco.intersight 2.2.0 cisco.ios 10.1.1 cisco.iosxr 11.1.0 cisco.meraki 2.21.4 cisco.mso 2.11.0 cisco.nxos 10.2.0 cisco.ucs 1.16.0 cloud.common 5.0.0 cloudscale_ch.cloud 2.5.2 community.aws 10.0.0 community.ciscosmb 1.0.11 community.crypto 3.0.3 community.digitalocean 1.27.0 community.dns 3.2.7 community.docker 4.7.0 community.general 11.1.2 community.grafana 2.3.0 community.hashi_vault 7.0.0 community.hrobot 2.5.0 community.library_inventory_filtering_v1 1.1.1 community.libvirt 2.0.0 community.mongodb 1.7.10 community.mysql 3.15.0 community.okd 5.0.0 community.postgresql 4.1.0 community.proxmox 1.2.0 community.proxysql 1.6.0 community.rabbitmq 1.6.0 community.routeros 3.8.1 community.sap_libs 1.4.2 community.sops 2.2.1 community.vmware 5.7.1 community.windows 3.0.1 community.zabbix 4.1.0 containers.podman 1.17.0 cyberark.conjur 1.3.6 cyberark.pas 1.0.35 dellemc.enterprise_sonic 3.0.0 dellemc.openmanage 9.12.3 dellemc.powerflex 2.6.1 dellemc.unity 2.0.0 f5networks.f5_modules 1.37.1 fortinet.fortimanager 2.10.0 fortinet.fortios 2.4.0 google.cloud 1.7.0 grafana.grafana 6.0.3 hetzner.hcloud 5.1.0 hitachivantara.vspone_block 4.0.1 ibm.qradar 4.0.0 ibm.storage_virtualize 2.7.4 ieisystem.inmanage 3.0.0 infinidat.infinibox 1.6.3 infoblox.nios_modules 1.8.0 inspur.ispim 2.2.3 junipernetworks.junos 10.0.0 kaytus.ksmanage 2.0.0 kubernetes.core 6.0.0 kubevirt.core 2.2.3 lowlydba.sqlserver 2.6.1 microsoft.ad 1.9.2 microsoft.iis 1.0.3 netapp.cloudmanager 21.24.0 netapp.ontap 23.1.0 netapp.storagegrid 21.15.0 netapp_eseries.santricity 1.4.1 netbox.netbox 3.21.0 ngine_io.cloudstack 2.5.0 openstack.cloud 2.4.1 ovirt.ovirt 3.2.1 purestorage.flasharray 1.36.0 purestorage.flashblade 1.20.0 splunk.es 4.0.0 telekom_mms.icinga_director 2.4.0 theforeman.foreman 5.4.0 vmware.vmware 2.2.0 vmware.vmware_rest 4.8.1 vultr.cloud 1.13.0 vyos.vyos 6.0.0 wti.remote 1.0.10 dpkg -l ansible Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-================-============-=============================================================== ii ansible 12.0.0~b3+dfsg-1 all Configuration management, deployment, and task execution system dpkg -S /usr/lib/python3/dist-packages/ansible_collections/community ansible: /usr/lib/python3/dist-packages/ansible_collections/community