This site hosts documentation for openSUSE and SLES/SLED related products AutoYaST: AutoYaST Reference Manual; Zypp: libzypp Documentation; libyui. It contains additional information about how AutoYaST should handle this module. E.g. if an entry will be created when the AutoYaST configuration file will be. Bugs. Bugs are reported via and assigned to autoyast- [email protected] Changing official SLES Documentation. The official SLES .

Author: Manos Mikakus
Country: Chile
Language: English (Spanish)
Genre: Politics
Published (Last): 24 April 2009
Pages: 105
PDF File Size: 7.15 Mb
ePub File Size: 14.39 Mb
ISBN: 198-2-42781-332-6
Downloads: 24362
Price: Free* [*Free Regsitration Required]
Uploader: Yozshusar

Actually it is not simply bad, it is horrible.

So do not expect to succeed if you use just Novell documentation. It is just impossible.

Suse Doc: AutoYaST – Custom User Scripts

Some pages on the Internet are more helpful and dramatically increase your chances of success. Actually I see the quality of Autoyast documentation as a serious problem for SLES as this is key functionality in enterprise deployment. It is clear that Novell brass made a huge blunder not allocating enough resources to making this functionality robust and providing good documentation.

General capacities of Autoyast are pretty standard, the only unique feature is that it is uses XML file to store settings: The file used for storing information about installation is called the XML control file or profile. The profile can reside on:. To initiate installation which uses autoyast file you need to specify keyword autoyast in Grub, for example.

See Setting up an installation server. Doing this the first time it is important to watch installer mini-OS booting messages. For that press Esc when install started.

You will see if DHCP fails or documentaion and if installed was able to read autoyast file. If just directory was specified, then linuxrc searches for a special configuration file info filewhich is a different type of file from autoyast profile.

That’s confusing, but this is how autoyast is architectured. This file is useful for completely automated installs of multiple servers. All linuxrc autotast instead of special file can be specified on the command line. In case you do not have DHCP on the segment those documentatuon include hostip, netmask and gateway. Enter this line at the GRUB prompt:. Profile enables very granular control of the installation process. If used properly, you can do a fully automated, hands-free installation.

If you happen to miss an item that the installation needs, it stops the installation at that portion and prompts you to enter what it needs.

Autojast configuration profile for the server is typically created during installation. Unlike Jumpstart and Kickstart there is no way to update it automatically as you change the server but you can write scripts to do that. This is a useful feature of autoyast: This is where XML file shines as a configuration storage medium, as editors for XML file are easy to write and generally belong to a pretty established software domain.

Yast documentaation such a specialized editor for XML file which among other things allow you to create parts of an autoinst. You will now be presented with a window that allows you to configure most dicumentation your installation options as if you were installing a new machine or performing an upgrade.

There is a possibility to close options and then edit them. You can proceed through the menu system configuring your options for a particular system or set of similar systems that you wish to automatically install.

Alternatively, you can create class definitions which allows you to save different parts of the configuration setup and then use different classes for different sets of machines. The use of classes is particularly good when you have a set of systems that are similar but that you would like installed in slightly different ways.

  AS NZS 3760 PDF

For example, you could create a class definition for the hardware setup of all your client machines and create a separate class for the packages you want installed on them, whether they are server machines, test machines, workstations, etc. You can then choose which classes are used by which machines when they are installed.

In our example here, all the machines documentatoon use the same hardware setup, but the workstation machines could docuemntation our workstation class of packages, test machines the test class, etc. Once you have progressed through each configuration screen in the config setup GUI from YaST2 you are ready socumentation save out your configuration file to disk.


When you save your configuration files they will be stored locally in two different locations depending on what file you have created as follows:.

Once you have confirmed that you have the AutoYaST packages installed on your system, you can now start to create configuration files. For most situations the basic configuration described here will be sufficient to perform your installations. Before attempting advanced configuration please make sure that you aitoyast first created a valid basic configuration file as described above.

It is perfectly possible to create your own configuration files from scratch but it is far easier to use the tools provided to do the job for you! Once you have your configuration file saved, you can open it in your favourite text editor.

The file is in XML format so it is particularly easy to follow and edit manually. You can use or modify any of the existing tags in your file, just so long as the tags, options, and syntax you use are legal. A full guide to the tags and their usage can be found in the AutoYaST manual, please see Appendix A of this guide for a reference.

The best use of editing the configuration file manually is probably for adding your own customised packages to the installation. Back in the SuSE Server Setup section we describe how to add your own customised packages to your install server. Here, we describe how to access those packages using the configuration file so they can be automatically installed with the rest of documentatiom system. You can include as many package tags under the packages section as you wish.

Use one package tag for each custom package you want to include in your config file and install on the client machine. The base tag at the bottom should be left as you configured it during the basic configuration. Save your modified configuration file from your text editor and it will then be ready to use in your installations as described below. When building appliances with SUSE Studio, I was often challenged with qutoyast a way to configuring an appliance on first boot.

The most common use cases like locale, time zone and network configuration are being offered by Studio already. Selecting these options will make Studio include the required packages and configuration to guide the user through a YaST workflow on first boot. But is there an easy way for further customizing your application on first boot? Next we need to create the AutoYaST profile, which will be run on first boot.

Here docukentation a simple example, that will create a simple ask dialog “Enter the user for this machine” docuentation prompt for input. Now let’s look at a more complex profile, that uses a script to validate the users input. This technique can also be used to process the users input and e.

This lab shows how to setup an automatic SLES9 installation environment, using PXE to start the boot and install process across the network. All the setup is done without user intervention. From the booting up process, components and packages selection, to the final stages and customization. This list only contains the changes of the autoyast itself.


In this dialog, select whether to clone your newly installed system for AutoYaST. Cloning is selected by default. AutoYaST installations are performed using a control file with installation and configuration data.

For detailed information, refer to Section 5. The desktop comes loaded with the applications you need to be productive, like: The OS has seamlessly integrated with your existing network infrastructure and collaboration environment.

Now you’re ready to make the push to a wider audience in your organization, but where to begin? There is an existing howto which goes into much greater detail, as well as describe howto to update device drivers. All files below the ‘inst-sys’ directory will be used to update the installation environment. The directory structure for the appropriate file locations must be preserved.

If you want to replace the mkfs files for example, add the updated mkfs files along with the appropriate directory structure under “inst-sys”:.

Another example could be if you wish to update the hardware detection library: Please refer to the Howto at ftp: Most installation sources reside on a servers harddisk and are available from the network via http, ftp, nfs or even SMB.

I am only focusing on http for this howto. You can validate that the filesystem was created correctly with the appropriate root directory structure starting at linux via the following command:. The latest autoyast2-utils RPM will contain the script as well. This script creates an “updates” tree under the SLE installation source.

This script updates the package database with any new packages or updated package versions in the updates repository.

AutoYaST | SUSE Linux Enterprise Server 12 SP4

After you have created the updates tree, and copied your updated RPMS, you have two options to tell autoyast about the new install updates:. YaST checks the signatures of files contained in the installation source.

If a package file is not signed, during a manual installation YaST asks the user what to do. If you use unsigned packages could be provided as part of a hot fix, or a in-house developed package in your installation source with autoyast, you can turn off the checks with the following configuration in your autoyast profile.

Please refer to the autoyast documentation for full details on what each of these do. You can however, mix the two options. As part of the effort to improve our ability to manage more machines at work I decided to explore two tools to make life easier:. I generally followed the guidance offered at this novell. By “on servers” I mean “no x windows”. If you have an existing openSUSE box setting up the installation server is pretty easy.

Here are the steps involved in setting the server up and linking it to the official Novell yast repostories so your new installations get updated packages. At this point, you can setup new openSUSE machines by installing documentatlon this server. Having the installation server is really nice because you can control and manage a single, consistent set of rpms.

Just having a central installation server is great but with autoyast you can almost completely automate installation of new openSUSE servers.

This works by creating an autoyast control file at which you autoyawt new installations.