[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
On Tue, Jan 31, 2023 at 07:21:03PM -0700, Orion Poplawski wrote: > On 1/31/23 11:03, Maxwell G wrote: > > On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote: > > Hi all, > > > > > Hi, Orion > > > Thanks for raising this question. > > > > Indeed! > > > > > I wonder if it's possible to continue to update collections to the > > > newest versions anyway. If someone wants to use the collection version > > > provided in "big ansible", they would use ansible 6.3.0 with all > > > included. If they want a newer collection, they can install a separate > > > newest RPM. > > > > I agree. I think we should update collections to the next major version > > (if it exists) after each RHEL minor release and then keep them updated > > with point releases in between. We update the ansible bundle to the next > > major version that corresponds to RHEL's ansible-core version at each > > RHEL minor release, so it makes to do the same with the standalone > > collection packages. Collection versions that are EOL upstream won't be > > tested with newer ansible-core versions. > > Does this capture the general sentiment? > > - ansible is the static/stable collection of collections paired with the > provided ansible-core for the life of the point release > > - ansible-collection-* packages will be at least the version of the > collection in ansible, and optionally higher while giving due diligence to > avoiding breaking changes. That sounds mostly reasonable. I guess I could come up with a crazy case like 'the version in ansible has some problem that wasn't noticed, so I want to keep the seperate collection on a older version until it's fixed' though. kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
On 1/31/23 11:03, Maxwell G wrote: On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote: Hi all, Hi, Orion Thanks for raising this question. Indeed! I wonder if it's possible to continue to update collections to the newest versions anyway. If someone wants to use the collection version provided in "big ansible", they would use ansible 6.3.0 with all included. If they want a newer collection, they can install a separate newest RPM. I agree. I think we should update collections to the next major version (if it exists) after each RHEL minor release and then keep them updated with point releases in between. We update the ansible bundle to the next major version that corresponds to RHEL's ansible-core version at each RHEL minor release, so it makes to do the same with the standalone collection packages. Collection versions that are EOL upstream won't be tested with newer ansible-core versions. Does this capture the general sentiment? - ansible is the static/stable collection of collections paired with the provided ansible-core for the life of the point release - ansible-collection-* packages will be at least the version of the collection in ansible, and optionally higher while giving due diligence to avoiding breaking changes. -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic Signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
On Tue, Jan 31, 2023 at 06:03:48PM +, Maxwell G wrote: > On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote: > Hi all, Note that some folks cc'ed are not subscribed to epel-devel, so it probibly rejected their posts. :( > > > Hi, Orion > > Thanks for raising this question. > > Indeed! > > > I wonder if it's possible to continue to update collections to the > > newest versions anyway. If someone wants to use the collection version > > provided in "big ansible", they would use ansible 6.3.0 with all > > included. If they want a newer collection, they can install a separate > > newest RPM. > > I agree. I think we should update collections to the next major version > (if it exists) after each RHEL minor release and then keep them updated > with point releases in between. We update the ansible bundle to the next > major version that corresponds to RHEL's ansible-core version at each > RHEL minor release, so it makes to do the same with the standalone > collection packages. Collection versions that are EOL upstream won't be > tested with newer ansible-core versions. Yes, when we first started to package collections we made sure (although I have not checked if anything changed) that the seperately packaged collections would override the bundled ones in the ansible package. So, while the ansible collection of collections and ansible-core are (and should be) closely tied together, the seperately packaged ansible collections should be free to update as long as they continue to work ok with ansible-core thats provided/etc. So, in practice I personally have been thinking of 'ansible' as the stable collection of collections, and the seperately packaged collections as 'next' or 'fast moving' channel. Just my 2cents. kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote: Hi all, > Hi, Orion > Thanks for raising this question. Indeed! > I wonder if it's possible to continue to update collections to the > newest versions anyway. If someone wants to use the collection version > provided in "big ansible", they would use ansible 6.3.0 with all > included. If they want a newer collection, they can install a separate > newest RPM. I agree. I think we should update collections to the next major version (if it exists) after each RHEL minor release and then keep them updated with point releases in between. We update the ansible bundle to the next major version that corresponds to RHEL's ansible-core version at each RHEL minor release, so it makes to do the same with the standalone collection packages. Collection versions that are EOL upstream won't be tested with newer ansible-core versions. -- Thanks, Maxwell G (@gotmax23) Pronouns: He/They ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?
On Mon, 30 Jan 2023 21:13:11 -0700 Orion Poplawski wrote: > So, I'm wondering if we should have some kind of (at least > semi-)coordinated plan for updating ansible collections in EPEL? > > My initial thought is we would sort of piggy back on to what the > "ansible" community collection bundles on top of the ansible-core > package provided by RedHat. So, currently in EL8.7 we have: > > ansible-core-2.13.3 > > and EPEL ships: > > ansible-6.3.0 - which corresponds to the ansible community package > that ships with ansible-2.13.3. > > Then we would endeavor to ship the individual package collection > versions that are contained in that package, .e.g: (taken from the > MANIFEST.json files): > > ansible.posix 1.4.0 > ansible.utils 2.6.1 > chocolatey.chocolatey 1.3.0 > community.docker 2.7.1 > community.general 5.5.0 > community.libvirt 1.2.0 > community.mysql 3.4.0 > community.rabbitmq 1.2.2 > containers.podman 1.9.4 > netbox.netbox 3.7.1 Sounds like a reasonable plan to me. > For reference, currently in epel we have: ... > ansible-collection-community-libvirt.noarch 1.1.0-3.el8 > epel I updated ansible-collection-community-libvirt to 1.2.0: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-98b1fc46a5 > I don't really have a particular agenda here, just trying to solicit > people's thoughts. Personally I like minimal installs so I have been > only using ansible-core + collections on the systems I maintain and > would like to continue to see them be usable together. I too just use ansible-core + collections on the systems I maintain. Regards, Paul. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
