06-18-2018, 05:25 PM
Anaconda improvements in Fedora 28
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28.png" width="1024" height="768" title="" alt="" /></div><div><p>Fedora 28 was released last month, and the major update brought with it a raft of new features for the Fedora Installer (Anaconda). Like Fedora, Anaconda is a dynamic software project with new features and updates every release. Some changes are user visible, while others happen under the hood — making Anaconda more robust and prepared for future improvements.</p>
<p><span id="more-21630"></span></p>
<h2>User & Root configuration on Fedora Workstation</h2>
<p>When installing Fedora Workstation from the Live media, the user and root configuration screens are no longer in the installer. Setting up users is now only done in the Initial Setup screens after installation.</p>
<div id="attachment_21639" style="width: 1034px" class="wp-caption alignnone"><img class="size-full wp-image-21639" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28.png" alt="The progress hub on a Fedora 28 Workstation live installation." width="1024" height="768" /></p>
<p class="wp-caption-text">The progress hub on a Fedora 28 Workstation live installation.</p>
</div>
<p>The back story is that the Fedora Workstation working group aimed to reduce the number of screens users see during installation. Primarily, this included screens that let a user set option twice: both Anaconda and the Gnome Initial Setup tool upon first boot. The working group considered various options, such as Anaconda reporting which screens have been visited by the user and then hiding them in Gnome Initial Setup. In the end<a href="https://fedoraproject.org/wiki/Releases/28/ChangeSet#Reduce_Initial_Setup_Redundancy"> they opted</a> for just always skipping the user and root configuration screens in Anaconda and just configuring a user with sudo rights in Gnome Initial Setup.</p>
<p>Because of this the respective screen (user creation) shows up just once (in Gnome Initial Setup), making the installation experience more consistent.</p>
<p>It’s also worth noting that this change only affects the Fedora Workstation live image. All other images, including the Fedora Workstation netinst image and other live images, are unaffected.</p>
<h2>Anaconda on DBus</h2>
<p>Last year <a href="https://rhinstaller.wordpress.com/2017/11/23/anaconda-modularization-install-classes-and-addons/">we announced</a> the commencement of our next major initiative — modularizing Anaconda. The main idea is to split the code into several modules that will communicate over DBus. This will provide better stability, extensibility and testability of Anaconda.</p>
<p>Fedora 28 is the first release where Anaconda operates via DBus. At startup, Anaconda starts its private message bus and ten simple modules. For now, <a href="https://rhinstaller.wordpress.com/2018/02/07/what-is-the-next-step-in-anaconda-modularization/">the modules just hold data</a> that are provided by a kickstart file and modified by the UI. The UI uses the data to drive installation. This means that you can use DBus to monitor current settings, but you should use the UI to change them.</p>
<p>You can easily explore the current Anaconda DBus API with the live version of Fedora Workstation 28. Just keep in mind that the API is still unstable, so it might change in the future.</p>
<p>To do so, boot the live image and install the <a href="https://wiki.gnome.org/Apps/DFeet">D-Feet</a> application:</p>
<pre>sudo dnf install d-feet</pre>
<p>Start the installer and get an address of the Anaconda message bus:</p>
<pre>cat /var/run/anaconda/bus.address</pre>
<p>Start D-Feet, choose the option ‘Connect to other Bus’ and copy the first part of the Anaconda bus address to the text field (see the picture below). Click on the ‘Connect’ button. The application will open a new tab and show you a list of available DBus services. Now you can view the interfaces, methods, signals and properties of Anaconda DBus modules and interact with them.</p>
<div id="attachment_21641" style="width: 1034px" class="wp-caption alignnone"><img class="size-full wp-image-21641" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28-1.png" alt="Connecting to the Anaconda DBUS session." width="1024" height="768" /></p>
<p class="wp-caption-text">Connecting to the Anaconda DBUS session.</p>
</div>
<div id="attachment_21642" style="width: 1034px" class="wp-caption alignnone"><img class="size-full wp-image-21642" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28-2.png" alt="The Anaconda DBUS API as visible in D-Feet." width="1024" height="768" /></p>
<p class="wp-caption-text">The Anaconda DBUS API as visible in D-Feet.</p>
</div>
<h2>Blivet 3.0 and Pykickstart 3.0</h2>
<p>Fedora 28 provides version 3 of blivet and Pykickstart, and Anaconda uses the updated versions too. While this is not really visible from end user perspective, changes like this are important to assure a robust and maintainable future for the Anaconda installer.</p>
<p>The main change in Pykickstart 3 is the switch from the deprecated optparse module to argparse for kickstart parsing. This not only brings all the features argparse has, it was also one of the prerequisites for having<a href="https://pykickstart.readthedocs.io/"> automatically generated kickstart documentation on Read the Docs</a>.</p>
<p>Blivet 3 is less radical update, but includes significant API improvements and cleanups. Some installer-related code still sitting in Blivet was finally moved to Anaconda.</p>
<h2>Migrating from authconfig to authselect</h2>
<p>The authconfig tool is deprecated and <a href="https://fedoraproject.org/wiki/Changes/Authselect">replaced with authselect</a> in Fedora 28, so Anaconda deprecated the kickstart command <i>authconfig</i> and introduced a new command: <a href="http://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#authselect"><i>authselect</i></a>. You can still use the <i>authconfig</i> command, but Anaconda will install and run the authselect-compat tool instead.</p>
<h2>Enabled hibernation</h2>
<p><a href="https://fedoraproject.org/wiki/Common_F24_bugs#Hibernation_doesn.27t_work_from_a_standard_install">Previously, Hibernation didn’t work</a> after installation because of a missing kernel option, so it had to be set up manually. Starting with Fedora 28, Anaconda adds the kernel option ‘resume’ with a path to the largest available swap device by default on x86 architectures.</p>
<h2>Reducing Initial Setup dependencies</h2>
<p>The Initial Setup tool is basically a lightweight launcher for arbitrary configuration screens from Anaconda. And while Anaconda often runs from a dedicated installation image, Initial Setup always runs directly on the installed system. This also means all the dependencies of Initial Setup will end up on users system, and unless they are uninstalled, they will take up space more or less forever.</p>
<p>The situation is even more dire on ARM, where users generally just <i>dd</i> a Fedora image to memory card or internal storage on the ARM board and Initial Setup basically acts as the installer, customizing the otherwise identical image for the given user. In this case Initial Setup dependencies directly dictate how small the Fedora image can be.</p>
<p>In Fedora 28, the new <i>anaconda-install-env-deps</i> metapackage depends on all installation-time-only dependencies. The <i>anaconda-install-env-deps</i> package is always installed on installation images (netinst, live), but is <b>not</b> an Initial Setup dependency and should thus prevent all the unnecessary packages from being pulled in to the installed system. There is also a nice side effect of finally consolidating all the <i>install-time-only</i> dependencies in the Anaconda spec file.</p>
<p> </p>
</div>
<div style="margin: 5px 5% 10px 5%;"><img src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28.png" width="1024" height="768" title="" alt="" /></div><div><p>Fedora 28 was released last month, and the major update brought with it a raft of new features for the Fedora Installer (Anaconda). Like Fedora, Anaconda is a dynamic software project with new features and updates every release. Some changes are user visible, while others happen under the hood — making Anaconda more robust and prepared for future improvements.</p>
<p><span id="more-21630"></span></p>
<h2>User & Root configuration on Fedora Workstation</h2>
<p>When installing Fedora Workstation from the Live media, the user and root configuration screens are no longer in the installer. Setting up users is now only done in the Initial Setup screens after installation.</p>
<div id="attachment_21639" style="width: 1034px" class="wp-caption alignnone"><img class="size-full wp-image-21639" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28.png" alt="The progress hub on a Fedora 28 Workstation live installation." width="1024" height="768" /></p>
<p class="wp-caption-text">The progress hub on a Fedora 28 Workstation live installation.</p>
</div>
<p>The back story is that the Fedora Workstation working group aimed to reduce the number of screens users see during installation. Primarily, this included screens that let a user set option twice: both Anaconda and the Gnome Initial Setup tool upon first boot. The working group considered various options, such as Anaconda reporting which screens have been visited by the user and then hiding them in Gnome Initial Setup. In the end<a href="https://fedoraproject.org/wiki/Releases/28/ChangeSet#Reduce_Initial_Setup_Redundancy"> they opted</a> for just always skipping the user and root configuration screens in Anaconda and just configuring a user with sudo rights in Gnome Initial Setup.</p>
<p>Because of this the respective screen (user creation) shows up just once (in Gnome Initial Setup), making the installation experience more consistent.</p>
<p>It’s also worth noting that this change only affects the Fedora Workstation live image. All other images, including the Fedora Workstation netinst image and other live images, are unaffected.</p>
<h2>Anaconda on DBus</h2>
<p>Last year <a href="https://rhinstaller.wordpress.com/2017/11/23/anaconda-modularization-install-classes-and-addons/">we announced</a> the commencement of our next major initiative — modularizing Anaconda. The main idea is to split the code into several modules that will communicate over DBus. This will provide better stability, extensibility and testability of Anaconda.</p>
<p>Fedora 28 is the first release where Anaconda operates via DBus. At startup, Anaconda starts its private message bus and ten simple modules. For now, <a href="https://rhinstaller.wordpress.com/2018/02/07/what-is-the-next-step-in-anaconda-modularization/">the modules just hold data</a> that are provided by a kickstart file and modified by the UI. The UI uses the data to drive installation. This means that you can use DBus to monitor current settings, but you should use the UI to change them.</p>
<p>You can easily explore the current Anaconda DBus API with the live version of Fedora Workstation 28. Just keep in mind that the API is still unstable, so it might change in the future.</p>
<p>To do so, boot the live image and install the <a href="https://wiki.gnome.org/Apps/DFeet">D-Feet</a> application:</p>
<pre>sudo dnf install d-feet</pre>
<p>Start the installer and get an address of the Anaconda message bus:</p>
<pre>cat /var/run/anaconda/bus.address</pre>
<p>Start D-Feet, choose the option ‘Connect to other Bus’ and copy the first part of the Anaconda bus address to the text field (see the picture below). Click on the ‘Connect’ button. The application will open a new tab and show you a list of available DBus services. Now you can view the interfaces, methods, signals and properties of Anaconda DBus modules and interact with them.</p>
<div id="attachment_21641" style="width: 1034px" class="wp-caption alignnone"><img class="size-full wp-image-21641" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28-1.png" alt="Connecting to the Anaconda DBUS session." width="1024" height="768" /></p>
<p class="wp-caption-text">Connecting to the Anaconda DBUS session.</p>
</div>
<div id="attachment_21642" style="width: 1034px" class="wp-caption alignnone"><img class="size-full wp-image-21642" src="http://www.sickgaming.net/blog/wp-content/uploads/2018/06/anaconda-improvements-in-fedora-28-2.png" alt="The Anaconda DBUS API as visible in D-Feet." width="1024" height="768" /></p>
<p class="wp-caption-text">The Anaconda DBUS API as visible in D-Feet.</p>
</div>
<h2>Blivet 3.0 and Pykickstart 3.0</h2>
<p>Fedora 28 provides version 3 of blivet and Pykickstart, and Anaconda uses the updated versions too. While this is not really visible from end user perspective, changes like this are important to assure a robust and maintainable future for the Anaconda installer.</p>
<p>The main change in Pykickstart 3 is the switch from the deprecated optparse module to argparse for kickstart parsing. This not only brings all the features argparse has, it was also one of the prerequisites for having<a href="https://pykickstart.readthedocs.io/"> automatically generated kickstart documentation on Read the Docs</a>.</p>
<p>Blivet 3 is less radical update, but includes significant API improvements and cleanups. Some installer-related code still sitting in Blivet was finally moved to Anaconda.</p>
<h2>Migrating from authconfig to authselect</h2>
<p>The authconfig tool is deprecated and <a href="https://fedoraproject.org/wiki/Changes/Authselect">replaced with authselect</a> in Fedora 28, so Anaconda deprecated the kickstart command <i>authconfig</i> and introduced a new command: <a href="http://pykickstart.readthedocs.io/en/latest/kickstart-docs.html#authselect"><i>authselect</i></a>. You can still use the <i>authconfig</i> command, but Anaconda will install and run the authselect-compat tool instead.</p>
<h2>Enabled hibernation</h2>
<p><a href="https://fedoraproject.org/wiki/Common_F24_bugs#Hibernation_doesn.27t_work_from_a_standard_install">Previously, Hibernation didn’t work</a> after installation because of a missing kernel option, so it had to be set up manually. Starting with Fedora 28, Anaconda adds the kernel option ‘resume’ with a path to the largest available swap device by default on x86 architectures.</p>
<h2>Reducing Initial Setup dependencies</h2>
<p>The Initial Setup tool is basically a lightweight launcher for arbitrary configuration screens from Anaconda. And while Anaconda often runs from a dedicated installation image, Initial Setup always runs directly on the installed system. This also means all the dependencies of Initial Setup will end up on users system, and unless they are uninstalled, they will take up space more or less forever.</p>
<p>The situation is even more dire on ARM, where users generally just <i>dd</i> a Fedora image to memory card or internal storage on the ARM board and Initial Setup basically acts as the installer, customizing the otherwise identical image for the given user. In this case Initial Setup dependencies directly dictate how small the Fedora image can be.</p>
<p>In Fedora 28, the new <i>anaconda-install-env-deps</i> metapackage depends on all installation-time-only dependencies. The <i>anaconda-install-env-deps</i> package is always installed on installation images (netinst, live), but is <b>not</b> an Initial Setup dependency and should thus prevent all the unnecessary packages from being pulled in to the installed system. There is also a nice side effect of finally consolidating all the <i>install-time-only</i> dependencies in the Anaconda spec file.</p>
<p> </p>
</div>