|
| 1 | +************** |
| 2 | +cobbler distro |
| 3 | +************** |
| 4 | + |
| 5 | +This first step towards configuring what you want to install is to add a distribution record to Cobbler's configuration. |
| 6 | + |
| 7 | +If there is an rsync mirror, DVD, NFS, or filesystem tree available that you would rather ``import`` instead, skip down |
| 8 | +to the documentation about the ``import`` command. It's really a lot easier to follow the import workflow -- it only |
| 9 | +requires waiting for the mirror content to be copied and/or scanned. Imported mirrors also save time during install |
| 10 | +since they don't have to hit external install sources. |
| 11 | + |
| 12 | +If you want to be explicit with distribution definition, however, here's how it works: |
| 13 | + |
| 14 | +.. code-block:: shell |
| 15 | +
|
| 16 | + $ cobbler distro add --name=string --kernel=path --initrd=path [--kernel-options=string] [--kernel-options-post=string] [--autoinstall-meta=string] [--arch=i386|x86_64|ppc|ppc64|ppc64le|arm64] [--breed=redhat|debian|suse] [--template-files=string] |
| 17 | +
|
| 18 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 19 | +| Name | Description | |
| 20 | ++=================+=====================================================================================================+ |
| 21 | +| arch | Sets the architecture for the PXE bootloader and also controls how Koan's ``--replace-self`` option | |
| 22 | +| | will operate. | |
| 23 | +| | | |
| 24 | +| | The default setting (``standard``) will use ``pxelinux``. | |
| 25 | +| | | |
| 26 | +| | ``x86`` and ``x86_64`` effectively do the same thing as standard. | |
| 27 | +| | | |
| 28 | +| | If you perform a ``cobbler import``, the arch field will be auto-assigned. | |
| 29 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 30 | +| autoinstall- | This is an advanced feature that sets automatic installation template variables to substitute, thus | |
| 31 | +| meta | enabling those files to be treated as templates. Templates are powered using Cheetah and are | |
| 32 | +| | described further along in this manpage as well as on the Cobbler Wiki. | |
| 33 | +| | | |
| 34 | +| | Example: ``--autoinstall-meta="foo=bar baz=3 asdf"`` | |
| 35 | +| | | |
| 36 | +| | See the section on "Kickstart Templating" for further information. | |
| 37 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 38 | +| boot-files | TFTP Boot Files (Files copied into tftpboot beyond the kernel/initrd). | |
| 39 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 40 | +| boot-loaders | Boot loader space delimited list (Network installation boot loaders). | |
| 41 | +| | Valid options for list items are <<inherit>>, `grub`, `pxe`, `ipxe`. | |
| 42 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 43 | +| breed | Controls how various physical and virtual parameters, including kernel arguments for automatic | |
| 44 | +| | installation, are to be treated. Defaults to ``redhat``, which is a suitable value for Fedora and | |
| 45 | +| | CentOS as well. It means anything Red Hat based. | |
| 46 | +| | | |
| 47 | +| | There is limited experimental support for specifying "debian", "ubuntu", or "suse", which treats the| |
| 48 | +| | automatic installation template file as a preseed/autoyast file format and changes the kernel | |
| 49 | +| | arguments appropriately. Support for other types of distributions is possible in the future. See the| |
| 50 | +| | Wiki for the latest information about support for these distributions. | |
| 51 | +| | | |
| 52 | +| | The file used for the answer file, regardless of the breed setting, is the value used for | |
| 53 | +| | ``--autoinstall`` when creating the profile. | |
| 54 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 55 | +| comment | Simple attach a description (Free form text) to your distro. | |
| 56 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 57 | +| fetchable-files | Fetchable Files (Templates for tftp or wget/curl) | |
| 58 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 59 | +| **initrd** | An absolute filesystem path to a initrd image. | |
| 60 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 61 | +| **kernel** | An absolute filesystem path to a kernel image. | |
| 62 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 63 | +| kernel-options | Sets kernel command-line arguments that the distro, and profiles/systems depending on it, will use. | |
| 64 | +| | To remove a kernel argument that may be added by a higher Cobbler object (or in the global | |
| 65 | +| | settings), you can prefix it with a ``!``. | |
| 66 | +| | | |
| 67 | +| | Example: ``--kernel-options="foo=bar baz=3 asdf !gulp"`` | |
| 68 | +| | | |
| 69 | +| | This example passes the arguments ``foo=bar baz=3 asdf`` but will make sure ``gulp`` is not passed | |
| 70 | +| | even if it was requested at a level higher up in the Cobbler configuration. | |
| 71 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 72 | +| kernel-options- | This is just like ``--kernel-options``, though it governs kernel options on the installed OS, as | |
| 73 | +| post | opposed to kernel options fed to the installer. The syntax is exactly the same. This requires some | |
| 74 | +| | special snippets to be found in your automatic installation template in order for this to work. | |
| 75 | +| | Automatic installation templating is described later on in this document. | |
| 76 | +| | | |
| 77 | +| | Example: ``noapic`` | |
| 78 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 79 | +| mgmt-classes | Management Classes (Management classes for external config management). | |
| 80 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 81 | +| **name** | A string identifying the distribution, this should be something like ``rhel6``. | |
| 82 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 83 | +| os-version | Generally this field can be ignored. It is intended to alter some hardware setup for virtualized | |
| 84 | +| | instances when provisioning guests with Koan. The valid options for ``--os-version`` vary depending | |
| 85 | +| | on what is specified for ``--breed``. If you specify an invalid option, the error message will | |
| 86 | +| | contain a list of valid OS versions that can be used. If you don't know the OS version or it does | |
| 87 | +| | not appear in the list, omitting this argument or using ``other`` should be perfectly fine. If you | |
| 88 | +| | don't encounter any problems with virtualized instances, this option can be safely ignored. | |
| 89 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 90 | +| owners | Users with small sites and a limited number of admins can probably ignore this option. All Cobbler | |
| 91 | +| | objects (distros, profiles, systems, and repos) can take a --owners parameter to specify what | |
| 92 | +| | Cobbler users can edit particular objects.This only applies to the Cobbler WebUI and XML-RPC | |
| 93 | +| | interface, not the "cobbler" command line tool run from the shell. Furthermore, this is only | |
| 94 | +| | respected by the ``authorization.ownership`` module which must be enabled in the settings. | |
| 95 | +| | The value for ``--owners`` is a space separated list of users and groups as specified in | |
| 96 | +| | ``/etc/cobbler/users.conf``. For more information see the users.conf file as well as the Cobbler | |
| 97 | +| | Wiki. In the default Cobbler configuration, this value is completely ignored, as is ``users.conf``. | |
| 98 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 99 | +| redhat- | Management Classes (Management classes for external config management). | |
| 100 | +| management-key | | |
| 101 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 102 | +| remote-boot- | A URL pointing to the installation initrd of a distribution. If the bootloader has this support, | |
| 103 | +| kernel | it will directly download the kernel from this URL, instead of the directory of the TFTP client. | |
| 104 | +| | Note: The kernel (or initrd below) will still be copied into the image directory of the TFTP server.| |
| 105 | +| | The above kernel parameter is still needed (e.g. to build iso images, etc.). | |
| 106 | +| | The advantage of letting the boot loader retrieve the kernel/initrd directly is the support of | |
| 107 | +| | changing/updated distributions. E.g. openSUSE Tumbleweed is updated on the fly and if Cobbler would | |
| 108 | +| | copy/cache the kernel/initrd in the TFTP directory, you would get a "kernel does not match | |
| 109 | +| | distribution" (or similar) error when trying to install. | |
| 110 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 111 | +| remote-boot- | See remote-boot-kernel above. | |
| 112 | +| initrd | | |
| 113 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
| 114 | +| template-files | This feature allows Cobbler to be used as a configuration management system. The argument is a space| |
| 115 | +| | delimited string of ``key=value`` pairs. Each key is the path to a template file, each value is the | |
| 116 | +| | path to install the file on the system. This is described in further detail on the Cobbler Wiki and | |
| 117 | +| | is implemented using special code in the post install. Koan also can retrieve these files from a | |
| 118 | +| | Cobbler server on demand, effectively allowing Cobbler to function as a lightweight templated | |
| 119 | +| | configuration management system. | |
| 120 | ++-----------------+-----------------------------------------------------------------------------------------------------+ |
0 commit comments