Skip to content
Snippets Groups Projects

reviewing AIMS docs

Merged Marta Vila Fernandes requested to merge review into master
Files
2
+ 16
8
@@ -150,16 +150,16 @@ To update the Kickstart file for LXPLUS204:
aims2client updateks lxplus204 --kickstart /new/kickstart/path
```
To enable lxplus204 for installation with SLC5 x86_64:
To enable lxplus204 for installation with CS8_X86_64:
```bash
aims2client pxeon lxplus204 SLC5_x86_64
aims2client pxeon lxplus204 CS8_X86_64
```
To display information about SLC5_x86_64:
To display information about CS8_X86_64:
```bash
aims2client showimage slc5_x86_64
aims2client showimg CS8_X86_64 --full
```
To see what else is available for installation:
@@ -171,10 +171,11 @@ aims2client showimage all
### Registering a device and/or Kickstart
```bash
aims2client addhost HOSTNAME [--kickstart=S] [--kopts=S] [--pxe] [--name=S]
aims2client addhost HOSTNAME [--kickstart PATH] [--kopts OPTONS] [--pxe|--bios|--uefi|--arm64] [--name IMAGENAME]
```
To register your host for installation, you must provide the HOSTNAME of the device as given in the Network Database. AIMS2 will then register each interface (hardware address) that is listed in the network database for that HOSTNAME. Only interfaces that are registered should be able to obtain DHCP leases on the CERN network. Should you provide the name of an INTERFACE ALIAS, only the hardware address(es) for that interface will be registered.
The `--pxe|--bios|--uefi|--arm64` option specifies platform/architecture of the client system. Default is `--pxe|--bios`.
To provide a Kickstart file for your installation you should use the `--kickstart PATH` option, where `PATH` is either a `http://` source, somewhere readable (by `linuxsoft.cern.ch`) within `/afs/cern.ch/`, − (STDIN) or a local file. The following examples are valid PATHs:
@@ -274,13 +275,18 @@ Please refer to to the addhost command for valid SOURCE options.
Please contact Linux.Support for permission to interact with PXE boot media.
```bash
addimage --name=S --arch=S --description=S --vmlinuz=S [--initrd=S] [--kopts=S] [--egroups=S]
addimage --name=S --arch=S --description=S --vmlinuz=S [--initrd=S] [--kopts=S] [--egroups=S] [--noprogress] [--force]
```
The option `--name=NAME` is for the name (alias) of your PXE boot media. When defining a name for you media, try to use the distro-arch combination and try to use a name which is meaningful to other users.
Options `--initrd=path` and `--vmlinuz=path` refer to the file system locations of your image and kernel respectively. These locations must be readable by the AIMS2 servers. Some users choose to use their AFS public/scratch directories.
The option `--noprogress` allows to upload the image without showing the progress percentage. Useful when added to automation scripts.
The option `--force` allows to upload the image and override any previous image with the same name. Use with caution.
If you want to check the uploaded boot media files, please refer to:
* <http://aims.cern.ch/aims/boot/IMAGENAME/vmlinuz>
@@ -354,11 +360,13 @@ This will return PXE boot media whose name begings with `cc7`
### Enabling PXE for a device
```bash
aims2client pxeon HOSTNAME NAME
aims2client pxeon HOSTNAME NAME [noexpiry] [pxe|bios|uefi|arm64]
```
To enable PXE boot for a device use the `pxeon` command. This command takes two options, the `HOSTNAME` you are enabling and the `NAME` of the PXE boot media you wish to use.
If `noexpiry` is specified the pxeboot will not be cleaned up 24 hours after enabling.
Default behaviour is to automatically disable pxeboot 24 hours after registration. Boot type option may be specified as `pxe|bios` (default, PXE/bios boot),
`uefi` (PXE/UEFI boot) or `arm64` (PXE/UEFI boot for aarch64 , ARM 64 platform).
If you want to check the generated configuration for your enabled interface, please refer to:
* **UEFI**: <http://aims.cern.ch/aims/config/uefi/grub.cfg-01-MACADDRESS>.
Loading