Skip to content
Snippets Groups Projects

Add spellchecker

Merged Add spellchecker
spell into master
Merged Alex Iribarren requested to merge spell into master
Compare
and
18 files
+ 44
− 37
Compare changes
  • Side-by-side
  • Inline
Files
18
docs/aims2/aims2client.md
+ 4
− 4
@@ -84,7 +84,7 @@ The second layer of authorisation for AIMS2 is centered around managing the PXE
To upload your own images to aims, you need to seek permission from <Linux.Support@CERN.CH> first.
Be warned, this process can take 48 hours (please complain to AIS for the delay) so if you plan to spend Monday morning building and the afternoon deploying, think again. This is a one time thing though; as as soon as the other guys manage to sycronise their databases faster, this time constraint will reduce.
Be warned, this process can take 48 hours (please complain to AIS for the delay) so if you plan to spend Monday morning building and the afternoon deploying, think again. This is a one time thing though; as as soon as the other guys manage to synchronize their databases faster, this time constraint will reduce.
When an image is uploaded, it is owned by you. This means nobody else can remove your image except you and the Linux administration team.
@@ -171,7 +171,7 @@ aims2client showimage all
### Registering a device and/or Kickstart
```bash
aims2client addhost HOSTNAME [--kickstart PATH] [--kopts OPTONS] [--pxe|--bios|--uefi|--arm64] [--name IMAGENAME]
aims2client addhost HOSTNAME [--kickstart PATH] [--kopts OPTIONS] [--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.
@@ -364,7 +364,7 @@ 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.
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:
@@ -375,7 +375,7 @@ If you want to check the generated configuration for your enabled interface, ple
Default configuration menus are:
* **UEFI**: http://aims.cern.ch/aims/config/uefi/grub.cfg
* **BIOS**: http://aims.cern.ch/aims/config/bios/main.conf
* **BIOS**: http://aims.cern.ch/aims/config/bios/main.conf
### Displaying a list of PXE boot targets