Project

General

Profile

Actions

Feature #22854

open

Installation media for multiple architectures

Added by Lukas Zapletal about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Unattended installations
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Consider the following OS’es defined in Foreman;

CentOS 7.4.1708
Ubuntu 16.04 LTS

Add multiple architectures for each of these, including x86_64, aarch64 & i386 and associate all these architectures with both of the operating systems. Both CentOS and Ubuntu have separate repos for altarch & ports, respectively, which means that you will need minimum 2 IM’s per OS;

IM CentOS 7 x86_64 : http://mirror.centos.org/centos-7/$major.$minor/os/$arch
IM CentOS 7 aarch64 & i386 : http://mirror.centos.org/altarch/$major.minor/os/$arch

IM Ubuntu 16.04 amd64 & i386 : http://archive.ubuntu.com/ubuntu
IM Ubuntu 16.04 aarch64 : http://ports.ubuntu.com

It’s possible to go wrong here as there is no way to define the relationship between architecture and IM. Foreman will present both IM’s and one of them won’t work. Obv naming them as above helps avoid mistakes but the point is you pick the architecture for the OS but that does not translate to the IM in any way I can see.

To further complicate things, Canonical also have the “HWE” flavor and the pxe files lives in the “release-updates” repository and the hard-coded tftp path in Foreman does not match. The only way to fix this that we’ve found is to have a separate OS that use “release-updates” and modify Foreman code to fetch the correct tftp bootfiles based on the release flavor.

Debian seems to be the least troublesome OS to deal with in this context. A single OS for major versions, multiple architectures and single IM seem to work fine.

https://community.theforeman.org/t/need-use-case-for-different-installation-media-for-single-operating-system/8320/6

No data to display

Actions

Also available in: Atom PDF