Autoload the installation profile from the medium root (jsc#PED-16010)

[lslezak]

Problem

• When manually injecting an autoinstallatino profile into the installation medium it is not used automatically. Agama should support autoloading the profile from this location.

Solution

• Autoload the installation profile from the medium root
• Use journal logging with more details in the autoinstallation CLI tool (log to stdout when running manually)
• Not finding any profile in the predefined locations is not reported as an error
• I refactored the code to share the part for initializing the logger

Testing

• Tested manually
• You can inject an installation profile using this command:

  xorriso -indev agama.iso -outdev agama-auto.iso -boot_image any replay -map profile.json /autoinst.json
  

  Where agama.iso is the input ISO, agama-auto.iso is the new modified ISO and the profile.json is the autoinstallation profile copied to the /autoinst.json location in the new ISO.

Screenshots

When running the autoinstallation manually from the terminal the log is printed on the console. When running from the systemd service the logging is redirected to the journal.

The example journal output below contains two service runs, the initial one with the original client, the second one is started after patching the client with this pull request. The new log contains more details (source code locations) and can distinguish between info, warnings and errors (not shown in this case).

Notes

If we want to have a less verbose output on CLI we could modify the logger to be quiet when the output goes to the terminal and add --verbose option to have it verbose always. But I think it is OK to have those details by default, it will be useful for debugging later.

[imobachgs]

In general, it looks good. But, please, move the logging module to agama-utils. The idea is to phase out the agama-lib at some point.