Skip to content

Latest commit

 

History

History
136 lines (98 loc) · 4.14 KB

README.md

File metadata and controls

136 lines (98 loc) · 4.14 KB

YaST - The AutoYaST Framework

Workflow Status Coverage Status

Development

This module is developed as part of YaST. See the development documentation.

Have a look to the AutoYaST Development Documentation if you would like to implement AutoYaST support for your YaST module.

Getting the Sources

To get the source code, clone the GitHub repository:

$ git clone https://github.com/yast/yast-autoinstallation.git

If you want to contribute into the project you can fork the repository and clone your fork.

Testing Environment

There are several possibilities how test an updated code. It also depends on the fact in which stage of installation it comes into effect. First stage runs between the start from installation media to reboot (or kexec), then continues second stage.

First Stage

Either use StartShell=1 option in Linuxrc, edit the installation system and run yast manually or use a DriverUpdate via Linuxrc.

Second Stage

There are two possible ways how to rerun this stage, just keep in mind that the system might be already configured and thus it might behave a bit differently:

cp /var/lib/YaST2/install.inf /etc/
touch /var/lib/YaST2/runme_at_boot
cp /var/adm/autoinstall/cache/installedSystem.xml \
  /var/lib/autoinstall/autoconf/autoconf.xml
reboot

or faster without rebooting but with possible side-effects:

yast ayast_setup setup filename=/var/adm/autoinstall/cache/installedSystem.xml

Auto Upgrade

Beside unattended installation this module provide also ability to do unattended upgrade.

Features

  • Semi automatic mode
  • Without autoyast profile on the boot command line it reads the profile from /root/autoupg.xml file
  • When using the Online installation medium the AutoYaST XML profile can be empty

Testing

To test autoupgrade run upgrade with parameters autoupgrade=1 and profile e.g. autoyast=ftp://example.com/ay_upgrade.xml. Following example profiles used for testing online and full media.

Online on registered system:

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
</profile>

Full on system without registration:

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
  <upgrade>
    <stop_on_solver_conflict config:type="boolean">true</stop_on_solver_conflict>
  </upgrade>

  <software>
    <products config:type="list">
      <listentry>SLES</listentry>
    </products>
  </software>

  <add-on>
    <add_on_products config:type="list">
      <listentry>
        <name>Basesystem</name>
        <product>Basesystem</product>
        <product_dir>/Module-Basesystem</product_dir>
        <media_url>relurl://</media_url>
        <ask_on_error config:type="boolean">false</ask_on_error>
      </listentry>
    </add_on_products>
  </add-on>
</profile>

Additional Documentation

  • {file:doc/profile_handling.md Profile Handling}
  • {file:doc/profile_fetching.md Profile Fetching}
  • {file:doc/validation.md Profile Validation}
  • {file:doc/error_reporting.md Error Reporting}
  • {file:doc/network_scenarios.md Network Scenarios}
  • {file:doc/multipath.md Old Multipath Support}

Contact

If you have any question, feel free to ask at the development mailing list or at the #yast IRC channel on freenode.