- College kickstart blog how to#
- College kickstart blog install#
- College kickstart blog mods#
- College kickstart blog code#
College kickstart blog install#
The ultimate goal is for a UI-less installation, since it should be possible to install the OS without a UI at all. Once the storage and package handling modules have been completed, we should be able to move the remaining back-end logic from the UI to their own modules.
College kickstart blog code#
These are, by far, the most complex parts of our code base, so it is unlikely that the storage and package handling objects will be replaced with modules in Fedora 28. Once the kickstart data is handled by modules, we will begin removing the storage and package handling objects from the UI. This will require careful and significant work, since we will have to move around all of the logic for storage configuration and the packaging to modules. We are also working on additional improvements for pykickstart, which are required for our use cases, such as adding extra attributes to kickstart errors and providing a minimal kickstart handler. We have significant extended the support for working with DBus in Anaconda via the pydbus package. Right now, we are ready to begin using the Timezone module and we’ve already begun working on the Network and User modules. This API will be used by the UI to access the kickstart data. A module will parse and generate one or more kickstart commands and provide an API for accessing and changing the command’s options and values. Each kickstart command will be moved to a DBus module. This can be easily done command by command, until the kickstart data object is completely useless and can be removed. The goal for Fedora 28 is to remove the kickstart data object from the UI. Continue reading “Anaconda: A Look Back at 10 Fedora Releases with New UI” →Īs the modularization of Anaconda is under heavy development, you might want to know what is the status of this project.
To set some context here, the team managed to fix a ton of those bugs and continue implementing features, while also working on RHEL-7.0, RHEL-6.4, RHEL-5.9, and of course Rawhide. It was very overwhelming, but while puttering away as fast as I could get up to speed, I also observed the team triage a huge amount of those bugs and fix a good percentage of them. “Things are a little crazy right now,” said everyone on the team as they welcomed me. It was a mad scramble, because this was it - Fedora 18 and RHEL-7.0 were the releases where the new UI for anaconda would debut, and that bugzilla treadmill was on fire from the speed with which users and QE reported bugs. This will mark the 10-release anniversary of anaconda’s new UI.īack in November 2012, when I joined Red Hat, the team was knee-deep in the midst of Fedora 18 Beta, as well as RHEL-7.0. Continue reading “Anaconda debugging and testing – part 1.” →įedora 28 is on the horizon. Because this topic is quite big I will split it into a few articles.
College kickstart blog how to#
I will describe useful methods to get your changes into the installation environment and how to test them easily with all your required use cases. In this article I want to create a short tutorial about tools which should help with debugging and development of Anaconda. Aside from that, we have unit tests, and we test if RPM files were created successfully. We have automatic installation tests called kickstart tests. Also thanks to modularization, we have much greater test coverage than before. Thanks to this effort, developers can connect to modules and play with them. For example we are working on the Anaconda modularization effort. To cover these issues, we (Anaconda developers) are investing quite a lot of our time to make this situation better.
For most of the common changes, luckily a simple 圆4 Virtual Machine is a good enough solution. And yes, not even developers are able to handle that. To have a really good feeling that everything is tested then the test should have been done on all the supported platforms, including IBM Z systems and Power PC. In addition Anaconda is supported on a variety of platforms and it behaves differently on each. To test Anaconda properly it is required to run it many times with all the modifications. Thanks to this complexity it is not an easy task to just do the required changes and run Anaconda to test it. Users can also run the Anaconda application locally too to create installation media.
College kickstart blog mods#
Additionally, there are installation mods (graphical, text and non-interactive) and these can be controlled manually, partially (default configuration preset) or fully automatic.
Anaconda is quite a complex project with a variety of dependencies on system tools and libraries.