I am hosting esm, cis, fips, and fips-updates for on-prem landscape in the ubuntu distribution but they are all under unique series as recommended by landscape so packages do not overlap.
For now I'd rather just enable each apt repo via landscape repo profile or a different configuration management tool and wait for a fix for correct service enablement. The newer landscape client/server has ability to report status of ubuntu pro services so there is added benefit to get this working for on-prem repos, landscape and airgapped environments.
Hi Lucas,
I am hosting esm, cis, fips, and fips-updates for on-prem landscape in the ubuntu distribution but they are all under unique series as recommended by landscape so packages do not overlap.
IE: landscaperepo. com/repository/ standalone/ ubuntu/ dists/bionic- esm-apps- security landscaperepo. com/repository/ standalone/ ubuntu/ dists/bionic- esm-apps- updates landscaperepo. com/repository/ standalone/ ubuntu/ dists/bionic- esm-infra- security/ landscaperepo. com/repository/ standalone/ ubuntu/ dists/bionic- esm-infra- updates/ landscaperepo. com/repository/ standalone/ ubuntu/ dists/fips- bionic/ landscaperepo. com/repository/ standalone/ ubuntu/ dists/jammy- esm-apps- security/
http://
http://
http://
http://
http://
http://
and so on
Just to understand the workaround: landscaperepo. com/repository/ standalone/ ubuntupro/ dists/{series} ?
Are you suggesting to put of all of these cis{usg}/esm/fips under a different distribution like
http://
For now I'd rather just enable each apt repo via landscape repo profile or a different configuration management tool and wait for a fix for correct service enablement. The newer landscape client/server has ability to report status of ubuntu pro services so there is added benefit to get this working for on-prem repos, landscape and airgapped environments.
Thanks,
Steven