[uyuni-users] DNF module support Uyuni
Hi all, Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ? If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates. Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in. https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy... Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Thanks Silvio for the reply. However I am not really if this help me. If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related: perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1 I guess that this occurs because of the fact that the 'squid' module is installed: Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================ Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k Regards, Philippe. Philippe?Bidault?|?Unix Engineer| Getronics M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in. https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy... Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi Have you seen this ? https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy... Here it might be better explained what the idea is. You need to make a normal repository out of the module repo. The UI helps you to create the filters and check that you do not select conflicting modules. But you need to know which modules you need. You need to create one rule per module. The result is a normal repository. When you assign this instead of the original repositories you have the same behavior as with centos7 and you can install everything what is in the repo and the UI show correct numbers. Calculation all this for every client on the server will never scale to 10 thousands of systems. Somebody told us kartello/foreman AKA Satellite6 uses the same mechanism. Am Donnerstag, 22. Oktober 2020, 12:12:05 CEST schrieb Bidault, Philippe:
Thanks Silvio for the reply.
However I am not really if this help me.
If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related:
perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1
I guess that this occurs because of the fact that the 'squid' module is installed:
Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================ Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k
Regards, Philippe.
Philippe?Bidault?|?Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy...
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
No, I did not, and now what Silvio replied to me yesterday make sense !! Thanks ! I have tested it, and indeed, this is exactly what is needed to be able to efficiently use CentOS 8 clients and in fact all DNF module-aware OS (Fedora, and perhaps others) in Uyuni. What I am not sure to understand is if I need to create a filter for each module, or if only 1 filter to include any module (for example the squid one is enough ? I ask because of this in the documentation: "As long as at least one AppStream filter is enabled in the CLM project, all target repositories are transformed into regular repositories." Philippe Philippe Bidault | Unix Engineer| Getronics M.34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Michael Calmer <mc@suse.de> Sent: jueves, 22 de octubre de 2020 16:39 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Have you seen this ? https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy... Here it might be better explained what the idea is. You need to make a normal repository out of the module repo. The UI helps you to create the filters and check that you do not select conflicting modules. But you need to know which modules you need. You need to create one rule per module. The result is a normal repository. When you assign this instead of the original repositories you have the same behavior as with centos7 and you can install everything what is in the repo and the UI show correct numbers. Calculation all this for every client on the server will never scale to 10 thousands of systems. Somebody told us kartello/foreman AKA Satellite6 uses the same mechanism. Am Donnerstag, 22. Oktober 2020, 12:12:05 CEST schrieb Bidault, Philippe:
Thanks Silvio for the reply.
However I am not really if this help me.
If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related:
perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1
I guess that this occurs because of the fact that the 'squid' module is installed:
Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ====================================================================== ====================================================================== ==================== Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k
Regards, Philippe.
Philippe?Bidault?|?Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content- lifecycle.html
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org N�����r��y隊[��x������칻 �&ޢ���� ����'��-���w�zf��쮞+�z�>� ޮ�^�ˬz��
Hi Philippe, On 23/10/2020 09:51, Bidault, Philippe wrote:
No, I did not, and now what Silvio replied to me yesterday make sense !! Thanks !
I have tested it, and indeed, this is exactly what is needed to be able to efficiently use CentOS 8 clients and in fact all DNF module-aware OS (Fedora, and perhaps others) in Uyuni.
What I am not sure to understand is if I need to create a filter for each module, or if only 1 filter to include any module (for example the squid one is enough ? You need to create a filter per module you want included. If the module depends on any other modules, they will be included automatically. So you just need to add what you actually want in the final repository. I ask because of this in the documentation: "As long as at least one AppStream filter is enabled in the CLM project, all target repositories are transformed into regular repositories." That means, if you don't have any module filters added, the target repositories will also be modular with all the modules as the original.
Philippe
Philippe Bidault | Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com
Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain.
The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you.
Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Michael Calmer <mc@suse.de> Sent: jueves, 22 de octubre de 2020 16:39 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi
Have you seen this ?
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy...
Here it might be better explained what the idea is.
You need to make a normal repository out of the module repo. The UI helps you to create the filters and check that you do not select conflicting modules. But you need to know which modules you need. You need to create one rule per module.
The result is a normal repository. When you assign this instead of the original repositories you have the same behavior as with centos7 and you can install everything what is in the repo and the UI show correct numbers.
Calculation all this for every client on the server will never scale to 10 thousands of systems. Somebody told us kartello/foreman AKA Satellite6 uses the same mechanism.
Am Donnerstag, 22. Oktober 2020, 12:12:05 CEST schrieb Bidault, Philippe:
Thanks Silvio for the reply.
However I am not really if this help me.
If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related:
perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1
I guess that this occurs because of the fact that the 'squid' module is installed:
Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ====================================================================== ====================================================================== ==================== Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k
Regards, Philippe.
Philippe?Bidault?|?Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content- lifecycle.html
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards
Michael Calmer
-------------------------------------------------------------------------- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
N�����r��y隊[��x������칻 �&ޢ���� ����'��-���w�zf��쮞+�z�>� ޮ�^�ˬz��
-- Can Bulut Bayburt <cbbayburt@suse.de> Java/Linux Developer, SUSE Manager, R&D SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
Hi, Understood, thanks ! Knowing that I have no control about which modules/packages the users will install, I guess that I will have to create a filter for every module. Isn't there a better solution knowing that I have counted 59 modules in the CentOS 8 AppStream repository, meaning that I will have to create 59 filters (well, it will be less as you told me that the module dependencies will be automatically added) ? Philippe. Philippe Bidault | Unix Engineer | Getronics M. 34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Can Bulut Bayburt <cbbayburt@suse.de> Sent: viernes, 23 de octubre de 2020 12:06 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Philippe, On 23/10/2020 09:51, Bidault, Philippe wrote:
No, I did not, and now what Silvio replied to me yesterday make sense !! Thanks !
I have tested it, and indeed, this is exactly what is needed to be able to efficiently use CentOS 8 clients and in fact all DNF module-aware OS (Fedora, and perhaps others) in Uyuni.
What I am not sure to understand is if I need to create a filter for each module, or if only 1 filter to include any module (for example the squid one is enough ? You need to create a filter per module you want included. If the module depends on any other modules, they will be included automatically. So you just need to add what you actually want in the final repository. I ask because of this in the documentation: "As long as at least one AppStream filter is enabled in the CLM project, all target repositories are transformed into regular repositories." That means, if you don't have any module filters added, the target repositories will also be modular with all the modules as the original.
Philippe
Philippe Bidault | Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com
Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain.
The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you.
Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Michael Calmer <mc@suse.de> Sent: jueves, 22 de octubre de 2020 16:39 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi
Have you seen this ?
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content- lifecycle-examples.html#_appstream_filters
Here it might be better explained what the idea is.
You need to make a normal repository out of the module repo. The UI helps you to create the filters and check that you do not select conflicting modules. But you need to know which modules you need. You need to create one rule per module.
The result is a normal repository. When you assign this instead of the original repositories you have the same behavior as with centos7 and you can install everything what is in the repo and the UI show correct numbers.
Calculation all this for every client on the server will never scale to 10 thousands of systems. Somebody told us kartello/foreman AKA Satellite6 uses the same mechanism.
Am Donnerstag, 22. Oktober 2020, 12:12:05 CEST schrieb Bidault, Philippe:
Thanks Silvio for the reply.
However I am not really if this help me.
If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related:
perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1
I guess that this occurs because of the fact that the 'squid' module is installed:
Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ===================================================================== = ===================================================================== = ==================== Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k
Regards, Philippe.
Philippe?Bidault?|?Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content - lifecycle.html
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards
Michael Calmer
---------------------------------------------------------------------- ---- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com ---------------------------------------------------------------------- ---- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
N r y隊[ x 칻 &ޢ ' - w zf 쮞+ z > ޮ ^ ˬz
-- Can Bulut Bayburt <cbbayburt@suse.de> Java/Linux Developer, SUSE Manager, R&D SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org N�����r��y隊[��x������칻 �&ޢ���� ����'��-���w�zf��쮞+�z�>� ޮ�^�ˬz��
I have noticed in the documentation that several filters matchers are available: https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy... However, the one I am interesting in, the "matches" one, which should allow to specify all the modules at once with a wildcard regexp is not available. Only 'equals' is. Is this limitation normal ? Philippe. -----Original Message----- From: Bidault, Philippe <Philippe.Bidault@Getronics.com> Sent: viernes, 23 de octubre de 2020 13:35 To: Can Bulut Bayburt <cbbayburt@suse.de>; uyuni-users@opensuse.org Subject: RE: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Understood, thanks ! Knowing that I have no control about which modules/packages the users will install, I guess that I will have to create a filter for every module. Isn't there a better solution knowing that I have counted 59 modules in the CentOS 8 AppStream repository, meaning that I will have to create 59 filters (well, it will be less as you told me that the module dependencies will be automatically added) ? Philippe. Philippe Bidault | Unix Engineer | Getronics M. 34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Can Bulut Bayburt <cbbayburt@suse.de> Sent: viernes, 23 de octubre de 2020 12:06 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Philippe, On 23/10/2020 09:51, Bidault, Philippe wrote:
No, I did not, and now what Silvio replied to me yesterday make sense !! Thanks !
I have tested it, and indeed, this is exactly what is needed to be able to efficiently use CentOS 8 clients and in fact all DNF module-aware OS (Fedora, and perhaps others) in Uyuni.
What I am not sure to understand is if I need to create a filter for each module, or if only 1 filter to include any module (for example the squid one is enough ? You need to create a filter per module you want included. If the module depends on any other modules, they will be included automatically. So you just need to add what you actually want in the final repository. I ask because of this in the documentation: "As long as at least one AppStream filter is enabled in the CLM project, all target repositories are transformed into regular repositories." That means, if you don't have any module filters added, the target repositories will also be modular with all the modules as the original.
Philippe
Philippe Bidault | Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com
Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain.
The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you.
Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Michael Calmer <mc@suse.de> Sent: jueves, 22 de octubre de 2020 16:39 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi
Have you seen this ?
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content- lifecycle-examples.html#_appstream_filters
Here it might be better explained what the idea is.
You need to make a normal repository out of the module repo. The UI helps you to create the filters and check that you do not select conflicting modules. But you need to know which modules you need. You need to create one rule per module.
The result is a normal repository. When you assign this instead of the original repositories you have the same behavior as with centos7 and you can install everything what is in the repo and the UI show correct numbers.
Calculation all this for every client on the server will never scale to 10 thousands of systems. Somebody told us kartello/foreman AKA Satellite6 uses the same mechanism.
Am Donnerstag, 22. Oktober 2020, 12:12:05 CEST schrieb Bidault, Philippe:
Thanks Silvio for the reply.
However I am not really if this help me.
If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related:
perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1
I guess that this occurs because of the fact that the 'squid' module is installed:
Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ===================================================================== = ===================================================================== = ==================== Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k
Regards, Philippe.
Philippe?Bidault?|?Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content - lifecycle.html
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards
Michael Calmer
---------------------------------------------------------------------- ---- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com ---------------------------------------------------------------------- ---- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
N r y隊[ x 칻 &ޢ ' - w zf 쮞+ z > ޮ ^ ˬz
-- Can Bulut Bayburt <cbbayburt@suse.de> Java/Linux Developer, SUSE Manager, R&D SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org N r y隊[ x 칻 &ޢ ' - w zf 쮞+ z > ޮ ^ ˬz
#2791 created (https://github.com/uyuni-project/uyuni/issues/2791). Thanks ! -----Original Message----- From: Bidault, Philippe Sent: 23 October 2020 13:57 To: Can Bulut Bayburt <cbbayburt@suse.de>; uyuni-users@opensuse.org Subject: RE: [uyuni-users] DNF module support Uyuni I have noticed in the documentation that several filters matchers are available: https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content-lifecy... However, the one I am interesting in, the "matches" one, which should allow to specify all the modules at once with a wildcard regexp is not available. Only 'equals' is. Is this limitation normal ? Philippe. -----Original Message----- From: Bidault, Philippe <Philippe.Bidault@Getronics.com> Sent: viernes, 23 de octubre de 2020 13:35 To: Can Bulut Bayburt <cbbayburt@suse.de>; uyuni-users@opensuse.org Subject: RE: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Understood, thanks ! Knowing that I have no control about which modules/packages the users will install, I guess that I will have to create a filter for every module. Isn't there a better solution knowing that I have counted 59 modules in the CentOS 8 AppStream repository, meaning that I will have to create 59 filters (well, it will be less as you told me that the module dependencies will be automatically added) ? Philippe. Philippe Bidault | Unix Engineer | Getronics M. 34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Can Bulut Bayburt <cbbayburt@suse.de> Sent: viernes, 23 de octubre de 2020 12:06 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Philippe, On 23/10/2020 09:51, Bidault, Philippe wrote:
No, I did not, and now what Silvio replied to me yesterday make sense !! Thanks !
I have tested it, and indeed, this is exactly what is needed to be able to efficiently use CentOS 8 clients and in fact all DNF module-aware OS (Fedora, and perhaps others) in Uyuni.
What I am not sure to understand is if I need to create a filter for each module, or if only 1 filter to include any module (for example the squid one is enough ? You need to create a filter per module you want included. If the module depends on any other modules, they will be included automatically. So you just need to add what you actually want in the final repository. I ask because of this in the documentation: "As long as at least one AppStream filter is enabled in the CLM project, all target repositories are transformed into regular repositories." That means, if you don't have any module filters added, the target repositories will also be modular with all the modules as the original.
Philippe
Philippe Bidault | Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W. www.getronics.com
Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain.
The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you.
Legal disclaimer: http://www.getronics.com/legal/ -----Original Message----- From: Michael Calmer <mc@suse.de> Sent: jueves, 22 de octubre de 2020 16:39 To: uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi
Have you seen this ?
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content- lifecycle-examples.html#_appstream_filters
Here it might be better explained what the idea is.
You need to make a normal repository out of the module repo. The UI helps you to create the filters and check that you do not select conflicting modules. But you need to know which modules you need. You need to create one rule per module.
The result is a normal repository. When you assign this instead of the original repositories you have the same behavior as with centos7 and you can install everything what is in the repo and the UI show correct numbers.
Calculation all this for every client on the server will never scale to 10 thousands of systems. Somebody told us kartello/foreman AKA Satellite6 uses the same mechanism.
Am Donnerstag, 22. Oktober 2020, 12:12:05 CEST schrieb Bidault, Philippe:
Thanks Silvio for the reply.
However I am not really if this help me.
If I install squid on a CentOS 8 (yum install squid), I will see 22 false-positives updates appearing on the Uyuni web UI for this server, all Perl related:
perl-constant-1.33-1001.module_el8.1.0+229+cd132df8.noarch perl-constant-1.33-396.el8.noarch CEBA-2019:3337-1 perl-DBI-1.641-3.module_el8.1.0+199+249f9f29.x86_64 perl-DBI-1.641-3.module_el8.1.0+199+8f0a6bbd.x86_64 CEBA-2019:3337-1 perl-Digest-MD5-2.55-397.module_el8.1.0+229+cd132df8.x86_64 perl-Digest-MD5-2.55-396.el8.x86_64 CEBA-2019:3337-1 perl-Digest-SHA-6.02-2.module_el8.1.0+229+cd132df8:1.x86_64 perl-Digest-SHA-6.02-1.el8:1.x86_64 CEBA-2019:3337-1 perl-Exporter-5.72-1001.module_el8.1.0+229+cd132df8.noarch perl-Exporter-5.72-396.el8.noarch CEBA-2019:3337-1 perl-File-Temp-0.230.600-2.module_el8.1.0+229+cd132df8.noarch perl-File-Temp-0.230.600-1.el8.noarch CEBA-2019:3337-1 perl-IO-Socket-IP-0.39-6.module_el8.1.0+229+cd132df8.noarch perl-IO-Socket-IP-0.39-5.el8.noarch CEBA-2019:3337-1 perl-libnet-3.11-4.module_el8.1.0+229+cd132df8.noarch perl-libnet-3.11-3.el8.noarch CEBA-2019:3337-1 perl-MIME-Base64-3.15-1001.module_el8.1.0+229+cd132df8.x86_64 perl-MIME-Base64-3.15-396.el8.x86_64 CEBA-2019:3337-1 perl-parent-0.237-2.module_el8.1.0+229+cd132df8:1.noarch perl-parent-0.237-1.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Escapes-1.07-396.module_el8.1.0+229+cd132df8:1.noarch perl-Pod-Escapes-1.07-395.el8:1.noarch CEBA-2019:3337-1 perl-Pod-Perldoc-3.28-397.module_el8.1.0+229+cd132df8.noarch perl-Pod-Perldoc-3.28-396.el8.noarch CEBA-2019:3337-1 perl-Pod-Usage-1.69-396.module_el8.1.0+229+cd132df8:4.noarch perl-Pod-Usage-1.69-395.el8:4.noarch CEBA-2019:3337-1 perl-Socket-2.027-4.module_el8.1.0+229+cd132df8:4.x86_64 perl-Socket-2.027-3.el8:4.x86_64 CEBA-2019:3337-1 perl-Term-ANSIColor-4.06-397.module_el8.1.0+229+cd132df8.noarch perl-Term-ANSIColor-4.06-396.el8.noarch CEBA-2019:3337-1 perl-Term-Cap-1.17-396.module_el8.1.0+229+cd132df8.noarch perl-Term-Cap-1.17-395.el8.noarch CEBA-2019:3337-1 perl-Text-ParseWords-3.30-396.module_el8.1.0+229+cd132df8.noarch perl-Text-ParseWords-3.30-395.el8.noarch CEBA-2019:3337-1 perl-Text-Tabs+Wrap-2013.0523-396.module_el8.1.0+229+cd132df8.noarch perl-Text-Tabs+Wrap-2013.0523-395.el8.noarch CEBA-2019:3337-1 perl-threads-2.21-3.module_el8.1.0+229+cd132df8:1.x86_64 perl-threads-2.21-2.el8:1.x86_64 CEBA-2019:3337-1 perl-threads-shared-1.58-3.module_el8.1.0+229+cd132df8.x86_64 perl-threads-shared-1.58-2.el8.x86_64 CEBA-2019:3337-1 perl-Time-Local-1.280-2.module_el8.1.0+229+cd132df8:1.noarch perl-Time-Local-1.280-1.el8:1.noarch CEBA-2019:3337-1 perl-Unicode-Normalize-1.25-1001.module_el8.1.0+229+cd132df8.x86_64 perl-Unicode-Normalize-1.25-396.el8.x86_64 CEBA-2019:3337-1
I guess that this occurs because of the fact that the 'squid' module is installed:
Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ===================================================================== = ===================================================================== = ==================== Installing: squid x86_64 7:4.4-8.module_el8.2.0+319+d18e041f.1 susemanager:centos8-x86_64-appstream 3.5 M Installing dependencies: libecap x86_64 1.0.1-2.module_el8.2.0+319+d18e041f susemanager:centos8-x86_64-appstream 29 k perl-Carp noarch 1.42-396.el8 susemanager:centos8-x86_64 30 k perl-DBI x86_64 1.641-3.module_el8.1.0+199+8f0a6bbd susemanager:centos8-x86_64-appstream 740 k perl-Data-Dumper x86_64 2.167-399.el8 susemanager:centos8-x86_64 58 k perl-Digest noarch 1.17-395.el8 susemanager:centos8-x86_64-appstream 27 k
Regards, Philippe.
Philippe?Bidault?|?Unix Engineer| Getronics
M.34617301667 | E. Philippe.Bidault@Getronics.com | W.www.getronics.com -----Original Message----- From: Silvio Moioli <moio@suse.de> Sent: jueves, 22 de octubre de 2020 11:02 To: Bidault, Philippe <Philippe.Bidault@Getronics.com>; uyuni-users@opensuse.org Subject: Re: [uyuni-users] DNF module support Uyuni
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
On 22/10/2020 10.58, Bidault, Philippe wrote:
Does somebody know when the DNF modules available in CentOS 8 for example will be supported in Uyuni ?
If we enable some DNF modules on a CentOS 8, we currently have mismatch between updates showed in the Web UI and real available updates.
Currently what you can do is to create channels via the Content Lifecycle Management feature to "filter" specific modules you are interested in.
https://www.uyuni-project.org/uyuni-docs/uyuni/administration/content - lifecycle.html
Regards, -- Silvio Moioli SUSE Manager Development Team -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
-- Regards
Michael Calmer
---------------------------------------------------------------------- ---- Michael Calmer SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com ---------------------------------------------------------------------- ---- SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer (HRB 36809, AG Nürnberg)
-- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org
N r y隊[ x 칻 &ޢ ' - w zf 쮞+ z > ޮ ^ ˬz
-- Can Bulut Bayburt <cbbayburt@suse.de> Java/Linux Developer, SUSE Manager, R&D SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org N r y隊[ x 칻 &ޢ ' - w zf 쮞+ z > ޮ ^ ˬz
participants (4)
-
Bidault, Philippe -
Can Bulut Bayburt -
Michael Calmer -
Silvio Moioli