Red Hat Bugzilla – Bug 1466967
RFE: Migrate Fedora server install class into the Anaconda source repository
Last modified: 2017-11-15 08:16:52 EST
The Feodra server install class is currently hosted separately from the Anaconda source code and is added via an install class during the installation.
As the Anaconda now contains even non Fedora/RHEL install classes (such as for CentOS or Scientific Linux) I think it no longer makes sense to host the Fedora Server install class separately.
Having install class together with the other install classes should make maintenance, debugging and testing easier. This might also help prevent or at least make easier to spot Install Class related issues such as for example bug 1466964.
As for making sure the Fedora Server is used during Fedora server compsoe generation (which has been raised during the original discussion in bug 1466964) there is now an Anaconda pull request under review that adds support for selecting install class via kickstart which seems like an ideal fit for this.
A slight correction - the bug number in description is unfortunately wrong - bug 1463297 is the correct one.
The Fedora Workstation install class could be moved as well.
(In reply to Vendula Poncova from comment #2)
> The Fedora Workstation install class could be moved as well.
Seems to be located here:
Martin, is this something the Anaconda team is going to take care of, or do you need something from me?
(In reply to Stephen Gallagher from comment #4)
> Martin, is this something the Anaconda team is going to take care of, or do
> you need something from me?
We can handle the merging of the install class to Anaconda codebase ourselves, but coordination with you will certainly be needed for Server to switch to using it.
BTW, this is the final form of the install class selection API I've mentioned in the description:
Stephen, could you point me to kickstarts for composing the Server installer (or logs)? I am not able to find using of fedora-productimg-server among fedora-kickstarts.
I'd even think the current building of server installer composes would keep working after moving the installclass to anaconda tree, without any need for specifying install class in kickstart (which could be a good thing to do nonetheless). I'd think choosing the right class is independent of the fedora-productimg-server package, rather it is set by lorax --version or --product options.
(In reply to Radek Vykydal from comment #7)
> Stephen, could you point me to kickstarts for composing the Server installer
> (or logs)? I am not able to find using of fedora-productimg-server among
> I'd even think the current building of server installer composes would keep
> working after moving the installclass to anaconda tree, without any need for
> specifying install class in kickstart (which could be a good thing to do
> nonetheless). I'd think choosing the right class is independent of the
> fedora-productimg-server package, rather it is set by lorax --version or
> --product options.
Thank you, BTW I guess the place where the install class is set (in compose process) is here: https://pagure.io/pungi-fedora/blob/master/f/fedora.conf#_432.
When this change is applied in Anaconda we can remove the installclass from fedora-productimg-server. I am going to clone a BZ to track that.
The installclass will be added to anaconda package in anaconda-28.11. When the package is built it can be removed from fedora-productimg-server. I'll let you know then.