5. Developing Installer Add-ons
5.1. Introduction to Anaconda and Add-ons
5.1.1. Introduction to Anaconda
Gtkwidgets (written in C),
dracutlibraries. Together, they form a tool that allows users to set parameters of the resulting (target) system and then set such a system up on a machine. The installation process has four major steps:
- installation destination preparation (usually disk partitioning)
- package and data installation
- boot loader installation and configuration
- configuration of the newly installed system
VNC, which allows you to use the GUI even on systems with no graphics cards or even attached monitor. However, there are still cases where this is not desired, but at the same time, you may want to perform an interactive installation. For these cases, a text mode (TUI) is available. The TUI works in a way similar to a monochrome line printer, which allows it to work even on serial consoles which do not support cursor movement, colors and other advanced features. The text mode is limited in that it only allows you to customize most common options, such as network settings, language options or installation (package) source; advanced features such as manual partitioning are not available in this interface.
5.1.2. Firstboot and Initial Setup
pygtk2module.  For this reason, a new tool called Initial Setup was developed, which reuses code from Anaconda. This allows add-ons developed for Anaconda to be easily reused in Initial Setup. This topic is further discussed in Section 5.6, “Writing an Anaconda add-on”.
5.1.3. Anaconda and Initial Setup Add-ons
%addon com_redhat_kdumpcommand and its options) and is fully integrated as an additional screen in the text-based and graphical interfaces. You can develop other add-ons in the same way and add them to the default installer using procedures described further in this guide.
5.1.4. Additional Information
- The Anaconda page on Fedora Project Wiki contains provides more information about the installer.
- Information about development of Anaconda into its current version is available at the Anaconda/NewInstaller Wiki page.
- The Kickstart Installations chapter of the Red Hat Enterprise Linux 7 Installation Guide provides full documentation of Kickstart, including a list of all supported commands and options.
- The Installing Using Anaconda chapter of the Red Hat Enterprise Linux 7 Installation Guide describes the installation process in the graphical and text user interfaces.
- For information about tools used for after-installation configuration, see Initial Setup and Firstboot.
5.2. Architecture of Anaconda
pykickstart- used to parse and validate Kickstart files and also to provide a data structure which stores values which drive the installation
yum- the package manager which handles installation of packages and resolving dependencies
blivet- originally split from the anaconda package as pyanaconda.storage; used to handle all activities related to storage management
pyanaconda- package containing the core of the user interface and modules for functionality unique to Anaconda, such as keyboard and timezone selection, network configuration, and user creation, as well as a number of utilities and system-oriented functions
python-meh- contains an exception handler which gathers and stores additional system information in case of a crash and passes this information to the
libreportlibrary, which itself is a part of the ABRT Project.
pykickstartmodule and imported into memory as a tree-like structure. If no Kickstart file is provided, an empty tree-like structure is created instead. If the installation is interactive (not all required Kickstart commands have been used), the structure is then updated with choices made by the user in the interactive interface.
/root/directory on the installed system; therefore the installation can be replicated automatically by reusing this automatically generated Kickstart file.
pyanaconda.kickstartmodule. An important rule which governs this behavior is that there is no place to store configuration data, and the installation process is data-driven and relies on transactions as much as possible. This enforces the following features:
- every feature of the installer must be supported in Kickstart
- there is a single, obvious point in the installation process where changes are written to the target system; before this point, no lasting changes (e.g. formatting storage) are made
- every change made manually in the user interface is reflected in the resulting Kickstart file and can be replicated
setupmethod) to modify the runtime environment of the installation if necessary, and then executed (the
executemethod) to perform the changes on the target system. These methods are further described in Section 5.6, “Writing an Anaconda add-on”.
5.3. The Hub & Spoke model
- users are not forced to go through the screens in some strictly defined order
- users are not forced to visit every screen no matter if they understand what the options configured in it mean or not
- it is good for the transactional mode where all desired values can be set while nothing is actually happening to the underlying machine until a special button is clicked
- it provides way to show an overview of the configured values
- it has a great support for extensibility, because additional spokes can be put on hubs without need to reorder anything and resolve some complex ordering dependencies
- it can be used for both graphical and text mode of the installer
Figure 2. Diagram of the hub and spoke model
- The Installation Summary hub which shows a summary of configured options before the installation begins
- The Configuration and Progress hub which appears after you click Begin Installation in Installation Summary, and which displays the progress of the installation process and allows you to configure additional options (set the root password and create a user account).
- ready - states whether the spoke can be visited or not; for example, when the installer is configuring a package source, that spoke is not ready, is colored gray, and cannot be accessed until configuration is complete
- completed - marks the spoke as completed (all required values are set) or not
- mandatory - determines whether the spoke must be visited and confirmed by the user before continuing the installation; for example, the Installation Destination spoke must always be visited, even if you want to use automatic disk partitioning
- status - provides a short summary of values configured within the spoke (displayed under the spoke name in the hub)
5.4. Threads and Communication
GLib.idle_add, which is not always easy or desired. To alleviate this problem, several helper functions and decorators are defined in the pyanaconda.ui.gui.utils module.
@gtk_action_nowaitdecorators. They change the decorated function or method in such a way that when this function or method is called, it is automatically queued into Gtk's main loop, run in the main thread, and the return value is either returned to the caller or dropped, respectively.
hubQ, which is being periodically checked in the main event loop. When a spoke becomes accessible, it sends a message to this queue announcing this change and that it should no longer be blocked.
progressQwhich serves as a medium to transfer installation progress updates.
5.5. Anaconda Add-on Structure
__init__.pyand other source directories (subpackages) inside. Because Python allows importing each package name only once, the package top-level directory name must be unique. At the same time, the name can be arbitrary, because add-ons are loaded regardless of their name - the only requirement is that they must be placed in a specific directory.
_) instead of dots so that the directory name is a valid identifier for a Python package. An example add-on name following these suggestions would therefore be e.g.
com_example_hello_world. This convention follows the recommended naming scheme for Python package and module names.
__init__.pyfile in each directory. Directories missing this file are not considered valid Python packages.
guifor the graphical interface and
tuifor the text-based interface. The
tuipackages must also contain a
tui/directories can contain Python modules with any name.
Example 2. Sample Add-on Structure
com_example_hello_world ├─ ks │ └─ __init__.py ├─ gui │ ├─ __init__.py │ └─ spokes │ └─ __init__.py └─ tui ├─ __init__.py └─ spokes └─ __init__.py
5.6. Writing an Anaconda add-on
5.6.1. Kickstart Support
com_example_hello_world/ks/directory you have created previously, make sure it contains an
__init__.pyfile, and add another Python script named
%addonstatement and is closed by
%addonline also contains the name of the add-on (such as
%addon com_example_hello_world) and optionally a list of arguments, if the add-on supports them.
Example 3. Using an Add-on in a Kickstart File
%addon ADDON_NAME [arguments] first line second line ... %end
AddonData. This class is defined in pyanaconda.addons and represents an object for parsing and storing data from a Kickstart file.
AddonDataclass. Anything between the first and last line is passed to the add-on's class one line at a time. To keep the example Hello World add-on simple, it will merge all lines in this block into a single line and separate the original lines with a space.
AddonDatawith a method for handling the list of arguments from the
%addonline, and a method for handling lines inside the section. The
pyanaconda/addons.pymodule contains two methods which can be used for this:
handle_header- takes a list of arguments from the
%addonline (and line numbers for error reporting)
handle_line- takes a single line of content from between the
Example 4. Using handle_header and handle_line
from pyanaconda.addons import AddonData from pykickstart.options import KSOptionParser # export HelloWorldData class to prevent Anaconda's collect method from taking # AddonData class instead of the HelloWorldData class # :see: pyanaconda.kickstart.AnacondaKSHandler.__init__ __all__ = ["HelloWorldData"] HELLO_FILE_PATH = "/root/hello_world_addon_output.txt" class HelloWorldData(AddonData): """ Class parsing and storing data for the Hello world addon. :see: pyanaconda.addons.AddonData """ def __init__(self, name): """ :param name: name of the addon :type name: str """ AddonData.__init__(self, name) self.text = "" self.reverse = False def handle_header(self, lineno, args): """ The handle_header method is called to parse additional arguments in the %addon section line. :param lineno: the current linenumber in the kickstart file :type lineno: int :param args: any additional arguments after %addon <name> :type args: list """ op = KSOptionParser() op.add_option("--reverse", action="store_true", default=False, dest="reverse", help="Reverse the display of the addon text") (opts, extra) = op.parse_args(args=args, lineno=lineno) # Reject any additoinal arguments. Since AddonData.handle_header # rejects any arguments, we can use it to create an error message # and raise an exception. if extra: AddonData.handle_header(self, lineno, extra) # Store the result of the option parsing self.reverse = opts.reverse def handle_line(self, line): """ The handle_line method that is called with every line from this addon's %addon section of the kickstart file. :param line: a single line from the %addon section :type line: str """ # simple example, we just append lines to the text attribute if self.text is "": self.text = line.strip() else: self.text += " " + line.strip()
__all__variable which is necessary to prevent Anaconda's collect method from taking the
AddonDataclass instead of add-on specific
HelloWorldDataclass inherited from
__init__method calling the parent's
__init__and initializing the attributes
self.reverseattribute is populated in the
handle_headermethod, and the
self.textis populated in
handle_headermethod uses an instance of the
pykickstartto parse additional options used on the
handle_linestrips the content lines of white space at the beginning and end of each line, and appends them to
setup- called before the installation transaction starts and used to make changes to the installation runtime environment
execute- called at the end of the transaction and used to make changes to the target system
Example 5. Importing the setup and execute Methods
import os.path from pyanaconda.addons import AddonData from pyanaconda.constants import ROOT_PATH HELLO_FILE_PATH = "/root/hello_world_addon_output.txt"
executemethods included is below:
Example 6. Using the setup and execute Methods
def setup(self, storage, ksdata, instclass, payload): """ The setup method that should make changes to the runtime environment according to the data stored in this object. :param storage: object storing storage-related information (disks, partitioning, bootloader, etc.) :type storage: blivet.Blivet instance :param ksdata: data parsed from the kickstart file and set in the installation process :type ksdata: pykickstart.base.BaseHandler instance :param instclass: distribution-specific information :type instclass: pyanaconda.installclass.BaseInstallClass :param payload: object managing packages and environment groups for the installation :type payload: any class inherited from the pyanaconda.packaging.Payload class """ # no actions needed in this addon pass def execute(self, storage, ksdata, instclass, users, payload): """ The execute method that should make changes to the installed system. It is called only once in the post-install setup phase. :see: setup :param users: information about created users :type users: pyanaconda.users.Users instance """ hello_file_path = os.path.normpath(ROOT_PATH + HELLO_FILE_PATH) with open(hello_file_path, "w") as fobj: fobj.write("%s\n" % self.text)
setupmethod does nothing; the Hello World add-on does not make any changes to the installation runtime environment. The
executemethod writes stored text into a file created in the target system's root (
__str__method recursively on the tree-like structure storing installation data, which means that the class inherited from
AddonDatamust define its own
__str__method which returns its stored data in valid Kickstart syntax. This returned data must be possible to parse again using
__str__method will be similar to the following example:
Example 7. Defining a __str__ Method
def __str__(self): """ What should end up in the resulting kickstart file, i.e. the %addon section containing string representation of the stored data. """ addon_str = "%%addon %s" % self.name if self.reverse: addon_str += "--reverse" addon_str += "\n%s\n%%end" % self.text return addon_str
__str__), it becomes a valid Anaconda add-on. You can continue with the following sections to add support for the graphical and text-based user interfaces, or you can continue with Section 5.7, “Deploying and testing an Anaconda add-on” and test the add-on.
5.6.2. Graphical user interface
126.96.36.199. Basic features
NormalSpoke, which is defined in
pyanaconda.ui.gui.spokes. As the class name suggests, it is a class for the normal spoke type of screen as described in Section 5.3, “The Hub & Spoke model”.
NormalSpoke, you must define the following class attributes which are required by the API:
builderObjects- lists all top-level objects from the spoke's
.gladefile that should be, with their children objects (recursively), exposed to the spoke - or should be an empty list if everything should be exposed to the spoke (not recommended)
mainWidgetName- contains the id of the main window widget  as defined in the
uiFile- contains the name of the
category- contains the class of the category the spoke belongs to
icon- contains the identifier of the icon that will be used for the spoke on the hub
titledefines the title that will be used for the spoke on the hub
Example 8. Defining Attributes Required for the Normalspoke Class
# will never be translated _ = lambda x: x N_ = lambda x: x # the path to addons is in sys.path so we can import things from org_fedora_hello_world from org_fedora_hello_world.gui.categories.hello_world import HelloWorldCategory from pyanaconda.ui.gui.spokes import NormalSpoke # export only the spoke, no helper functions, classes or constants __all__ = ["HelloWorldSpoke"] class HelloWorldSpoke(NormalSpoke): """ Class for the Hello world spoke. This spoke will be in the Hello world category and thus on the Summary hub. It is a very simple example of a unit for the Anaconda's graphical user interface. :see: pyanaconda.ui.common.UIObject :see: pyanaconda.ui.common.Spoke :see: pyanaconda.ui.gui.GUIObject """ ### class attributes defined by API ### # list all top-level objects from the .glade file that should be exposed # to the spoke or leave empty to extract everything builderObjects = ["helloWorldSpokeWindow", "buttonImage"] # the name of the main window widget mainWidgetName = "helloWorldSpokeWindow" # name of the .glade file in the same directory as this source uiFile = "hello_world.glade" # category this spoke belongs to category = HelloWorldCategory # spoke icon (will be displayed on the hub) # preferred are the -symbolic icons as these are used in Anaconda's spokes icon = "face-cool-symbolic" # title of the spoke (will be displayed on the hub) title = N_("_HELLO WORLD")
__all__attribute is used to export the spoke class, followed by the first lines of its definition including definitions of attributes mentioned above. The values of these attributes are referencing widgets defined in
category, which has its value imported from the
HelloWorldCategoryclass from the
HelloWorldCategoryclass will be discussed later, but for now, note that the path to add-ons is in sys.path so that things can be imported from the com_example_hello_world package.
title, which contains two underscores in its definition. The first one is part of the
N_function name which marks the string for translation, but returns the non-translated version of the string (translation is done later). The second underscore marks the beginning of the title itself and makes the spoke reachable using the Alt+H keyboard shortcut.
__init__method and the
__init__method should only call the parent's
__init__method and (for example) initialize non-GUI attributes. On the other hand, the
initializemethod that is called when the installer's graphical user interface initializes should finish the full initialization of the spoke.
Example 9. Defining the __init__ and initialize Methods
def __init__(self, data, storage, payload, instclass): """ :see: pyanaconda.ui.common.Spoke.__init__ :param data: data object passed to every spoke to load/store data from/to it :type data: pykickstart.base.BaseHandler :param storage: object storing storage-related information (disks, partitioning, bootloader, etc.) :type storage: blivet.Blivet :param payload: object storing packaging-related information :type payload: pyanaconda.packaging.Payload :param instclass: distribution-specific information :type instclass: pyanaconda.installclass.BaseInstallClass """ NormalSpoke.__init__(self, data, storage, payload, instclass) def initialize(self): """ The initialize method that is called after the instance is created. The difference between __init__ and this method is that this may take a long time and thus could be called in a separated thread. :see: pyanaconda.ui.common.UIObject.initialize """ NormalSpoke.initialize(self) self._entry = self.builder.get_object("textEntry")
dataparameter passed to the
__init__method. This is the in-memory tree-like representation of the Kickstart file where all data is stored. In one of the ancestors'
__init__methods it is stored in the
self.dataattribute, which allows all other methods in the class to read and modify the structure.
HelloWorldDataclass has already been defined in Section 5.6.1, “Kickstart Support”, there already is a subtree in
self.datafor this add-on, and its root (an instance of the class) is available as
__init__does is initializing an instance of the
GtkBuilderwith the spoke's
.gladefile and storing it as
self.builder. This is used in the
initializemethod to get the
GtkTextEntryused to show and modify the text from the kickstart file's %addon section.
initializemethods are both important when the spoke is created. However, the main role of the spoke is to be visited by an user who wants to change or review the values this spoke shows and sets. To enable this, three other methods are available:
refresh- called when the spoke is about to be visited; This method refreshes the state of the spoke (mainly its UI elements) to make sure that current values stored in the
self.datastructure are displayed
apply- called when the spoke is left and used to store values from UI elements back into the
execute- called when the spoke is left and used to perform any runtime changes based on the new state of the spoke
Example 10. Defining the refresh, apply and execute Methods
def refresh(self): """ The refresh method that is called every time the spoke is displayed. It should update the UI elements according to the contents of self.data. :see: pyanaconda.ui.common.UIObject.refresh """ self._entry.set_text(self.data.addons.org_fedora_hello_world.text) def apply(self): """ The apply method that is called when the spoke is left. It should update the contents of self.data with values set in the GUI elements. """ self.data.addons.org_fedora_hello_world.text = self._entry.get_text() def execute(self): """ The excecute method that is called when the spoke is left. It is supposed to do all changes to the runtime environment according to the values set in the GUI elements. """ # nothing to do here pass
ready- determines whether the spoke is ready to be visited; if the value is false, the spoke is not accessible (e.g. the Package Selection spoke before a package source is configured)
completed- determines if the spoke has been completed
mandatory- determines if the spoke is mandatory or not (e.g. the Installation Destination spoke, which must be always visited, even if you want to use automatic partitioning)
textattribute of the
Example 11. Defining the ready, completed and mandatory Methods
@property def ready(self): """ The ready property that tells whether the spoke is ready (can be visited) or not. The spoke is made (in)sensitive based on the returned value. :rtype: bool """ # this spoke is always ready return True @property def completed(self): """ The completed property that tells whether all mandatory items on the spoke are set, or not. The spoke will be marked on the hub as completed or uncompleted acording to the returned value. :rtype: bool """ return bool(self.data.addons.org_fedora_hello_world.text) @property def mandatory(self): """ The mandatory property that tells whether the spoke is mandatory to be completed to continue in the installation process. :rtype: bool """ # this is an optional spoke that is not mandatory to be completed return False
statusexists; this property contains a single line of text with a short summary of configured values, which can then be displayed in the hub under the spoke title.
statusproperty is defined in the Hello World example add-on as follows:
Example 12. Defining the status Property
@property def status(self): """ The status property that is a brief string describing the state of the spoke. It should describe whether all values are set and if possible also the values themselves. The returned value will appear on the hub below the spoke's title. :rtype: str """ text = self.data.addons.org_fedora_hello_world.text # If --reverse was specified in the kickstart, reverse the text if self.data.addons.org_fedora_hello_world.reverse: text = text[::-1] if text: return _("Text set: %s") % text else: return _("Text not set")
SpokeWindowwidget. This widget, along with some other widgets specific to Anaconda, is found in the anaconda-widgets package. Other files required for development of add-ons with GUI support (such as Glade definitions) can be found in the anaconda-widgets-devel package.
188.8.131.52. Advanced features
pyanacondapackage contains several helper and utility functions and constructs which may be used by hubs and spokes and which have not been covered in the previous section. Most of them are located in
englightboxcontent manager which is also used in Anaconda. This manager can put a window into a lightbox to increase its visibility and focus it and to prevent users interacting with the underlying window. To demonstrate this function, the sample add-on contains a button which opens a new dialog window; the dialog itself is a special
HelloWorldDialoginheriting from the
GUIObjectclass, which is defined in
dialogclass defines the
runmethod which runs and destroys an internal Gtk dialog accessible through the
self.windowattribute, which is populated using a
mainWidgetNameclass attribute with the same meaning. Therefore, the code defining the dialog is very simple, as demonstrated in the following example:
Example 13. Defining a englightbox Dialog
# every GUIObject gets ksdata in __init__ dialog = HelloWorldDialog(self.data) # show dialog above the lightbox with enlightbox(self.window, dialog.window): dialog.run()
enlightboxcontext manager to run the dialog within a lightbox. The context manager needs a reference to the window of the spoke and to the dialog's window to instantiate the lightbox for them.
FirstbootSpokeMixIn(or, more precisely, mixin) as the first inherited class defined in the
@gtk_action_nowaitdecorators), but they are out of scope of this guide. Readers are recommended to go through the installer's sources for examples.
5.6.3. Text User Interface
tuidirectory as described in Section 5.5, “Anaconda Add-on Structure”.
simplelineutility, which only allows very simple user interaction. It does not support cursor movement (instead acting like a line printer) nor any visual enhancements like using different colors or fonts.
Widget. Widgets, which are units containing information to be shown (printed) on the screen, are placed on UIScreens which are switched by a single instance of the
Appclass. On top of the basic elements, there are hubs, spokes and dialogs, all containing various widgets in a way similar to the graphical interface.
NormalTUISpokeand various other classes defined in the
pyanaconda.ui.tui.spokespackage. All of those classes are based on the
TUIObjectclass, which itself is an equivalent of the
GUIObjectclass discussed in the previous chapter. Each TUI spoke is a Python class inheriting from the
NormalTUISpokeclass, overriding special arguments and methods defined by the API. Because the text interface is simpler than the GUI, there are only two such arguments:
title- determines the title of the spoke, same as the
titleargument in the GUI
category- determines the category of the spoke as a string; the category name is not displayed anywhere, it is only used for grouping
NoteCategories are handled differently than in the GUI.  It is recommended to assign a pre-existing category to your new spoke. Creating a new category would require patching Anaconda, and brings little benefit.
prompt, and properties (
status). All of these have already been described in Section 5.6.2, “Graphical user interface”.
Example 14. Defining a Simple TUI Spoke
def __init__(self, app, data, storage, payload, instclass): """ :see: pyanaconda.ui.tui.base.UIScreen :see: pyanaconda.ui.tui.base.App :param app: reference to application which is a main class for TUI screen handling, it is responsible for mainloop control and keeping track of the stack where all TUI screens are scheduled :type app: instance of pyanaconda.ui.tui.base.App :param data: data object passed to every spoke to load/store data from/to it :type data: pykickstart.base.BaseHandler :param storage: object storing storage-related information (disks, partitioning, bootloader, etc.) :type storage: blivet.Blivet :param payload: object storing packaging-related information :type payload: pyanaconda.packaging.Payload :param instclass: distribution-specific information :type instclass: pyanaconda.installclass.BaseInstallClass """ NormalTUISpoke.__init__(self, app, data, storage, payload, instclass) self._entered_text = "" def initialize(self): """ The initialize method that is called after the instance is created. The difference between __init__ and this method is that this may take a long time and thus could be called in a separated thread. :see: pyanaconda.ui.common.UIObject.initialize """ NormalTUISpoke.initialize(self) def refresh(self, args=None): """ The refresh method that is called every time the spoke is displayed. It should update the UI elements according to the contents of self.data. :see: pyanaconda.ui.common.UIObject.refresh :see: pyanaconda.ui.tui.base.UIScreen.refresh :param args: optional argument that may be used when the screen is scheduled (passed to App.switch_screen* methods) :type args: anything :return: whether this screen requests input or not :rtype: bool """ self._entered_text = self.data.addons.org_fedora_hello_world.text return True def apply(self): """ The apply method that is called when the spoke is left. It should update the contents of self.data with values set in the spoke. """ self.data.addons.org_fedora_hello_world.text = self._entered_text def execute(self): """ The excecute method that is called when the spoke is left. It is supposed to do all changes to the runtime environment according to the values set in the spoke. """ # nothing to do here pass def input(self, args, key): """ The input method that is called by the main loop on user's input. :param args: optional argument that may be used when the screen is scheduled (passed to App.switch_screen* methods) :type args: anything :param key: user's input :type key: unicode :return: if the input should not be handled here, return it, otherwise return True or False if the input was processed succesfully or not respectively :rtype: bool|unicode """ if key: self._entered_text = key # no other actions scheduled, apply changes self.apply() # close the current screen (remove it from the stack) self.close() return True def prompt(self, args=None): """ The prompt method that is called by the main loop to get the prompt for this screen. :param args: optional argument that can be passed to App.switch_screen* methods :type args: anything :return: text that should be used in the prompt for the input :rtype: unicode|None """ return _("Enter a new text or leave empty to use the old one: ")
__init__method if it only calls the ancestor's
__init__, but the comments in the example describe the arguments passed to constructors of spoke classes in an understandable way.
initializemethod sets up a default value for the internal attribute of the spoke, which is then updated by the
refreshmethod and used by the
applymethod to update Kickstart data. The only differences in these two methods from their equivalents in the GUI is the return type of the
refreshmethod (bool instead of None) and an additional
argsargument they take. The meaning of the returned value is explained in the comments - it tells the application (the
Appclass instance) whether this spoke requires user input or not. The additional
argsargument is used for passing extra information to the spoke when scheduled.
executemethod has the same purpose as the equivalent method in the GUI; in this case, the method does nothing.
promptare specific to the text interface; there are no equivalents in Kickstart or GUI. These two methods are responsible for user interaction.
promptmethod should return a prompt which will be displayed after the content of the spoke is printed. After a string is entered in reaction to the prompt, this string is passed to the
inputmethod for processing. The
inputmethod then processes the entered string and takes action depending on its type and value. The above example asks for any value and then stores it as an internal attribute (
key). In more complicated add-ons, you typically need to perform some non-trivial actions, such as parse
cas "continue" or
ras "refresh", convert numbers into integers, show additional screens or toggle boolean values.
inputclass must be either the
INPUT_DISCARDEDconstant (both of these are defined in the
pyanaconda.constants_textmodule), or the input string itself (in case this input should be processed by a different screen).
applymethod is not called automatically when leaving the spoke; it must be called explicitly from the
inputmethod. The same applies to closing (hiding) the spoke's screen, which is done by calling the
TUIObjectand call one of the
self.app.switch_screen*methods of the
EditTUISpokeclass from the
pyanaconda.ui.tui.spokespackage. By inheriting this class, you can implement a typical TUI spoke by only specifying fields and attributes which should be set in it. The example below demonstrates this:
Example 15. Using EditTUISpoke to Define a Text Interface Spoke
class _EditData(object): """Auxiliary class for storing data from the example EditSpoke""" def __init__(self): """Trivial constructor just defining the fields that will store data""" self.checked = False self.shown_input = "" self.hidden_input = "" class HelloWorldEditSpoke(EditTUISpoke): """Example class demonstrating usage of EditTUISpoke inheritance""" title = _("Hello World Edit") category = "localization" # simple RE used to specify we only accept a single word as a valid input _valid_input = re.compile(r'\w+') # special class attribute defining spoke's entries as: # Entry(TITLE, ATTRIBUTE, CHECKING_RE or TYPE, SHOW_FUNC or SHOW) # where: # TITLE specifies descriptive title of the entry # ATTRIBUTE specifies attribute of self.args that should be set to the # value entered by the user (may contain dots, i.e. may specify # a deep attribute) # CHECKING_RE specifies compiled RE used for deciding about # accepting/rejecting user's input # TYPE may be one of EditTUISpoke.CHECK or EditTUISpoke.PASSWORD used # instead of CHECKING_RE for simple checkboxes or password entries, # respectively # SHOW_FUNC is a function taking self and self.args and returning True or # False indicating whether the entry should be shown or not # SHOW is a boolean value that may be used instead of the SHOW_FUNC # # :see: pyanaconda.ui.tui.spokes.EditTUISpoke edit_fields = [ Entry("Simple checkbox", "checked", EditTUISpoke.CHECK, True), Entry("Always shown input", "shown_input", _valid_input, True), Entry("Conditioned input", "hidden_input", _valid_input, lambda self, args: bool(args.shown_input)), ] def __init__(self, app, data, storage, payload, instclass): EditTUISpoke.__init__(self, app, data, storage, payload, instclass) # just populate the self.args attribute to have a store for data # typically self.data or a subtree of self.data is used as self.args self.args = _EditData() @property def completed(self): # completed if user entered something non-empty to the Conditioned input return bool(self.args.hidden_input) @property def status(self): return "Hidden input %s" % ("entered" if self.args.hidden_input else "not entered") def apply(self): # nothing needed here, values are set in the self.args tree pass
_EditDataserves as a data container which is used to store values entered by the user. The
HelloWorldEditSpokeclass defines a simple spoke with one checkbox and two entries, all of which are instances of the
EditTUISpokeEntryclass imported as the
Entryclass). The first one is shown every time the spoke is displayed, the second instance is only shown if the first one contains a non-empty value.
EditTUISpokeclass, see the comments in the above example.
5.7. Deploying and testing an Anaconda add-on
/usr/share/anaconda/addons/directory in the installation runtime environment; to add your own add-on into that directory, you must create a
product.imgfile with the same directory structure and place it on your boot media.
product.imgfile and repackaging the image, see Section 2, “Working with ISO Images”.
inst.kdump_addon=onoption in the boot menu.